Originally Posted by TimNielsen
But here is the thing that I'm finding increasingly frustrating, you're saying this could be related to a corrupt audio file. Then why the hell can't ProTools, KNOWING obviously while file is throwing up this error, come back and say 'File XXX is corrupted, would you like me to repair, or quarantine, or remove, or SOMETHING, this file...
I mean, I ran into a situation a few months ago, where some fade got corrupted, and it took my down my ENTIRE session. Lost. Could not repair it, recover it, import tracks from it. Nothing. Spent a full day on it, and screwed.
PT8 seems so much more prone to these kinds of things than any other version of PT. And I mean, it must BE ProTools that's causing this corruption. I never have had a single file from any other system, program, anything, on my mac, get corrupted. Yet PT files, especially session files and fade files, get fracked up all the time.
Why?
And why when one audio file does get corrupted, by whatever means, will ProTools just throw up a generic 'magic ID error' and then refuse to even open the session at all. That just seems silly that you could couldn't build in some better robustness into this program. It has seemingly so many Achilles' Heels to take it down, a single fade, one audio file getting messed up could screw up your entire session.
Why not say 'This audio file seems corrupted, should I go ahead and load it anyway, and highlight it in bright red and tell you where it is on the timeline so you can investigate', instead of just saying 'some ID doesn't match, can't open session, game over' ?
|