Premiere Pro CC 2014 suddenly choppy or no playback from timeline or preview

Hey folks. The header says it all - can't play back anything smoothly as of this morning.
HP Z820 w/ dual Xeons, nVidia Quadro 4000, 32Mb RAM, 500Gb SSD boot, several internal and external (via USB3) drives.
This is pretty frustrating. One thing to consider is that, due to misconfiguration of a synchronizing program, my C: drive got 100% loaded up over the weekend. I removed the errant files and it now has 45% empty. (Only programs on C:, no media.)
I have updated the nVidia driver, which didn't help at all.
Anyone else seeing this? Thanks -

How old is your SSD? As long, as it has no garbage collector (like the Samsung EVO) and it was heavy in use over last month this really might be the reason. Also external drives can slow down the playback for they are often under 7200rpm or don't deliver full speed via usb 3 for some reasons as I have experienced...

Similar Messages

Premiere Pro CC 2014 (8.1.0) freezes while scrubbing timeline

Using a Mac Mini (late 2012 model), running Mavericks 10.9.5
Processor: 2.6 GHz Intel Quad Core i7
Memory: 16 GB
Graphics: Intel HD Graphics 4000 1024MB
I am also using a 2TB Fantom G-Force Megadisk external HD to store all my media. It is connected via a Firewire 800 cable
I've been having a lot of trouble with Premiere Pro CC 2014. While scrubbing through a project, a frame will all of a sudden freeze in the program monitor. I have my processors displayed on my menu bar and I've noticed that whenever I run into lag time or freezing the 8 processors won't all be firing, usually just one is actually working at that time. I am also only running one program at a time as to not tie up my processor.
All of my source files are usually AVCHD. Most of my work is under 10 minutes long, so they are just short corporate videos not feature length movies. I understand that editing native files can really slow your processors so with my latest project I consolidated and transcoded in the Project Manager to Apple ProRes in order to test that. Even with that I'm still having the exact same problem.
These are some other steps I've taken to correct this:
I've contacted Adobe several times and they told me that the Graphics Card is known to have problems and to contact Apple. I contacted Apple and they said there are no known problems with that Graphics Card it sounds like a software issue. I ran a disk permissions test and uninstalled and reinstalled the software. Same problems. Nothing has worked.
I've trashed my preferences as well
Really it seems that both Adobe and Apple are pointing the finger at each other. All I want to do is edit my videos without having to restart Premiere Pro every 10 minutes.

This seems to be an issue for me A LOT too. I can't keep Premiere open for more than 2 minutes at a time right now. The Customer Service rep from India did a "Team View" on my computer before and after 45 minutes finally fixed the issue. But I can't seem to get a hold of customer support right now. I hope you and I both find a solution soon. Good luck!

Premiere Pro CC 2014.2 - Crash when dragging videofile into timeline

