-
Invalid public movie atom error message after QT 7.3 upgrade
Great band name, but a real problem. Since upgrading QuickTime to 7.3.0, P2 files (DVCPRO HD 24p 720) (which I BELIEVE, not sure, were all brought in via P2 Log Pro) make my computer go all bloooey as soon as the playhead hits them. I get the error message < invalid public movie atom >. My output screen turns green, canvas and viewer are both non-functional. I need to quit and restart the program, avoiding any clips captured by P2 Log, which are peppered throughout this particular project. Clips brought in via regular FCP P2 import seem to be fine, however. Is anyone else experiencing this, and is there a workaround (such as trashing QT 7.3 and going back to an earlier version? I’m not sure how to do that properly…). Disk Warrior, repairing permissions have no affect on the problem. Thanks, Dean
g5 quad, OS 10.4.10, FCP 5.1.4, 4.5gb ram, some pain
-
9 Replies
-
Just got an email from imagine software saying QT 7.3 breaks their software:
“ATTENTION MAC USERS of HD Log, P2 Log, P2 Log Pro, and DV Log!
The recent QuickTime 7.3 has caused complications for many software products utilizing its video technology. Imagine Products has also experience such issues with the 7.3 QT update. Please be aware, the update may break QuickTime files from our software as well as other software applications.
While we are working tirelessly to correct the problem and provide our users a timely patch for their software, we ask that you consider NOT updating to QuickTime 7.3 at this time. If you have already done so, please be patient while we find a workaround.
Sincerely,
The Imagine Products, Inc. Team
DV Log
-
I just spoke with the people at Imagine software. They’re not sure that reverting to an earlier version of QT will help at this point, and the “replacing codec” fix does not seem relevant to this particular issue with P2 Log Pro files.
-
hi.
I have the same problem.
Same scenario… except I think that I brought this P2 footage in through FCP.
Have you figured out how to deal with it?
thanks,
michael -
I was fortunate, or perhaps smart enough, to have cloned my hard drive to another drive about a month ago, so I’ve offloaded the newer files off my current drive, wiped it clean, and am now cloning the old drive and its unupgraded QT system back onto my working drive. I guess the alternative would have been an archive and install with 7.2 QT, but it didn’t come to that for me. Best of luck….this is indeed nasty.
-
Imagine Products advises me that rolling back to QT 7.2 will work. That means a complete drive wipe and system install. Not what I had in mind for the next two days.
They also say no fix until after US Thanksgiving, at least ten days away for P2Log Pro and longer for HD Log.
Maybe Apple will do a QT update before then? Any info?
-
It’s a bad thing, this thing. I was fortunate in that I had another drive with my previous system cloned onto it (my favorite form of backup) which I swapped out with my “updated” QT drive, and I’m back in business. If I didn’t, I’d be looking at the complete reinstall you’re talking about, not pretty. I’d like to think there’s a fix in the new 6.0.2 update to fcp just released, but I read the release notes briefly and saw nothing about this problem in there…
Poor imagine software…all their mac stuff is broken with this QT release, it must really suck for them. -
I have the same problem after uppgrading to quicktime 7.3, but only with clips imported with p2 log.
If I re-import a non working clips with final cut, it works very well. The soulution seems to be to re-import all files that where imported trough p2 log with Final cut instead.
What would a vise strategy be for reimporting files? Is it possible to batch import p2 files in finalcut pro?
I have hundreds of non working clips and hundreds of clip working clips? To manually re-import all non working clips would take a lot of time. Batch importing P2 files would really be a time saver!
paulS
-
Imagine Software just published a fix for the problem with QT 7.3 and P2 log (pro).
Here’s what they just sent me:
ATTENTION MAC USERS of HD Log, P2 Log, and P2 Log ProWe’ve now resolved the incompatibility issues with the recent QuickTime 7.3 update. The problem was P2 specific.
New versions of all Panasonic P2 compatible applications are now available for download that are fully compatible with QT 7.0 – 7.3. The patches are also compatible with OSX 10.5.
Please download the appropriate update for your software from our web page at: http://www.ImagineProducts.com/dlupdates.htm (under the Support/Downloads tab)
Details of the problem:
The new QT 7.3 changed (slightly) how null values within the MOV file header are defined. Apple, for some unknown reason, departed from the long standing zero (0) designator for a null setting–now a minus one (-1) value = null. This small change (which may have been an oversight?), causes QT Player and any QT based application attempting to play the MOV file to fail since the QT engine no longer knows what action to perform when a zero designation is encountered.
Since MOV files already existing with a zero designation are no longer playable, it is unclear at this point whether Apple will fix the problem in later QT updates or not. There are numerous applications providing QT files that may have been affected by this problem, and you may have many older QT files created by Apple applications that will not open due to this problem.
At Imagine Products, we’re looking into the possibility of providing a batch “repair” utility for existing MOV files with this specific problem. If successful, we’ll send out another email when it’s available.
Thank you all again for your patience. And again, we wish you a happy holiday.
Sincerely,
The Imagine Products, Inc. Team
-
IF you have the files saved on an external drive (or even if they were at ANY point saved on an external drive), go to your manuf’s website and download the latest firmware upgrade for that external drive. Worked for me and solved ALL my .dmg issues, ALL my public movie atom issues, and all my “Error 4960” issues.
If the files became “corrupt” at some point (while they were on an external drive) – copying them to another location would only be making copies of broken files. You have to go back to the drive (hopefully they are still there). Keeping the files ON the drive, update the firmware. Everything came back for me, instantly. Whew!
Reply to this Discussion! Login or Sign Up