We experienced a major bug when working with AE CS6.
AE will change any Quicktime exported from AVID when importing or opening.
This will result in unreadable files with the error:
"this 'MooV' file is damaged or unsupported"
In CS5 the file would open properly without any problem.
What really makes this issue dramatic: AE CS6 is corrupting the file
while opening it!
when you import the Quicktime for the first time it looks as everything is ok.
Save the project and open it again,-error.
This destroyed almost all the quicktime footage from a production when someone accidentially opened the project withCS6 where all the clips where linked to.
What is going on here?
Thank you very much,
AVID MC 5.3.3
Oh, man.... I can not imagine your pain and frustration.
I sincerely hope someone from Adobe looks at this thread. The ususal know-it-alls who frequent this forum aren't even responding.
Perhaps my lame response will get somethig going. People will doubtlessly want to know details about your machine & system enumerated here for diagnostic purposes.
If no good comes of it, I hate to say this: if you don't need the features in CS6, I strongly recommend reverting to CS5 just to get the job done.
No idea, but I've seen several errors lately in conjunction with Avid vs. Adobe. Most of them referred to reference QT's, though and there the fix is simply re-exporting, possibly consolidating your media in MC beforehand. If it affects your native files, then I guess you're pretty FUBAR'd and in the future can only hope to duplicate all footage or use video mixdowns, not media linked to the original master clips...
Ok here you go:
This is a Demo-project that will kill your quicktime.
You must restart to get back to normal.
The AVID Quicktime will be unreadable even after this.
Use it at your own risk!
Is the footage that becomes damaged stored on a local drive or on a network?
In one of my clients' facilities we've discovered that using the Madia Manager tool in FCP7 mangles the Quicktime files it tries to process. So far, my only conclusion is that it may be related to a long-standing bug in Quicktime that prevents writing Quicktime files over 2.5GB across certain networks. When FCP attempts to change the metadata of clips over that size, the file becomes unuseable.
I wonder if this is a similar issue - perhaps CS6 AE writes something into QT metadata?
Is does not matter if the files are stored on the network or on the local drive.
You can try the Demo-Project (post 5)
We are painfully aware about the 2.15 GB bug and are astonished that since two Years nobody feels in charge to fix this problem.
I do very much hope that this new topic will be treated different...
I got your footage and it was behaving badly for me as well. It was on a local drive and shouldn't have anything to do with the 2.15 GB bug. That is about writing to a network, which is not supported in CS6.
I would file a bug report, making sure to include the codecs used in the quicktime footage, and the link to those sample files you uploaded. They helped a lot when recreating the issue.
The bug report link is here - https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Make sure you all post a bug report and link to any media/projects that show this behavior.
Screaming in this forum doesn't help, you must make yourself heard via the bug report database that is monitored by the development team.
The bug report form is available at http://adobe.com/go/wish
Wes Plate, one of the initiators of Automatic Duck (which is the "parent" software of the Pro Import module) pointed out that the problem doesn't seem to occur if
Preferences>Media & Disk Cache>Write XMP IDs to Files on Import
I confirmed this, testing it with two lenghty projects that had been totally destroyed whe that setting was enabled (thankfully we had full backups).
Try it out, there's a very good chance it will work for everyone.
I still did file a bug report – it is inacceptable behavior, I hope they at least disable that "feature" by default.
As Jonas says, we can't and don't respond to every bug report. If you need a response from Adobe personnel, then you need to contact Adobe Technical Support:
Note that there has been an Adobe technical staff member on this thread for a while now, Greg Baber.
A real person does read and process every bug report that we get through this form. In fact, that person is sometime me---though the rotating responsibility right now happens to be in the hands of one of my colleagues. Similarly, a real person (me at this time) reads every feature request that we get through the same form.
Regarding this specific bug: We are looking into this and are discussing how we can prevent this problem in the future. For now, the best thing to do is to disable that preference for writing XMP IDs to files on import.