Premiere Pro CC (2014) and Grayscale Still Images?
Dropping black & white still images in the timeline. Is it better to leave them as Grayscale, or should I convert them to RGB?
Take a look at your GPU usage with something like GPU-Z to see if both Premiere versions are using the same amount of MPE GPU hardware acceleration. Actually with CC 2014 it might work faster because Adobe added in more 4k effects/features for GPU acceleration.
You might want to download our Premiere Pro BenchMark (PPBM) and run it on both versions. The H.264 very complex timeline has 4K material in it and usually shows Premiere Pro 8.xxx take about only half the time that Premiere Pro CS6 take to export that same timeline.
Similar Messages
-
I just updated to Premiere Pro CC 2014 and it can't start up
I just updated to Premiere Pro CC 2014, and now I am seeing an error message saying it cannot find any capable play modules. I updated the driver for my graphics card (Firepro), and tried running as administrator with no change. I am running amd fire pro control center which doesn't have the speed settings that is suggested for this problem. For some reason, the original Premiere Pro CC can still open (luckily). I looked up this problem on the on the support page, and it is listed, but when I click the link it redirects me to the start of the troubleshooting questions. I hope there is an answer to let me use the latest version of Premiere!
[moving to Premiere Pro... JTS]Same here! Screen shot attached. I'm running the latest MBP with max specs. Anybody there @ Adobe.......?
***UPDATE*** - it's pretty easy to fix yourself. Just follow these helpful instruction on Creative Cow: Re: CC 2014 startup issues : Adobe Premiere Pro -
When I try to use a Dyamic Link between something I've cut in Premiere and a composition in After Effects, if it is simply an audio level change it will not update in AE. Only if I alter the Video track does it then take the changes reflected. Any suggestions as to what is causing this?
Running Adobe Premiere Pro CC 2014 and After Effects CC 2014.As Dave alludes, AfterEffects is all about the visual changes ... or at least, mostly. For changes to the audio outside of PrPro's internal controls, highly suggested you use Audition instead. It is all about the sound ... and yes, will update PrPro when used correctly.
Neil -
Premiere Pro CC 2014 and AME using only 25% of CPU
Hello all,
I've been having this problem with Premiere PRO CC 2014 and that when exporting it uses only 25% of my CPU thus taking 4 times longer than CS6 to export the same file project. I read a couple of forums with people having the same problems, I tired disabling CPU parking, disabling "Import sequences natively" in AME but no result.
Quick PC specs:
i5 4670
16GB of RAM
GeForce GTX 760 4GB DDR5
Everything for Adobe including the video files in use are of Samsung's SSD drives. Using CUDA as the render engine.
Currently one hour and 4 minutes clip in 4k takes about 52 hours to encode in Premiere CC 2014 and 9hr to encode the same project in CS6. Any ideas?Take a look at your GPU usage with something like GPU-Z to see if both Premiere versions are using the same amount of MPE GPU hardware acceleration. Actually with CC 2014 it might work faster because Adobe added in more 4k effects/features for GPU acceleration.
You might want to download our Premiere Pro BenchMark (PPBM) and run it on both versions. The H.264 very complex timeline has 4K material in it and usually shows Premiere Pro 8.xxx take about only half the time that Premiere Pro CS6 take to export that same timeline. -
Premiere Pro CC 2014 and Media Encoder CC 2014 not completing encode.
This is a project that I have been successfully encoding in short segments until now. Now when encoding, session runs about 10-15 minutes and then ends without error messages.
Removing effects and changing to Mercury PB Engine SW did not help.
Also tried disabling metadata as suggested in another forum.
When CUDA used, logged as "Encoding failed." When Mercury SW used, logged as "File Successfully Encoded" even though video file is only 6 KB with no content.
Premiere Pro Build 8.1.0 (81)
Media Encoder Build 8.1.0.122
Windows 7 Professional
Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
8 GB RAM
NVIDIA GeForce GT 610 (9.18.13.3788)I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out. -
Premiere Pro CC 2014 and Media Encoder CC 2014 Crashing constantly
Running out of options and ideas...
Symptom: Every time I work on any project in Premiere Pro CC 2014 or try to render out in Premiere Pro CC 2014 or Media Encoder CC 2014, the software crashes after 2-3 minutes of use/rendering when the GPU is enabled in Premiere/Media Encoder, or after 5-10 minutes of use/rendering in software only mode. The crash is a software crash, Windows continues to run fine.
I have tried all the standard list of steps that adobe reps post on threads like these - clearing media cache, software only on render, new project, etc. https://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-windows.html
Windows event is not that helpful to me:
Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff5ecb4de40
Faulting process id: 0x1dc8
Faulting application start time: 0x01d04a503cd82df2
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: unknown
Report Id: cacdfbab-b717-11e4-826d-8863dfc268bc
Faulting package full name:
Faulting package-relative application ID:
I have wiped adobe off the machine and reinstalled - same problem. I have tried projects that crash the machine on other machines and it works fine.
The machine is new, clean install and runs everything else great - 3ds max, high res games, scientific computing - max memory use, etc.
Spec:
5K iMac running bootcamp and Windows 8.1
Intel Core i7-4790K @ 4.0 GHz
32 GB ram
1TB SSD
AMD Radeon R9 M295X 4GB GDDR5
I have used this bootcamp/imac configuration for 5+ years on 3-4 machines and everything has always just worked great. Guess it was my time for a problem, but I'm open to new ideas to try...
Finally - I hope someone from Adobe reads this. I have spent 2 nights on the phone with support. The first night I got an over confident answer that it's a gpu driver issue, just go with software only (no luck - same crashes and different drivers aren't solving the problem). Tonight I was hung up on "by accident" as the agent looked up my video card after waiting 15 minutes to talk to someone, only to be hung up on a second time while on hold after calling back and waiting 20 minutes (because I assume the Adobe call center closed). No message to say so, just hung up on. An overall very disappointing experience.
Thanks in advance to anyone with ideas on things to try,
Cheers!I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out. -
Premiere Pro CC 2014 and Medie Encoder CC 2014 problem
Hello there,
Every time that I am willing to export my project my Premiere Pro CC 2014 stop responding all together. I tried the short cut (Commend+M) or going through the Manu bar. the result is the same, Premiere Pro CC 2014 just freezes and does not respond to anything till I force quit it and restart it allover again. I tried exporting from Premiere Pro it self, without using Media Encoder, but the problem remains the same.
I am using the new Mac Pro. I heard Adobe Premiere Pro is experiencing problems with the New Mac Pro. Is that true? Or is there other issue?
Thank you and looking forward to hear back,
MarufI am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out. -
I Have Windows 8
3.4 Ghz 8 Core Intel i7
32 GB Ram
PPCC2014
I was using Premiere Pro CC for the last year or so and .MTS Files have worked fine. Since I upgraded. I can no longer use .MTS Files.
I sync all of my footage using Plural Eyes. I updated plural eyes so that it would work with the New Premiere Pro CC 2014 update.
I tried going back to Premiere Pro CC; however, that was updated as well. It does recognize the .MTS files there, but it doesn't import the new .xml correctly created from Plural Eyes 3.5
If anyone knows any help or workaround so I can complete my TV episode. That would be great.
Also, I would prefer not to have to Transcode anything. Hours and Hours and Huge files won't really work.
I've also looked in to Re-wrapping. I understand Clipwrap is great for that; however, I have Windows not Mac. Other options look way too involved. I'd really just like my Premiere Pro to work the way it's supposed to,.
Does Adobe Media Encoder Rewrap?
Anyway, any ideas would be helpful.
ThanksThank You, Thank You!!!! That worked. I had to "Link Media" to the new file path, after I renamed the parent folder; however, it's working!!!! Hopefully there will be a fix for that soon!
-
I'm trying to install Premiere Pro CC 2014 and it keeps failing. I'm at this all day!
I've been trying to install Premiere Pro CC 2014 all day. It will begin the installation then progress. Suddenly it will decrease the %complete. Once it went all the way to 84% then failed. Can anyone tell me why this has happened. I have never had any trouble installing any other apps from my CC Membership.
Please read, and reply back here with information https://forums.adobe.com/thread/1499014
-try some steps such as changing browsers and turning off your firewall
-also flush your browser cache so you are starting with a fresh browser
http://myleniumerrors.com/installation-and-licensing-problems/creative-cloud-error-codes-w ip/
http://helpx.adobe.com/creative-cloud/kb/failed-install-creative-cloud-desktop.html
or
A chat session where an agent may remotely look inside your computer may help
Creative Cloud chat support (all Creative Cloud customer service issues)
http://helpx.adobe.com/x-productkb/global/service-ccm.html -
Premiere Pro CC 2014 and Radeon R9 295x2 issues
Just added the R9 295x2 to my system and have experienced a few issues. I installed the Catalyst 14.12 with the newest drivers and when OpenCL acceleration was enabled there was no video display at all in the source or program monitors. Is Premiere not yet supporting these newest drivers? I instead tried installing the previous driver, 14.9 and the issue was resolved. However I now have the issue of tearing during playback. I have an NEC 4K monitor and when I enable playback to this monitor it displays tearing on playback of both 1080 and 4K files. Hoping to get this issue fixed and perhaps the newest drivers can be supported and resolve all issues?
Windows 7
4930K CPU
Radeon R9 295x2
512GB SSD
32GB RAM
27 inch Asus 1080p for GUI
24 inch NEC 4K for playback
Thanks.Take a look at your GPU usage with something like GPU-Z to see if both Premiere versions are using the same amount of MPE GPU hardware acceleration. Actually with CC 2014 it might work faster because Adobe added in more 4k effects/features for GPU acceleration.
You might want to download our Premiere Pro BenchMark (PPBM) and run it on both versions. The H.264 very complex timeline has 4K material in it and usually shows Premiere Pro 8.xxx take about only half the time that Premiere Pro CS6 take to export that same timeline. -
Premiere Pro CC Export issue on still images
Premiere CC latest version 2014.
Hey guys. So I've recently had some serious problems on a couple of projects where I have exported videos with stills (jpegs) in the timeline, and they flicker or have dark lines running through when exported to h264 files - but only on the still images. It is not interlace issues. The exports have odd dark lines flickering over that portion of the export file. The video elements in the timeline seem to export fine though. It has happened on both my main desktop PC on a large complicated edit and on my VAIO laptop on another separate projects that was a very simple talking head with JPEG overlays. So I don't think its an isolated issue in a particular project or on a particular graphics card. Is this a bug in Premiere?
This is a serious problem that got me into trouble this evening on a quick turn around job and I couldn't export a decent version of my timeline.
Any suggestions?Hi James,
This is a serious problem that got me into trouble this evening on a quick turn around job and I couldn't export a decent version of my timeline.
Any suggestions?
Sorry about that. Did you apply any effects? If so, what were they and with which combinations? Did you apply effects to clips or to adjustment layers?
Thanks,
Kevin -
Premiere Pro CS5 won't import still images correctly
I've about had it with this pile of ****.
Brand new install of Premiere Pro CS5. When attempting to import still images, random images will show up as other images. i.e. in Windows, I'll have the following:
one.jpg (shows up at one.jpg)
two.jpg (shows up at two.jpg)
three.jpg (shows up at three.jpg)
Once I import them into PPro, I get this:
one.jpg (shows up at one.jpg)
two.jpg (shows up at two.jpg)
three.jpg (shows up at one.jpg) <-----
In other words, three.jpg is named three.jpg in PPro, but when I bring it into a sequence, or view it, it displays the image from one.jpg
I've tried clearing the media cache, renaming the images, moving them to different directories/drives. Any suggestions? Or should I just get my money back ffs. Thanks for any help.
-EricYou've stumbled onto a bug.
Here's the interim fix.
Imported Image Links Problem
And here -
Does MXF OP1A work with Premiere Pro CC 2014, and later?
Is below formats can work through Adobe preimere CC
File Format: MXF OP1A
Filename extension : *.mxf
VIDEO and ADVANCED VIDEO:
MPEG Type: MPEG-2 Long GOP
Format Profile: 4:2:2@High Level
Video Resolution: 1920x1080(PAL) 16:9 DISPLAY
Frame Rate: 25
Bit-depth: 8
Field Order: Top field first
Deinterlacing: None
Max Bitrate: 50Mbps
Average Bitrate: 35 Mbps
Min Bitrate: 30 Mbps
GOP STRUCTURE: N=12, M=3 (Exam: IBBPBBPBBPBB).
AUDIO
Audio Coding: PCM
Sample Bit-depth: 24 bits
Sample Frequency: 48kHz
Audio channel: Stereo
Message was edited by: Kevin MonahanIt works with a caveat. There is a bug that has been reported here and has yet to be fixed. MXFs are fine to edit with and such, but if you are trying to export to them the resulting file can contain below black information that wasn't present in the original file. Check your exports.
Here is a thread on it:
Re: Data below black level 0 in h264 mp4 files.
(look at the waveform screen captures in the middle of the thread.)
I am still having to use CS 6.03 for all of my mxf exports until Adobe resolves this issue. Been reporting it for years now. It's a pain. -
Running an update for Premiere Pro CC (2014) and the update has frozen at 42%
What do I need to do to get the update to resume? Or do I need to reinstall the update completely?
This is an open forum, not Adobe support... you may get better help from Adobe staff
Adobe contact information - http://helpx.adobe.com/contact.html
-Select your product and what you need help with
-Click on the blue box "Still need help? Contact us" -
Premiere Pro CC 2014 playback freezing and crashing with new iMac i7
Using Premiere Pro CC 2014 and having constant playback freezing and software crashes on a brand new iMac i7.
Here are the specs:
iMac i7 4.0GHz 5k Retina
32 GB Ram
AMD Radeon R9 M295X 4GB graphics card
512GB Solid State Drive
I was on chat yesterday with an Adobe tech. Although playback/render settings show the OpenCL option to utilize the AMD graphics card for processing, I was advised to switch to "Software Only" as that card is not supported yet. I had to re-render my 45 minute documentary (which doesn't appear to be any faster than it was on my old 2011 iMac by the way) and it still has the same issues.
So frustrating? Anyone else experiencing this? Any advice? I hope I didn't just buy this "super machine" in vein.
Thanks,
JasonHi All,
Taking some tips from Kevin Monahan. If you haven't already gone through this list please do so.
Sign out from Creative Cloud, restart Premiere Pro, then sign in
Update any GPU drivers
Trash preferences
Ensure Adobe preference files are set to read/write
Delete media cache
Remove plug-ins
If you have AMD GPUs, make sure CUDA is not installed
Repair permissions
In Sequence Settings > Video Previews, change the codec to one that matches your footage
Disconnect any third party hardware
If you have a CUDA GPU, ensure that the Mercury Playback Engine is set to CUDA, not OpenCL
Disable App Nap
Reboot
Best,
Peter Garaway
Adobe
Premiere Pro
Maybe you are looking for
-
With Firefox as browser, when working on the South West Airline website, when I clicked on the airport code or on their calendar, nothing happened such as showing airport location or the calendar to work on. with Internet Explorer, no such problem. T
-
can anyone help me with video chat on facebook ?my mac book pro cam keeps freezing freinds can see and hear me but i cannot see them im frozen in time but when i go full screen they bappear but they break up any way this can be put right?was fine bef
-
HT4059 How do I load PDF from email to iBooks?
How do I load PDF from email to iBooks?
-
I have a substantial IPhoto '08 library backed up on Mozy.com. My hard drive crashed and, after replacement by Apple, I notice I now have IPhoto '09 installed. I know Mozy has had problems with restoring metadata associated with IPhoto (they know i
-
Hi; i create a project jfx with javafx fxml application; in the second window wher i give the app name ;at the javfx platform the only choice is to put default javafx platform and i click finish the app in projects netbeans appears in red(something w