There's no user setting for this. Something is wrong in your system somewhere, I just don't have a clue where to start looking.
My system was fine with CS6 premiere pro. After I updated it to premiere CC, I am having this problem.
I get that. I just don't know why. You're the first I've seen report this issue. My own two systems do not show this behavior.
Thank you for your reply
I opened CS 6 project file and I was working on it on CC by adding videos and new sequences and there was this huge lag in it.
2 people found this helpful
I've seen other reports of odd behavior for older projects opened in CC7. Try a new project with the same media. How does it perform?
Thanks Jim for the info
You are right. The problem is with opening the older projects in CC7. When I opened a new project and put some videos on it and edited them and exported to adobe media encoder. It was smoother as CS6
Thank you for your time and your support, mate.
I'm having the same issue in CC, I started the project in CC and it very sluggish, I hit the play button there is a delay (2-3 seconds0 and when I hit stop there an even longer delay before it stops (3-4 seconds)
When I did an xml export to CS6, there are no problems with playback or stoping playback.
Also I'm working on a music video with around 1,000 clips and over 900 edits. No effects and the project
has been pre-rendered. Once again I loaded this project into CS6 (via XML) and I'm not having this problem.
3.40 GHz, AMD Phenon II X4 965
32 Gb Ram
Nvidia GTX 570
500 GB Hybrid SSD (Programs)
500 Gb Hybrid SSD (Footage & Project files)
I am having this same problem and can't figure out what is going on. CS6 runs excellent, CC is unbearable. two second delay on almost everything. It is unusable.
-Intel i7 970 3.2GHz with HyperThreading
-Solid State main drive (C drive)
One thing I noticed is that some Adobe processes don't clean up after themselves, causing the system to bog down. I only know this because my Premiere CC tends to crash frequently with my converted CS6 project so with every crash, I saw some duplicate Adobe processes running in Task Manager. I noticed my CC project running slower and slower on inevitable relaunches, thanks to crashing. So, my steps to recover from a crash are now..
1. Exit out of Adobe Creative Cloud from system tray.
2. Kill all Adobe processes in Task Manager.
3. Restart Adobe Creative Cloud.
4. Restart Premiere CC project.
BTW, has anyone noticed that there are 2 'Adobe CEF Helper Project (32 bit)' processes running? Are they duplicates?
Cool, thanks. I’ll give it a try. It sucks because we got halfway through a 12 disc exercise video DVD set before I really started noticing problems. I can’t copy and paste the clips into CS6 and an xml/edl export doesn’t recognize titles. So needless to say, I’m freaking out.
But thanks I’ll give it a try and let you know what happens.
CHRIS TEEBO FILMS
Same issue here.
Still unresolved. I started my project in CC. I've noticed ALL projects in CC start fast and start slowing down after only a few hours of editing. Restarts don't help. It seems once the project is slow, that project will continue to get slower the more you add to it. You can remove some footage from your Sequence, and it might make things a tad faster, but... you've... removed some footage...
Hopefully everyone here has submitted their own Bug Report to Adobe:
As my current project is at whopping 5 second response time on any action, I'm at a complete standstill until this is resolved.
Curious: does everyone who has experienced this problem have CS6 currently installed (not running, of course) on their machine (I do)?
I'm having a similar issue. The major difference in my case, is that video playback is completely stopped, audio plays fine, but video will not playback in the viewer. I can watch the clips individually and scrub through the edit with no lag.
This is happening on 2 Macs and a PC. All have been updated to 7.0.1 and still no fix. Anyone have any ideas?
anyone noticed that there are 2 'Adobe CEF Helper Project (32 bit)' processes running?
Have any of you guys who started the project in CC synced you're settings?
I did not sync my settings. I'm about to wipe everything and reinstall. I have CS6 still installed, but I'm uninstalling that as well, in the chance that it is lending to the problem.
I advise you not to uninstall CS6 as I have already done that and it didn't help. Continue working on your CS6 until adobe fixes this bug.
Awesome. . . Thanks for the heads up.
I just wonder if this could be your problem, running both versions of PPro?
Maybe other's who are doing this could comment. I was running CS6 previously but after verifying CC worked OK, uninstalled CS6. I have run into issues with other software (Windows) where two versions of the same program were installed. Uninstalling the old one has usually worked for me.
I too have run into problems with syncing. I really don't like this idea tbh. You can't beat having local settings with backups. As with all technology - when it works, great, when it doesn't lots of frustration and hassle you just don't need.
Jim Simon wrote:
Have any of you guys who started the project in CC synced you're settings?
I have done a settings sync UP to the cloud and (maybe) a sync DOWN (not sure about that one). Do you have a hunch?
I remember reading about another issue that only occurred after a sync, so I thought it worth checking.
I have both CC and CS6 installed and often actually running at the same time, and have never experienced this issue. Different versions of PP have long coexisted on the same machine, so I'm very skeptical of this as a cause.
WHen I initially used CC version of PP I did a sync up as I have never saved settings before. When I went into the program the other day it said it couldn't perform a sync, maybe the Cloud Server was down. I'm just saying that can be a disadvantage with this type of backup system.
My mouse and keyboard also use the cloud to store settings instead of how it used to work by storing them locally on a RAM chip. If the mouse can't sync for whatever reason, it still works as a basic mouse but all other functionality, I.e. macros, button function is lost and it happens more than I would like. And you are forced into this, there is no choice but its the best mouse for me ergonomically as I have joint problems.
if you are running both versions of the program concurrently with no issues, great. But sometimes running two versions can be problematic and it can vary even between seemingly similar platforms. I know with advances in programming this is not as bad as it used to be but that depends on how well it was written.
Just went to the store and bought a new computer just to test this issue out before I gave up. Same thing is happening, Slow in response, rendering time is doubled. I give up. Both of these machines are running Windows 8, maybe that is the problem.
I have it on Windows 8 myself without any such issues. You're not using a project that was started in CS6, are you?
No I am not. But I do have tons of titles in the project. I just did a test. With no titles, it encodes in almost real-time with GPU on (still double the amount of time it took with CS6), with titles it is taking about 3x real time even though the yellow bar on top of the timeline indicates it does not need additional rendering. It seems as though it takes the longest when there is a motion effect applied to the title (manually keyframed animate in).
In my tests, exporting through Adobe Media Encoder no longer uses GPU acceleration like CS6 did, even if you have it turned on for the project. So those longer encode times do not surprise me.
You can still perform a direct Export, though, and get that acceleration back. (You just can't do anything else while it exports.)
I've always found the same thing with motion effects, they do seem to drastically increase encode times. Same with titles if you have a lot.
I always assumed its because I don't have professional skills and have learnt through books, forums and experimentation so I do it in a less efficient way than a pro editor would.
Would it make a difference if you did the animation in After Effects and imported it as a composition?
I'm by no means an expert on encoding but do sometimes wonder if codecs are fully optimised for the hardware capacity now available. Is some of due to the number of file formats and the fact that the codec has to be able to handle slight variances of each proprietary Manufacturer's format, so can't be fully optimised for every single one. I know there are supposed to be all these standards but with the sheer number of hardware devices out there, is that really the case.
Media encoder never used GPU
It did when you queued up a sequence from Premiere Pro CS6. It no longer does with Premiere Pro CC.
I have the same problem with a MacBook Pro using Adobe Premiere CC. It used to work fast until I did some updates and now my i7 Macbook is running super slow. It just took 2-hours to render a 15-minute timeline with just one title at the beginning. I typically use Adobe rather than Avid Media Composer to do these smaller projects and to render for the web because it's faster. Just not in the past 10-days or so...I hope Adobe gets it fixed soon.
The updates were for Adobe Creative Cloud - not to programs on the MacBook Pro.
Updates to Premiere Pro will reset the "supported cards" text file. You will have to reedit or delete that to get acceleration back for AME exports.
I am having the same problem! Interestingly my Sony VAIO Duo 13 Ultrabook is pretty light on it's feet with Premiere but my custom built NLE frequently runs into these problems.
The result is that I can often load a project faster in the ultrabook and some projects I can actually edit faster!!? The ultrabook has a satisfyingly powerful Corei7 but no serious graphics capabilities to speak of, so rendering is software only and it bogs down a lot when working with compressed formats like AVHCD. I got it just to use it's Wacom digitizer for Photoshop and Illustrator but on my last video, I got frustrated with my desktop NLE machine and cut it on my tiny laptop. (Did it in the car on a road trip. Fun to be able to! But vastly less than ideal for anything very professional.)
My problem is that Once my desktop NLE is running, it can churn through very complex native editing like a dream. It's just that every time I need to change what the program is doing, it takes an exceedingly long time to load new components of the program, i.e. bringing up an effects panel or the audio mixer. My assumption is that once everything the program needs is loaded into ram, there is no problem, but the program is somehow interfering with computers reading and writing to the C: drive where the program is held. Maybe it is creating is some issue with ram caching to the C: drive that is slowing things down. After working with Premiere the problem persists and it takes equally long to open other programs. I had similar problems this summer with the CS6 AVHCD bug in this thread. This is not as bad, but seems very similar in its manifestation. There is no longer any connection to any one codec. Instead, the problem seems to emerge as Premiere has been running for a while. Or after opening Premiere, closing it and then reopening with out a system restart in between. A project imported from Final Cut Pro 6 via XML was particularly problematic, but the problem is sporadic so it was hard to tell if it was that or just a couple of bad days.
Any help or advice would be very much appreciated.
Here are my specs:
- Windows 8 Pro x64
- Intel Core i7-3770K 3.50GHz
- RAM: 16 GB
- Graphics: GTX 660 ti
- Motherboard: ASUS P8Z77-V PRO Thunderbolt
- C: drive: OCZ-Vertex 4 (120GB / 45 free)
- D: drive: Contains Premiere Projects (16TB, RAID 0, 4 SATA3 drives on Intel Rapid Storage Chipset)
- E: drive: Contains User Folders (1TB SATA3)
Has anyone made any progress on this? I have the same problem on a brand new iMac 3.5ghz i7. I receive project files from a CS6 user, but I have to edit them in CC to use MPE with the iMac, and the performance is dreadful and unpredictable.
I feel like I'm right back to the stupid AVCHD bug all over again...
Sorry man, the upgrade to Windows 8.1 did the trick for me and some others I have spoken with. My guess is that's why this thread has been dormant for some time.
Glitches with a project file may cause erratic behavior. Your post seems to imply that you are only having trouble with a project that you imported from CS6. If that is the case, you could get around that by exporting your project as XML and reimporting as a new project to reset any project related issues without loosing much editing progress.
Yes, its only trouble with CS6 imported projects. These are multi-camera projects and I need to maintain all the nested timelines and such. XML does away with all that...doesn't it?
Multicam is well supported in XML. It shouldn't be a problem. The things you are more likely to have trouble with are filters, color correction, titling and any transitions over and above simple dissolves.
In any case, nothing can be lost by trying, since your original project will be uneffected.
I was on your same page, on my Mac I brought 2 projects from cs6 believing cc would do it better, same lagging problem.
The footage was coming from a Canon DSLR (h264, 1080, 24p). So I had the settings as (new sequence from clip), raw as the material, nothing changed, the lagging and audio out of sync was happening all the time. Then changed the settings to .....believe me here ARRI Cinema, keeping the same frame rate and size, of course, (you'll lose the renders you had before). That improved the rendering time and didn't lag anymore.
Coincidence, I don't know, I'm going to try on my 2nd project, but has worked for me so far.
Nevermind the ARRI Cinema settings didnt work on my 2nd project. I actually tried that because when I created a sequence from clip, it said Arri instead of DLSR, don't know why.
Tried XML from cs6, didnt work either.
Don't wanna give up, just going to keep trying, don't know why one project worked and the other one didnt. Both with similar filters (Gamma correction, 3 way color). And only 3 clips had added Warp Stabilizer.
Let's stay in touch!
Message was edited by: Cris_K