-
PP has encountered a problem…
have you seen this before???
thanks for helping out a bonehead!
__________________________FCS3 / Adobe CC
3.33 GHz 6-Core Intel Xeon Mac Pro
24GB RAM
ATI Radeon HD 5870
…and a few TeraBytes o’ storage
(then it’s on to PetaBytes, ExaBytes and MosquitoBytes!) -
4 Replies
-
What are you doing when this occurs? Are you opening Premiere first or trying to open a project to have it launch Premiere? Is this a project you’ve opened successfully before? Are the project and media local or external? Have you installed any new plug-ins or done software updates recently? Are you current on CC?
– Oliver
Oliver Peters – oliverpeters.com
-
Oliver,
Thanks for the reply and query. In answer:
Just editing as usual. A long ways (several days) into a project, and it “just happened”, though seemed to keep occurring when i click on a specific clip in the sequence, so assuming the clip had been corrupted, so i opened the last version (thank you, 20 instances of auto-save!) prior to the error and have had no problems since.
I’ve tried both.
Yes. For many days.
Local.
No.
Yes. CC 2019.
thanks for helping out a bonehead!
__________________________FCS3 / Adobe CC
3.33 GHz 6-Core Intel Xeon Mac Pro
24GB RAM
ATI Radeon HD 5870
…and a few TeraBytes o’ storage
(then it’s on to PetaBytes, ExaBytes and MosquitoBytes!) -
So it sounds like you solved the problem. That it was a corrupt clip.
– Oliver
Oliver Peters – oliverpeters.com
-
It appears so. And it got corrupted in between two saved versions. Very odd.
thanks for helping out a bonehead!
__________________________FCS3 / Adobe CC
3.33 GHz 6-Core Intel Xeon Mac Pro
24GB RAM
ATI Radeon HD 5870
…and a few TeraBytes o’ storage
(then it’s on to PetaBytes, ExaBytes and MosquitoBytes!)
Reply to this Discussion! Login or Sign Up