Hey guys,
when I try to drag a image or videofile (doesn't really matter which fileformat, codec or length) into a sequence Premiere Pro CC 2014.2 will crash immediately, without a warning. Just the usual "Adobe Premiere has stopped working" in Windows 7.
I'm using Windows 7 64-bit with 4GB RAM, Intel Core i3-4130 COU @ 3,40 GHz and a Intel HD Graphics 4400. Premiere Pro worked seamlessly just days before, without any change to the system. The error occured in Premiere Pro CC 2014.1 too. Maybe it's a problem with the video preview? Music files are no problem.
Thanks in advance! Need help asap. customers are waiting

Solution:
My graphics card did not supported the "Mercury Playback Engine GPU Acceleration (Open CL)". You can change it into "Mercury Playback Engine Software Only" in your Project Settings.
But this is in the wrong place in my opinion. Why not in "Edit/Preferences"? I could've changed it by myself but I did not find the menu.
Thanks Michaela from the Adobe Support Chat!

Premiere Pro CC 2014 keeps freezing when loading projects from Premiere Pro CC

Hi everyone,
I'm reporting this issue in case someone else would have the same problem.
I just downloaded the 2014 version of Premiere Pro CC, and when I'm loading a project from Premiere Pro CC into CC2014 I have the software freezing and being unable to even play the loaded sequences. It seems that dynamic link is having trouble linking the CC and the CC2014 version of Premiere Pro.
Until now the only solution I found was to kill the process of the software and start it again, after 8 times I got my sequence loaded alright, then sometimes it is freezing again, killing process, starting software again, and so on. Does anyone has the same problem ?
I'm running a Windows 7 Ultimate PC with 12Go RAM dedicated only to Premiere Pro.
Cheers,
Vincent

Hi Vincent,
I feel your pain, you are not alone. Here are my machine specs and my very frustrating situation, if anyone has any idea as to how I should move forward, I would really appreciate the input/advice...
iMac - 27" Late 2013
Processor 3.4 GHz Intel Core i5
Memory 12 GB 1067 MHz DDR3
Graphics NVIDIA GeForce GTX 780M 4096 MB
Software OS X 10.9.4 (13E28)
I'm having similar issues that began when I installed Premiere Pro CC 2014, and actually got worse with the latest update/release. The majority of my projects worked fine at first, but the update last week ended that quickly. I did what I know I never should do and updated Adobe CC while completing a project on a deadline. I thought some of the fixes would help me complete the project sooner. Needless to say, the deadline has passed, my client is pissed enough to not pay me or hire me again and I'm stuck with an almost-there version that I can't export correctly because of this software. This is my problem, not Adobe's, but I didn't expect such a detrimental update to halt my operation.
After doing some research, I found that some plugins could be the cause of some specific editing issues, mainly due to incorrect or inaccessible folders - who knows if its Dynamic Link, CC apps or 2014 apps. I concluded that my issue at the time was a plugin permissions issue on the Adobe "Preference" Folder, so I reset the permissions on the folder so that CC and 2014 apps would be able to access its contents without any problems. This was the wrong decision. For some reason, resetting this folders permissions also effected the main HDD, it's Kernel Text files and their respective permission. I could not boot my machine, just got the Apple and spinning wheel until I had to power down. I ended up on the phone with 3 different AppleCare reps who helped me at least be able to turn the machine back on and access my desktop/files, apps, etc. Outside of this, no one could offer anything other than "Uninstall the problematic application, reboot, reinstall, etc..." or "Backup your files and reimage the HDD." When I mentioned the recent CUDA driver update for my graphics card (NVIDIA GeForce GTX 780M 4096 MB now running CUDA Driver Version: 6.0.51), it was like they had never heard of graphics cards being used in their machines.
Resetting permissions on Adobe Preference Folder...
This is what I read would get the CC and 2014 apps communicating correctly so that they could utilize my plugins. There is a problem, I believe, in that their are TOO MANY locations where Adobe folders/components live. There are 3 "Preferences" folders that I found, and I don't know which effects what process, but the folder I changed permissions on clearly effects the operation of all of the CC & 2014 apps I had installed, as well as my HDD. Kernel Extensions and the entire system.
Based on my perceived effects of the Preference folder, I needed to uninstall everything, run the Adobe CC Cleaner Tool, download/install just the 2014 releases and see if that resolved the issue. I'm not downloading CC apps, the 2014 releases should run fine on their own. I've yet to confirm this with Adobe, as what I've read has simply said to install the new release next to the CC apps, rather than on top of, as traditional update releases work. Anyway, one by one, I reinstalled the 14 apps that I use on a regular basis on a "clean" machine with no trace of previous Adobe apps.
After reinstalling (without any plugins), I was at least able to open Premiere Pro from the Application folder and work for a few minutes before both Program and Source monitors froze and had to force quit the app. If I try to open the Project File by double clicking it in the Finder, SpeedGrade opens up instead of Premiere Pro - never seen that before. I also had to force quit to end that process and reopen in Premiere instead of SpeedGrade.
So back to Premiere, if I do have success in opening a project in the right application, Premiere freezes - if not immediately, eventually it will just stop responding. The video clips, sequence segments and UI freeze, but the audio will keep playing until I force quit. When I force quit, Premiere Pro doesn't close entirely. The UI closes, but the process still runs. I've even force quit from Finder, force quit again from the Dock, Shut Down the machine, restarted and Premiere Pro will still be open, but "Not Responding", so I force quit again and open the project. Just now, I opened PP, made minor edits to a sequence, sent it to Media Encoder, exported, but the video I tested exported without audio. I force quite PP twice just before that and it is still running now, but again, it is "not responding".
Ultimately, none of this works, nor have my attempts at resolving these many issues. One thing I know is that there is something VERY WRONG with either the latest release/update to 2014 apps, the Preference folder or the permissions that were changed.
As I mentioned previously, and what I think is a major oversight by someone at Adobe, is that for some reason the permission changes to ONE Adobe folder also effected my entire system and Macintosh HD. Some Kernel Extension files went missing, which is never good and should not happen when resetting folder permissions, so I believe my issues are far greater than the faulty Adobe CC 2014 applications, and is the cause of many of my problems right now. If I can't get things sorted soon, I'm going to reimage my HDD and start from scratch. As much as I would like to avoid this, I really have no choice if I want to get back to work and not lose clients over inexplicable technology issues.
If I find a solution, I will repost, but I think Adobe has to make some serious fixes on this release before anything is resolved entirely. I pay them monthly and rely on their software and platform to work without issue, which is foolish - I know, but I've used CC since it was introduced and it has work well enough until now.
Is there anyone at Adobe that can offer some advice??

Premiere Pro CC 2014 - Black flickering lines during playback and when exporting video

I am fairly new to Premiere and have recently started using creative cloud on my new MacBook Pro retina - 2.3 GHz Intel Core i7 - 16GB Memory - OSX Version 10.9.4
I shot a music video using my friends camera and all the shots were absolutely fine, I dropped them into Premiere and started editing the video together.
Some of the clips are perfectly fine during playback, although sometimes my playback stutters a little, but some of the clips have strange horizontal lines that flash through them when I watch it back. I have only used basic things such as the highlight/shadow and sharpen tools in Premiere. I thought that it maybe fine once I exported the video but when I open up the exported file on my desktop in Quicktime the little black flashes/glitches are still there in some of the shots.
Here is a screenshot you can see a line halfway between the top of my head and the top of the screen, when you watch the video there are lots of these flashing about.
Could this be something that I have set up wrong?
CPU/GPU related?
Thanks,
Jordan

Hi there,
thanks for the reply!
GRAPHICS = NVIDIA GeForce GT 750M 2048 MB
I tried that but it didn't work unfortunately, Mine was already set to the one you said, I tried the other but no change

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,
Maruf

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.

Timeline frequently stutters during playback after upgrade to Premiere Pro CC 2014?

I recently upgrade to Premiere Pro CC 2014 and I have noticed that my timeline playback frequently stutters on playback if I jump around in the timeline. Other times if I just hit play the sequence will start playing back fine but then it will start stuttering after a few shots? This never happened before. I'am playing back C100 AVCHD media using create sequence from clip option for my timeline settings. I recently upgraded to Yosemite OS on my mac pro and I have not noticed any improvement. Any help would be appreciated.
Thanks
Harry
My specs: Mac Pro 2009
Processor 2 x 2.26 GHz Quad-Core Intel Xeon
Memory 32 GB 1066 MHz DDR3 ECC
Graphics NVIDIA GeForce GTX 680 2048 MB
Startup disk SSD

Thanks for the info Kevin. However on doing more probing into my problem I
realized the problem was being cause by my Kona LHi card. The Kona card has
started to whining sound, so I disconnected the card. When I went back in
Premiere Pro everything in the time line played back really fast with no
stuttering. The response time in the timeline is very fast. And I can jump
around the timeline with no problem. I will be getting my Kona Card looked
at by AJA, I'm sure there is a problem with card.
Thanks
Harry
On Sat, Nov 8, 2014 at 1:31 PM, Kevin Monahan <[email protected]>

Importing Final Cut XML Hangs Premiere Pro CC 2014

I am posting this more as a question as to how to report hangs or console reports of PP crashes.
I have a Final Cut Pro project that I wanted to migrate to Premiere Pro using the XML route. When I import the XML from Final Cut, the app hangs with a series of console messages. I think it can't import the DVCPro HD audio and many of the filters used in the Final Cut Project also cause this hang.
On import, a rectangle dialog box appears with no content in it - just a white box. Then the pinwheel of death.
Here are some of the console messages:
11/21/14 10:50:24.289 AM Adobe Premiere Pro CC 2014[1051]: Error loading /Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHDAudio: dlopen(/Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHDAudio, 262): no suitable image found. Did find:
/Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHDAudio: no matching architecture in universal wrapper
11/21/14 10:50:24.290 AM Adobe Premiere Pro CC 2014[1051]: Cannot find function pointer NewPlugIn for factory C5A4CE5B-0BB8-11D8-9D75-0003939615B6 in CFBundle/CFPlugIn 0x115488460 </Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin> (bundle, not loaded)
11/21/14 10:50:30.419 AM Adobe Premiere Pro CC 2014[1051]: Unable to find filter reference documentation "".
11/21/14 10:51:20.658 AM Adobe Premiere Pro CC 2014[1051]: NSAlert is being used from a background thread, which is not safe. This is probably going to crash sometimes. Break on void _NSAlertWarnUnsafeBackgroundThreadUsage() to debug. This will be logged only once. This may break in the future.
11/21/14 10:51:41.000 AM kernel[0]: Sandbox: sandboxd(1088) deny mach-lookup com.apple.coresymbolicationd
11/21/14 10:51:42.102 AM sandboxd[1088]: ([279]) coreaudiod(279) deny file-read-data /Library/Audio/Plug-Ins/Components/A52Codec.component
This also generates an Adobe Premiere Pro hang log in the console system diagnostics.

Sort of a work around I am testing:
I have a cool script to open FCPro projects in AE. Sort of a free Automatic Duck. I was going to do this:
Remove all effects and proprietary tracks in FCPro, as some cause problems with this script. Trial and error here.
Use the free script FCP2AE to export to AE (it's hard to find now)
Open the timeline in AE via the script FCP2AE
Export that from AE as PPProCC 2014 project
Open in PPCC2014
That may work, it may also work just to remove all effects and then save the XML and open in PP CC 2014. Again sometimes it does work. The simpler the FCPro project the better.
Another option
I was able to open the FCPro audio only OMF in Audition. Then I exported via XML FCPro format from Audition and this opened the audio tracks in PPCC2014. The stereo tracks were broken and placed on two mono tracks so you'll have to address that one.

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.

Can't Move Audio Clips in Timeline After Expanding to View Waveforms (Premiere Pro CC 2014.2)

So, this seems to be a bit of a weird one, and I'd be pretty stoked if it ended up being something silly that I'm doing wrong, but I can't for the life of me figure out what that might be.
As the title suggests, I can't use the mouse to move some audio clips in a timeline once I expand the track to view the waveforms. This appears to only happen with independent audio clips (WAV. AIFF, MP3, etc), and not with clips attached to video. Also, it's worth noting that I don't have track keyframes turned on. I was hoping that was it, but it wasn't.
So, what happens is this:
1) I drag an audio clip down to the timeline (I can drag it onto an existing track, or drag to the bottom of the sequence and create a new track. Neither option seems to get a different result.).
2) So long as the track isn't expanded and the waveform isn't visible, I can move the clip left, right, or up and down to a different track.
3) As soon as I expand the track to view the waveform this functionality goes out the window. When this issue happens I can use the keyboard to nudge left and right, but that's about all the movement I have.
4) It's almost as though the track becomes corrupt. The lanes for the track don't redraw properly, and the track is pretty much unusable. I can't put anything into it, and I can't take anything out. All I can do is delete the track and start again.
Complicating issues is that this doesn't always happen, but instead is one of those "vast majority of the time" issues. I can't see any rhyme or reason for why it works or doesn't. I seem to do the exact same thing, but occasionally get different results. It doesn't matter what type of file I'm using (WAV, AIFF, etc), and this only happens with independent audio clips.
Once again, I don't have track keyframing turned on when this happens. Believe me, I wish that was it.
I have already filed a couple of bug reports about this over the last month or so, but haven't heard anything yet. I was wondering if anyone else was having the same issue, and if so, whether they had any workarounds.
Mandatory system info:
Windows 7 Professional SP1 (64-Bit)
Intel i7-3820
32GB RAM
Nvidia GTX 980 (350.12)
Premiere Pro CC 2014.2

