Premiere Pro CC 2014 gets stuck on Media Pending.

Hi there,
I've been having a bit of trouble with PPCC 2014 opening projects then getting stuck with all my footage and assets and after effects comps just displaying with 'Media Pending'. The program still works, opens, and I can save and click around so it's not crashing but nothing loads unless I force it to relink which obviously isn't great when I'm having to edit multiple large projects. These projects still open just fine on regular old Premiere Pro CC so I will continue using that for the time being.
Media Encoder is also having an issue with After Effects comps that are in Premiere Pro timelines and only display as 'Media Pending'.
Fortunately all these issues go away if I reboot my machine and try again straight away, but having to reboot my mac just to open a project or do a export isn't exactly preferable.
I have a Mac Pro (late 2013) with 10.9.4 with 16gb Ram and a AMD D500 3GB card.
I'm just wondering if anyone has been suffering with the same issues and has come across any fixes.
Thanks in advance.

Here is my post from another thread concerning the same issue:
I got through Adobe to connect to me remotely to solve this problem twice. They cleaned the cache and preferences and renamed my Adobe folder under applications (don't exactly know how thy did it.) The problem disappeared only to come back after a little while. No video playback, unresponsive buttons - but playable audio, and media pending for all clips. I told them to report this to tech support. This was about a month ago but no updates still..I know I hadn't had this issue neither with CS6 nor with CC.
I am currently rendering my project after changing the sequence's editing mode to Quicktime ProRes Proxy to see if it will help. Preview is still preview but as you said maybe the issue is to be with preview settings set to i-frame mpeg. I have read about the mpeg importer plugin to be an issue in previous versions of premiere pro concerning issues with media pending but i might be wrong.
After changing the sequence settings to Prores Proxy (or if you don't have these codecs installed you may try another codec or google "Prores codec install" and have them installed) the problem cleared away. I have looped the timeline and played it over and over for a couple of hours without the issue surfacing.
For Adobe support and for others to know here is a wiki concerning the issue in CS5. FAQ:Why does my clip show as "media pending"? - Adobe Premiere Pro

Similar Messages

Premiere pro cc 2014 black screen or "media offline"

Almost impossible to do much work in Premiere CC 2014. I use 3 machines in business and Premiere doesn't work with any of them for long. I can be editing fine for about an hour then suddenly my program monitor goes black or says media offline. The only way I can get it back is to reboot about 4-5 times before the project will load again. This happens regardless of where the media is stored, what version of Mac OS is used, or what plugins are used. Anybody else experiencing this?

Hey John! Thanks for the help! So far I've encountered the issue on three different macs. Two are stock iMacs so some AMD chip. The third and least problematic is a desktop running a GTX 780 with CUDA 6.0.46. I will have to check on the two iMacs on Monday... I'm updating the Cuda for the desktop to see if that changes anything.

Premiere Pro CC 2014.1 - end of media indicators different in source and program monitors???

Here are two screen grabs showing the right edges of the source and program monitors in PPCC 2014.1. Does anyone know why the end of media indicators are so different? Left is source monitor, right is program monitor.

Those are actually different indicators. The one on the left is the end of media indicator, which lets you know there are no more frames in the source clip. The one on the right is commonly known as the end of sequence indicator, which can also get to in the Source Monitor if you play a clip to the end and then hit Right Arrow.
Both indicators are controlled by the same option in the Overlay Settings dialog: End of Media/Sequence Indicators.

Hard Drive Setup Recommedation - Premiere Pro CC 2014

Premiere CC on my old Win 7 64bit hard drive had smooth video previews. Premiere CC 2014 on my new Win 8.1 64bit hard drive is choppy and sluggish. Same ATI Mobility Radeon HD 4650 car which uses WDDM v1.1 as the driver. No other driver available.)
Would love some expert advice how to setup my new configuration to be optimized for Premiere Pro CC 2014, get rid of choppy video.
Video is not a huge part of our small 2 person business so
1. I can't justify a large volume expensive SSD
2. can't justify another 2+ days to reload Windows 8.1 and all my programs on the small SSD I have (might not even fit.)
Should I leave programs and OS only on the new WD hard drive... put Premiere project and other data files on the old TOS hard drive and use something like the SDD via eSata as the scratch disk?
Dell Studio 1747 Laptop - 8GB RAM
1. NEW - INTERNAL WD7500BPKX new hard drive with Windows 8.1 - (Program files only) 7200 RPM, 750GB, 16 MB Buffer, 6GB/s
2. OLD - INTERNAL TOSHIBA MK 5056GSY old hard drive w/ Windows 7 (can be wiped and only have data files) 7200 RPM, 500GB, 16 MB Buffer, 3GB/s
3. SPARE - EXTERNAL Lacie d2Next - (partitioned, can be wiped) 5400 RPM, 500GB, 3GB/s eSata
4. SPARE/DONATED - EXTERNAL (eSata, Firewire, USB) OCZ-Agility3 SSD (can be wiped) ~100GB
Thanks. These configurations are an art that we can't specialize in due to our staff size, workload and budget.

Tweakers Page - Disk Setup but start with increasing RAM to at least 16 GB.

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.

Exporting to Media Encoder crashes Premiere Pro CC 2014

Greetings,
I am experiencing a problem with premiere off and on. Right now it is an on problem. When I am exporting from Premiere Pro CC (and CC 2014) it will intermittently crash Premiere. I have tried this with several different audio and video formats (AVI [Lagarith and uncompressed], WAV, H.264, MPG2, AAC, etc). At the moment, every time I go to export to queue it locks up and hangs on the "Preparing data for export..." Media Encoder Launches and then it just freezes. I get "Problem Even Name: AppHangB1" over and over. Sometimes a full restart will fix this temporarily and sometimes it goes away for a long while. I managed to get a few sequences exported and then it just kept freezing on every PP CC restart.
Here are my system specs:
Premiere Pro CC (up to date)
Win 7 64bit (up to date)
i7 970
24GB Ram
NVIDIA 470GTX (driver up to date)
3 x 1.5TB internal
4TB internal
3TB internal
12TB RAID 5 via USB 3.0
USB 2.0 and 3.0 drives
FireWire audio device (M-AUDIO FireWire1814)... although, I am not using it for playback. It is connected.
Footage is from C100 H.264 .MTS, H.264.mov from 7D, and H.264 .MOV from iPhone.
All stock video plugins with a few third party audio plugs.
This problem happens with and without third party plugs, but it happens that this project uses them.
I have chatted with Adobe help twice about the matter and nothing has come of it. Log out, log in = same. Restart = same (sometimes), create new user account = same, and so on. The only thing I haven't done is completely re-install premiere, which seems a bit overkill. One of the reps said he would get back to me in a few days after he watched the issue via screen share. Never heard back.
I get the sense that this has something to do with PProHeadless.exe not launching or not running properly. When the crash happens on a fresh restart of PP CC 2014 PProHeadless is not running. I can start PProHeadless and it will send sequence to media encoder. When I try to export another sequence from the same project it crashes and I see another instance of PProHeadless launched.
Also, once the projects are exported to Media Encoder, I can encode them to any format with no problem. The problem is getting the sequences there!
Is there anything that I am overlooking here?
Thanks for the help!

Hi
Premiere pro cc 2014 8.0.1 (21) build
Encoder CC 2014 8.0.1.48
I use CC for Teams so it updates all the time.
Again when I tried to use it today by letting premiere open it by sending an output into Queue it crashed both Encoder and Premiere.
In order to shut down Encoder and Premiere I had to go into Task Manager and "End Process Tree" on everything adobe I could find because just ending Encoder did not work it would not close. I remembered that years ago when Premiere would crash we had to end a photoshop process. I found photoshop open even though it was not "alive" on my task bar. I had used it yesterday but had closed it. I also had to close dynamiclinkmanager.exe *32 as well as one of the three Adobe CDF Helper.exe*32. They popped back on but Encode closed and then I got a message that Premiere needed to close and did when I clicked the button to let it close.
After all this I re-opened Encoder by itself and checked the Preferences finding that Import Sequences Natively option was again checked.
By the way for me, "Launch AME manually, then drag the sequence from PPro's Project panel to AME's Queue (or to a preset in the Preset Browser). That uses a different code path than the File>Export>Media workflow." won't work most of the time because I do live events of panel interviews that may run 2 or more hours. I need to break them down to chapters for the web
Also I know this isn't part of this problem but I and many others would still love dynamiclink to work to Encore because the DVD is not dead yet. The current work path is a drag.
Looks like some programers and engineers have some work to do.
Thanks
Dennis
My computer:
Self built PC windows 7 Professional 64 bit Build 7601 SP 1 I use auto update so it is up to date.
ASUS P6x58D Premium Motherboard
Intel (R) Core i7 930 @ 2.80 Ghz
Installed Memory 12 GB
NVIDIA GeForce 9500 GT
NVIDIA GeForce GTX 580
2 Apple Monitors and a HP full HD Monitor
With a BlackMagic Intensity Pro Capture Card

Premiere Pro CC 2014 very unresponsive while rendering on background with Adobe Media Encoder

Usually while I eddit videos on Premiere, I'm rendering on the background with AME. Or at least I used to. Some time ago, this process suddenly stopped working, as rendering on the background bagan to make Premiere really unresponsive, and quite impossible to work with. I couldn't think of any change I made other than switching my HDD, and I blamed it on that (it made sense because new HDD is one of those WD Green ones, a little worse than my old Seagate one). So I adapted to just queueing everything and start rendering when I was done edditing. But yesterday I installed a 240gb Kingston HyperX SSD, re-installed Windows and the main apps on it, and tried again, hoping to see an improvement. Now I was storing the original media on the HDD, running OS, Premiere and AME on the SSD, and rendering to the HDD. It did not work. Premiere still became slow while I rendering with AME. So I thought it might get better if the HDD was not reading and writing at the same time, and I switched the original media to the SSD, while still rendering to the HDD. Also didn't help. I don't know why this setup suddenly does not work, and I really need to fix it.
My setup:
Windows 7 Home Premium 64bit
Intel Core i7 2600 @ 3.4GHz
12GB of RAM
nVidia GeForce GTX 560 (yes, drivers are up to date)
Dual monitors (one for Premiere workspace and one for a bigger program monitor)
2TB WD Green HDD where I keep most of my junk (and media files)
240GB Kingston HyperX SSD where I run the OS and important apps (Premiere and AME included)
I'm running Adobe Premiere Pro CC 2014 (8.1.0 build) and AME CC 2014 (8.1.0.122 build)

Hi chriscorrell,
Thank you for posting on Adobe forums.
Upgrading your OS might be a good idea because Premiere CC 2014's OS requirement is OS X 10.8.
See here: System requirements | Adobe Premiere Pro
Thanks,
Rameez

Premiere Pro CC 2014 Crashes During Media Export

Hi, I have diligently applied several of the fixes listed here:
Re: Premiere Pro CC 2014 freezes frequently and crashes
However, Premiere Pro CC crashes at about 10% of the video export -- it gets through the audio stuff as far as i can see.

yeah, checked out the article.
my computer is not shutting down. premiere is crashing. the media exporter is crashing.
it gets through the audio then it crashes during the video processing.
i even tried to hit pause every 2 seconds.
a test exports fine from premiere 6.0, but i am concerned that 6.0 might crash if i rebuild the whole project.
hmm i have an idea.
obviously i would much rather the software worked.

Premiere Pro CC 2014 & Media Encoder Crash when rendering

Every time I try and render something out of Premiere Pro CC 2014 it will crash before it completes the render. I have no idea why. I am on a windows 8 machine running the latest version of Premiere Pro CC 2014.Any idea what is going on?
Here is the log from Event Viewer:
Faulting application name: Adobe Premiere Pro.exe, version: 8.0.1.21, time stamp: 0x53c7b17f
Faulting module name: mc_enc_avc.dll, version: 9.8.11.6624, time stamp: 0x536af65d
Exception code: 0xc0000005
Fault offset: 0x00000000000e7f80
Faulting process id: 0x650
Faulting application start time: 0x01cfb99562fe469a
Faulting application path: E:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: E:\Program Files\Adobe\Adobe Premiere Pro CC 2014\mc_enc_avc.dll
Report Id: f30f38a1-2589-11e4-bf2c-bc5ff467c039
Faulting package full name:
Faulting package-relative application ID:
Here is the Report.wer that windows automatically generates: http://pastebin.com/hriEegkJ
I have also tried rendering out of media encoder and I get a crash also (Report.wer: http://pastebin.com/Dpvk6bDb):
Faulting application name: Adobe Media Encoder.exe, version: 8.0.1.48, time stamp: 0x53c99d97
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000002c2cce3d
Faulting process id: 0xcf8
Faulting application start time: 0x01cfb9906060796e
Faulting application path: E:\Program Files\Adobe\Adobe Media Encoder CC 2014\Adobe Media Encoder.exe
Faulting module path: unknown
Report Id: 07096c20-2584-11e4-bf29-a0f3c1153ce7
Faulting package full name:
Faulting package-relative application ID:

More hardware information might help someone give you an idea
-Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
or
http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-af ter-effects/

Where is a link to the Premiere Pro CC 2014.1 (8.1) update? - Can I get help with the ticktime.cpp-290 error?

Ola to precisando do premiere versao 8.1 caravan consegue o link?
Message was edited by: Kevin Monahan
Reason: needed better title

Hi Kevin,
I posted about the same problem (TickTime.cpp-290 error) in another thread, but since you're asking here specific questions to resolve it, I'm answering it here.
Re: Debug Event: [...\ ...\src\TickTime.cpp-290]
What were you doing when this error started to occur?
          Nothing special I remember. The only thing I do recall, is:
          I was working with Premiere Pro (where the main project is), After Effects but rendering some PNG sequence, and Adobe Media Encoder. I sent from AE to AME a project to render. Configured 2 outputs (PNG & MP4). The same way I sent from PP a project to render and one error occured. Unfortunately I didn't write down the error, but it was like a path C://AME_64/something. But the AME queue updated and everything seemed OK. I close AME to be sure that the error wouldn't be the source of future error during rendering, and relaunched it. And at that time I couldn't open it. I got the error "Adobe Media Encoder has encountered an unexpected error and cannot continue". The only way I found to resolve this is to remove the directory /Users/%USERNAME%/My Documents/Adobe/Adobe Media Encoder/8.0/". The problem seems to appear when I save the queue. And since that time, Premiere do the TickTime.cpp-290 error.
          Another thing I noticed, don't know if it was there before, is, the AEP file in AME queue setttings displayed framerate as "25 / 29.97 / 30 / ...", a 2 digits number for the framerate. But suddenly (I thought first it was because of the Premiere Pro file being added to the queue, but no because it appended after without it), it was displayed as "25 000 / 29 970 / 30 000", a 5 digit number.
          After that, the TickTime.cpp-290 appeared. Sometimes when opening project, sometimes and resetting or changing the workspace (because it was messed up), sometimes when closing.
Do you have iCloud installed?
          No.
Is this a Premiere Pro CC 2014.0 or Premiere Pro CC 2014.1 project that was updated to Premiere Pro CC 2014.2? If so:
          It started long time ago a draft in CS6, but since I reopen the project, I saved new versions in Premiere Pro CC 2014.2 (not sure if I have other version like 2014.1 or 2014.0). Is there a way to know which 2014 version are my files? If I look into the XML I only saw Version="28"
Do you have a copy that can be opened in an earlier version?
              An old draft version in CS6. But that version has footage in different framerate and not all be interpreted at the timeline framerate.
Do you get the same error in that earlier version?
               No error here, the file opens properly.
              Additional info: I tried to open the 2014.2 file on another computer (where PP 2014.2 is installed) and same problem (this computer is on Win7 64-bit)
Did you use any unusual footage types in your project?
     I used MOV (Animation), MP4 (H264), and PNG sequence. The framerates of the footages are 24,25,30 and 60fps (but everything has been interpreted in 30fps)
If you remove them, do you still get an error?
              When I had the error, but not when I open the project file, I resave the file removing anything not interpreted in 30fps (because at that time I still had footage interpreted in their original framerate). I was able to work for some time, but now I can't open it anymore despite that.
Was the fps interpretation changed in any of the clips?
     Since the error appeared, and because I saw in another thread that it could be related to footage of different framerate, my timeline is now in 30fps and all the footage have been interpreted in 30fps. Footage are MP4, MOV, PNG sequence in 24, 25, 30 & 60fps.
If so, restore them to their original fps and see if you still get the error.
              Unfortunately, since I can't open the project anymore, I can't test that.
Did you use Warp Stabilizer?
          No.
Do you have any browser plug-ins?
          What do you call browser plug-in in Premiere?
Are there any third party plug-ins used?
          I have Magic Bullet Looks 2, and I'm using it on this project.
If so, remove the effect from those clips and see if it improves the situation.
              Unfortunately, since I can't open the project anymore, I can't test that.
Some additional infos on my computer.
I use Windows 8.1 (64-bit), all Adobe softwares installed have the last update (for video apps, it's 2014.2)
The language settings are configured in French, but Windows and CC apps are in English.
If needed the 2014.2 project file is here:
https://dl.dropboxusercontent.com/u/68413846/showreel19_30fps.prproj
Thanks in advance to help us to resolve this weird bug.
Christophe.

Premiere Pro CC 2014.2 crashes when "locating media"

The problem;
Premiere Pro CC 2014.2 crashes when "locating media". I am working on a project that has not given me any problems for the last 200 hours. About a week ago I notice that the .proj file size was 276mb and found this odd because my largest project to date was never larger than 80mbs. I thought that the premiere was running slow because of the project size. As luck would have, when my client made their their final changes 2 days ago, I opened the project and premiere would hang on the locating media window and then would crash. I called Adobe and spent an hour on the phone with them to no avail.
Project workflow
- 700gb of 5d footage
- 20 sequences under 5 minutes
- Dynamically linked files with AE
- Warp Stabilized about a dozen clips of under 5 sec
- On every sequence color correction adjustment layer with RGB Curves, Three way color corrector and sharpen filter
- I kept old versions of the sequences (I was in version 5 before the crash)
What I have tried;
- Unsuccessfully tried to open auto-save files for this project.
- Successfully opened other older non relevant project
- Removed Mercury playback engine in the project settings
- Cleaned out media cache database through pp in media Preferences
- Manually deleted cache files in /Common/Media Cache Files and /Common/Media Cache
- Tried importing sequences into new .proj file; it would crash as a result.
What "worked".
I was able to open it on another computer. save it under another file name. bring it back to my original computer and open it without problem. I lost about 3 days working through this problem, I missed my deadline. and angered the client. I was able to use a friends IMAC to "fix" the problem, however I can't always count on him being there if it happens again.
Questions.
- What the hell happened? Why could I open it on one computer and not on the other?
- Is there a way to fix a corrupted .proj files on a PC?
- What should the average file size be, before it becomes unstable? (I'm pretty that my file size was bloated by all the previous versions of the sequences)
Windows 8.1 64bit
Premiere 2014.2
Intel Quadcore i7-4770 3.40GHz
16gb Ram

Hi,
I would suggest the following steps:
http://blogs.adobe.com/kevinmonahan/2014/09/10/premiere-pro-cc-freezing-on-startup-or-cras hing-while-working-mac-os-x-10-9-and-later/
Run a disk permission repair on your boot drive, and
Reset Home Folder permissions and ACLs Error | Apple Support Communities
Thanks,
Rameez

Can't get GeForce GTX 560 Ti card CUDA to work with new Premiere Pro CC 2014 version

In the past I've been able to get CUDA on my GeForce GTX 560 Ti card to work with Mercury Playback engine by adding "GeForce GTX 560 Ti" to the cuda_supported_cards.txt file. But with the new CC 2014 version of Premiere, that file isn't in the Premiere Pro directory anymore. Is there a way to get my GTX 560 Ti to be listed as a CUDA-supported card with CC 2014?

Okay, I figured it out. I installed the latest graphics driver and then opened the NVIDIA control panel. In there I selected "Manage 3D settings" and went to the "program settings" tab. I selected Adobe Premiere (adobe premiere pro.exe) from the list and under the "CUDA - GPUs" feature, I changed it to "Use these GPUs" and selected my GTX 560 Ti (which was the only one listed).
After doing that, I opened Premiere Pro CC 2014 and selected "Project Settings - General" and was then able to choose "Mercury Playback Engine GPU Acceleration" under Renderer (which had previously been unavailable).
Hopefully this will help someone else if they encounter the same problem.

I am using 4K Footages for editing in Premiere pro CC 2014, but its getting crash in between at every 15 to 20 mins. Kindly suggest how can it be solved, does any plugins or settings needed to edit 4K footages? Also would like to mention that footages fra

I am using 4K Footages for editing in Premiere pro CC 2014, but its getting crash in between at every 15 to 20 mins. Kindly suggest how can it be solved, does any plugins or settings needed to edit 4K footages? Also would like to mention that footages frame rates are 29.97 and i have set timeline to 25 FPS is requirement by client. kindly revert. Thanks

Thanks Richarad ..It has solved the problem but still crashes some times .As the programme has the break (bumper)after every five minutes ,i hope it will not compress bumper time too after export.

Importing Premiere Pro CC 2014 media into Avid MC8

Hi guys,
I've been having a problem using AAFs to move sequences from Premiere Pro CC 2014 to Avid Media Composer 8, long story short I'm working with a post company using Adobe for everything, but the editor is at a different facility and uses Avid. I've been testing a workflow to go between the two, I know how to use both programmes and relink media, but when I import the AAF i made in Premiere into Avid although the footage names are there and the sequence shows up in the correct order when i try to reconnect the offline media no matter what I try it just won't do it.
Having googled it I found that this used to be an issue between Premiere CS6 and Avid 7, so is this still an issue that I have to find a way around? Or is there a simple fix that I haven't found?
Thanks,
Andy
Also I forgot to note that the files we use are .MXF, which are unsupported by FCP7, meaning we can't go through Automatic Duck in there. Go figure.

More hardware information might help someone give you an idea
-Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
or
http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-af ter-effects/

Premiere Pro CC 2014 gets stuck on Media Pending.

Similar Messages

Maybe you are looking for