-
Strange behavior of Quicktime Player X ….
Hi folks,
Something really strange happened here. I had a PRORES 422 timeline with subtitles made with the App ” Text Up 2″ that I’ve exported as simple Quicktime.
I opened it up with QTP X just to check it out and it played weird shrinking and enlarging inside the the window / frame. I though that could be something about render in FCP and I went back and redered it again but the same thing happened. I’ve tried with QTP 7 and it played smoothly correct.
Any idea ? Does anybody knows if there is a conflict between PRORES codecs and QTP X ?
thanks to everybody …
FredyMacBook Pro 17″
2.5 GHz Intel Core 2 Duo
4GB 667 MHz DDR2 SDRAM
(2) External HD LaCieMac (400/800 FW and USB)with 500GB -(2) USB External HD Western Digital (in cases) with 750GB
OS X 10.5.7
Final Cut Studio 2 -
6 Replies
-
QuickTime X is part of Snow Leopard. Why are you running this on 10.5.x? This can cause problem. Stick to the QT version applicable to your OS.
All the best,
Tom
Class on Demand DVDs “Complete Training for FCP7,” “Basic Training for FCS” and “Final Cut Express Made Easy”
Author: “Final Cut Pro 5 Editing Essentials” and “Final Cut Express 4 Editing Workshop” -
Sorry I had not update my profiles …. Now it is done.
I’m running Snow Leopard 10.6.4 and the latest version of FCS.thanks.
Fredy.MacBook Pro 17″
2.5 GHz Intel Core 2 Duo
4GB 667 MHz DDR2 SDRAM
(2) External HD LaCieMac (400/800 FW and USB)with 500GB -(2) USB External HD Western Digital (in cases) with 750GB
OS X 10.6.4
Final Cut Studio “3” -
If you put that movie in Compressor and play it in the preview window, is it okay or does it do wacky stuff?
What if you reimport that movie back into FCP and play it, is it okay or wacky?
In QT 7 Player Preferences, is the box checked “Enable Final Cut Studio Color Compatibility”? If it is, uncheck it and tell me how it plays.
If you go back to your original sequence and change the sequence codec from ProRes to ProRes HQ and then output a movie, do you get the same results in QT X or is everything okay?
Interested to hear your results.
-
Everything was OK on your 4 options !
To double check I’ve duplicated the sequence in FCP and before changing to PRORES HQ, I re-exported the sequence and the same wacky thing happened. But with the HQ codec it didn’t.
Mysteries of QT ??? lolMacBook Pro 17″
2.5 GHz Intel Core 2 Duo
4GB 667 MHz DDR2 SDRAM
(2) External HD LaCieMac (400/800 FW and USB)with 500GB -(2) USB External HD Western Digital (in cases) with 750GB
OS X 10.6.4
Final Cut Studio “3” -
Thank you.
I think this is a FCP ProRes bug of some sort. I didn’t think it happened in FCP 7.0.2 though.
See this recent post for very similar problem.
https://forums.creativecow.net/thread/8/1094366The workaround seems to change the sequence codec prior to output to ProRes HQ.
-
Hi Fredy,
We ran into the exact same problem about a year ago, shortly after upgrading to Snow Leopard and the original FCP 7. For the life of me, I can’t remember why it happened or how we solved it. But if I remember right, it either had something to do with interlacing or frame size. What are the dimensions and field settings for your sequence and render?
– David
Reply to this Discussion! Login or Sign Up