Update:
I was just looking to post a screenshot of the timeline when I discovered something interesting. As soon as I use the vertical scroll bar to the right of the sequence, the tracks start to work again. Close off the waveform and the clip goes haywire. Move the scroll bar a tiny bit (or a lot), and suddenly the clip starts working.
Pretty bizarre.
The good news is that for the time being that could be a workaround, though it would be great for this to not happen at all.

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

Adobe premiere pro cc 2014.2 has stopped working error 1000

I'm about to throw this desktop across the room. Please someone help me. When I was using this last week, it would close all of a sudden after a while. Now, it does it so quickly I can only save once. Can anyone help? It's going down hill and I've got deadlines.
Thanks in advance,
Leslie

Adobe Premiere Pro CC 2014.2 is the version I am on.
I am up to date on all updates.
Windows 7 64 bit Enterprise
It stops working with anything I do.
This is the error message I get in the application log:
Log Name:      Application
Source:        Application Error
Date:          4/27/2015 4:13:02 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      USDOE0042087DT.BECHTELJACOBS.ORG
Description:
Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
Faulting module name: devenum.dll, version: 6.6.7600.16385, time stamp: 0x4a5bded7
Exception code: 0xc0000005
Fault offset: 0x00000000000016a0
Faulting process id: 0x13a8
Faulting application start time: 0x01d0812687cc6c6e
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: C:\Windows\system32\devenum.dll
Report Id: cde2b72f-ed19-11e4-be69-005056c00008
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-04-27T20:13:02.000000000Z" />
    <EventRecordID>696921</EventRecordID>
    <Channel>Application</Channel>
    <Computer>USDOE0042087DT.BECHTELJACOBS.ORG</Computer>
    <Security />
