-
Premiere Projects won’t open on a CUDA-enabled machine
So after a project last november, the project files stopped opening. None of them. None of the backups, none of the auto-saves. Nothing.
I couldn’t import sequences into new projects – NADA.
Other projects worked fine – except the one that didn’t.
Old projects work fine – load, etc. etc.
In fact, today I discovered that the project which won’t load on a 5,1 Mac Pro with a Quadro 4000 running 10.7.x load fine on one of our other iMacs running 10.8.1. It’s incredibly odd.
Saving said project on the iMac, and attempting to load it on the Mac Pro still results in the same “serious error” crash.
I’m at a complete loss. The project files clearly aren’t corrupt, but I can’t load them on the machine they were originally edited on (I’d like to edit in that suite with a client.)
Any ideas where to go from here. So far I’ve jumped through the usual Adobe hoops: cleared preferences, caches, etc. Checked disk permissions and even used Digital Rebellions Project File Repair utility to no avail. DId I forget something obvious?
Thanks Cow Crew!
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
1 Reply
-
So here’s what happened.
In the case of all the “Projects that won’t open on the Mac Pro” – they all used a 64-bit VST effect on the output buss of the Audio Mixer. The plugin has since seen a minor x.01 point update from the manufacturer since the project was last known-good.
Opening the project on a machine that does not have the plugin installed/available marks the single plugin on the master buss “offline.”
Here’s the buggy/catchy bit.
If I select “none” from the plugin drop down. It does not hold. Even though the plugin appears to be removed, it is, in fact, not. If I open another timeline/sequence in the same project and then return to the one in question, “Offline” appears again on the master buss.
You/I/One must actually select another plugin (preferably one of the ones that ships with Premiere) and then select “none” to ensure the removal.
If the plugin is removed in this way (again highlighting a bug somewhere in there), then the project will open on the original machine (the one WITH the plugin in question to begin with.)
This is the first time I’ve been truly, deeply, disappointed with Premiere Pro CS6. I’ve had in-use crashes with iLok authenticated plugins before, but never a project that wouldn’t open on a source machine with the very plugin (authorized and all) that was causing the crash.
I’m going to suggest Digital Rebellion add “remove audio plugins” from their Project File Repair utility as a result of this discovery.
Good luck editors!
PK
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger
Reply to this Discussion! Login or Sign Up