-
nothing but problems since installing the new premiere pro CC2014
hello
we are a filmproduction in switzerland working on a documentary, editing on premiere pro cc. ever since I installed the new version (pp cc2014) there have been nothing but problems. adobe support is very slow so I thought I would try my luck here and see if any of you have encountered similar problems.
– after first install of pp cc2014, premiere keeps crashing every 2-5mins saying: premiere pro has encountered an error [/ppro801/releases/2014.03/PremierePro/UIFramework/Src/HotTimecodeControl.cpp-259]’
– I chat with adobe support and go through all possible sceanrios (check if it’s project-based, change user accounts, save reboot, empty cache, uninstall/reinstall etc). during that process the crashing problem dissapears but new ones appear:
– one is that I can’t save my projects anymore (still ppcc14); when I manually save it and re-open, some changes are kept but not others (clips/sequences are not open the way they were before, markers are saved but not marker-notecs, etc). once I opened a different project (a copy of our work-project) and realized it had actually saved an action I had done on the original work project!! the support, at this point, said it was “corrupted beyond repair” and forwarded it some some other tech support who never called me back.
– another problem at that point was that I couldn’t open older projects with the older pp-version (7.2.2) anymore, with premiere saying: “This project contained a sequence that could not be opened. No sequence preview preset file or codec could be associated with this sequence type.” – which was really bad because now I couldn’t even work on my previous projects anymore. at this point I had already uninstalled all the cc-applications and re-installed only premiere pro as it was PRIOR to all the problem’s appearing (version 7.2.2).
– to check if the problems were on our computer I installed the same version on my laptop to find that, here, the sequence-preset/codec-problem did not appear, and it WAS in fact able to open the projects, saying only: “MIssing Renderer: This project was last used with Mercury Engine GPU Acceleration which is not available on this system. Mercury Playback Engine Software only will be used.” so lots of red render lines, but at least it was all there.
– now very interestingly, after I re-opened the same project on our work-computer, the sequence-preset/codec-problem had also dissapeared here and only the ‘missing renderer’-message appeared. that one could be solved by changing the project preferences (after it said that renderer was not certified 3 times, it finally worked). so I thought I could finally continue working… when I noticed I still couldn’t save my projects correctly.
so, as you see it’s all very random and “corrupt”. I get the feeling that the problem is in fact on our computer, but that it was caused by the installation of the new version. I don’t know what else to do, and neither does adobe…
does anyone have ANY idea what could cause such random issues??
thanks a lot!
-
3 Replies
-
I’m having this same thing tonight. I notice that it’s happening when I have markers open. Frustrating.
-
Yes indeed, I got the same error & hard crash today (Sept 19, 2014) when I was editing markers.
Here are the errors:
https://imgur.com/a/RYk32I’m on a MacBook Pro 10.8.5 with Premiere Pro CC 2014.0.1
-
Hey, I am also getting the same two errors.
[/ppro801/releases/2014.03/PremierePro/UIFramework/Src/HotTimecodeControl.cpp-259]
&
[/ppro801/releases/2014.03/PremierePro/UIFramework/Src/InlineEditText.cpp-140]
I am also editing a documentary and heavily use the Markers window. So it seems that it must be an issue with the Markers.
I tried some basic troubleshooting by uninstalling Premier, and reinstalling it completely. I even updated my operating system in the process, but the problem seemed to only get worse. For a while I could edit in chunks of 10 or 15 minutes before a crash. Now when I open the project, it is crashing 10 seconds after I try and edit anything.
Sounds like an issue that Adobe may not yet be aware of?
Reply to this Discussion! Login or Sign Up