</System>
<EventData>
    <Data>Adobe Premiere Pro.exe</Data>
    <Data>8.2.0.65</Data>
    <Data>5486db4a</Data>
    <Data>devenum.dll</Data>
    <Data>6.6.7600.16385</Data>
    <Data>4a5bded7</Data>
    <Data>c0000005</Data>
    <Data>00000000000016a0</Data>
    <Data>13a8</Data>
    <Data>01d0812687cc6c6e</Data>
    <Data>C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe</Data>
    <Data>C:\Windows\system32\devenum.dll</Data>
    <Data>cde2b72f-ed19-11e4-be69-005056c00008</Data>
</EventData>
</Event>

Rendering white flicker on the program monitor and output video file. How to get rid of this flicker in adobe premiere pro cc 2014?

Hello,
I have been working with long sequences in adobe premiere pro cc 2014. All of sudden, I see white flicker in the program monitor and rendered output too. The flicker does not follow any pattern. It is very random.
How to work around on this?
Regards
Naveen Alle

Concurrently working on the same project it requires a specific implementation in all editing programs like Avid's Unity/ ISIS shared storage. That's what you are simply not considering. none of your issues would be any problem if your projects resided on a commonly accessed server or something like that. Check respective hardware solutions.
Mylenium

Premiere Pro CC 2014 suddenly choppy or no playback from timeline or preview

Similar Messages

Maybe you are looking for