BEWARE OF QUICKTIME 7.3 with P2 Media

doondoon

doondoon

Well-known member
Just upgraded to Leopard/Quicktime 7.3 and I really feel stupid. Normally I would've waited for the first update, but I got excited and went ahead. I REGRET IT.:(

Now, after the update, ALL OF THE P2 media (any quicktime file shot on the HVX and then brought into FCP through FCP) doesn't open and is 'offline'.

When I attempt to open any of the files I get this error message.

An invalid public movie atom was found in the movie.

Apple. GET IT TOGETHER.:crybaby::angry::angry::angry::angry:

Anyone have this problem... I've seen it on other boards but couldn't find a fix.
 
The issues with QT 7.3 have been reported at the Apple Discussions in FCS for about 10 days now, among other issues with Leopard.

I can and do run P2CMS in Leopard without an issue.

Why not just reinstall Leopard and don't update to 7.3.
 
QT 7.3 doesn't add anything to the mix.

Why not stay with 7.2 on a production machine. In fact, many never moved past 7.1.6.
 
i can't believe I upgraded.
so I guess I'm going to have to do an archive and install to go back to the previous quicktime because you can't uninstall quicktime once it's been upgraded... it somehow becomes part and parcel of OSX.
what a nightmare. I can't fu**ing believe that Apple released a version of quicktime that doesn't work right.
 
This is my number 1 issue with Apple... OK number 2 issue... alright maybe number 3... They CONSTANTLY screw users over with QuickTime.
 
Without meaning any insult, it is always prudent to follow the "IF IT AIN'T BROKEN, THEN DON'T FIX" sampler for any updates.

Many of us with production machines that are running without issue don't touch a QT or OS update until issues with it have been fleshed out for at least a couple of weeks.

To might the horse and barn door analogy, but it is a prudent practice to follow. If nothing FCP is added by the QT or OS update, just sit tight.

best
 
This certainly got my attention, having just upgraded my G4 Powerbook 1.67 GHz to QT 7.3 last night. I also upgraded to OSX 10.4.9 at the same time.

So I just made a little test of importing a clip I have on a P2 card into FCP 5.1.2 and had no problems. It played in the P2 capture window fine, and imported into FCP's Capture Scratch folder and played from the timeline/canvas just fine too. Seemed completely normal in every way.

Sorry to hear you're having this problem, but perhaps my absence of one (thus far) can provide you with some useful information as well as some hope. Best of luck.
 
David S. said:
Without meaning any insult, it is always prudent to follow the "IF IT AIN'T BROKEN, THEN DON'T FIX" sampler for any updates.

Many of us with production machines that are running without issue don't touch a QT or OS update until issues with it have been fleshed out for at least a couple of weeks.

To might the horse and barn door analogy, but it is a prudent practice to follow. If nothing FCP is added by the QT or OS update, just sit tight.

best
Click to expand...
And of course, always make backups. Not just of all your data, but for convenience's sake, your OS and programs as well.

I don't understand why someone would do an OS upgrade without backing the system up in case something goes terribly wrong.
 
Does this effect the PC? I was holding off until they got the Nvidia driver and quicktime problem fixed for a bunch of months and just yesterday I figured it must have been fixed by now and upgraded. :P
 
On the PC side, QuickTime doesn't really factor into the P2 workflow because PC users don't re-wrap their MXF files into MOVs, nor does Apple support DVCProHD on the PC.

If you are using the Raylight Decoder, then there could be an issue, but I don't know for sure. It would mostly affect cross-platform workflow with material coming from a Mac.

Edius uses QuickTime internally (that's one of the reasons why it can open DVCProHD MOVs without any third-party help), and I have not experienced problems since upgrading to QT 7.3.
 
Running Tiger, Final Cut Studio 2, and QT 7.3 here. Just pulled in 10 hours of P2 material today without a problem. Are there other circumstances to this? Does it matter what type of footage you shoot with the HVX? The footage I pulled in was 720 24pN.
 
Beat Takeshi said:
Does this effect the PC? I was holding off until they got the Nvidia driver and quicktime problem fixed for a bunch of months and just yesterday I figured it must have been fixed by now and upgraded. :P
Click to expand...

ALWAYS check with the software manufacturer to verify that they have qualified the version of QTime you are wanting to use. As mentioned above in the thread, the issue in question does not affect P2 on the PC specifically.

However, it may affect your editing app, or your DVD authoring software etc., if it relies on QTime as part of its workflow. If it has not been qualified to work with your specific version of your software, don't upgrade.
 
THoff said:
And of course, always make backups. Not just of all your data, but for convenience's sake, your OS and programs as well.

I don't understand why someone would do an OS upgrade without backing the system up in case something goes terribly wrong.
Click to expand...

Everything is backed up. That doesn't make it less of a huge pain in the ass and it doesn't excuse Apple from the LIST of problems people are experiencing with the new quicktime.
 
krestofre said:
Running Tiger, Final Cut Studio 2, and QT 7.3 here. Just pulled in 10 hours of P2 material today without a problem. Are there other circumstances to this? Does it matter what type of footage you shoot with the HVX? The footage I pulled in was 720 24pN.
Click to expand...



I imported all of my footage months ago via final cut pro (it was also 720pn). Final Cut did it's thing and converted the footage to quicktime. No problems - I've been editing for months.

THEN I upgraded to 7.3 and all of the HVX footage gives me the error.

I can however, bring HVX footage in with no problems no that it's been upgraded... so I guess it only seems to effect previously transfered footage. My problem is that I've got almost 2 Terrabytes of previously transfered HVX footage that won't open.
 
Take_1 said:
ALWAYS check with the software manufacturer to verify that they have qualified the version of QTime you are wanting to use. As mentioned above in the thread, the issue in question does not affect P2 on the PC specifically.

However, it may affect your editing app, or your DVD authoring software etc., if it relies on QTime as part of its workflow. If it has not been qualified to work with your specific version of your software, don't upgrade.
Click to expand...

When you say qualified who is the authority? Internet Forums?
I thought Apple would be (since it's their operating system and their software and their computer).
 
doondoon said:
Everything is backed up. That doesn't make it less of a huge pain in the ass and it doesn't excuse Apple from the LIST of problems people are experiencing with the new quicktime.
Click to expand...

The point being what?

If you backed up and there issues, then do a clone back.

That takes about a 35 minutes on my production machine.

All these issues are the nature of the beast. Software occasionally has bugs, and its part of the process to take that into account.
 
doondoon said:
When you say qualified who is the authority? Internet Forums?
I thought Apple would be (since it's their operating system and their software and their computer).
Click to expand...

There should be release notes available from either Apple or the software manufacturer that you want to use the new version of QT with (sometimes you have to dig a little). Alternatively, if you belong to a user group (like this one for instance) you can put out a general post inquiring if anyone knows if the latest version has been qualified for your setup. Its simple... albeit frustrating to be sure having to wait.
 
You must log in or register to reply here.
Back
Top