What is the latest version of QT that works fully with FCS2 & AE ?

[Walter Biscardi]

latest and greatest works here.

Walter Biscardi, Jr.
Biscardi Creative Media
HD and SD Production for Broadcast and Independent Productions.

STOP STARING AND START GRADING WITH APPLE COLOR Apple Color Training DVD available now!
Read my Blog!

[Andy Mees]

me too, Toke
the present offering is one that is working solidly here for me … however clearly not so for you there are a number of factors that might influence the success or failure of any particular combination of OS and application versions and updates:
a lot might hinge on specific hardware variations ie processor revisions, gpu’s/gfx cards, ram etc
other factors might include which other software is installed that could potentially cause a conflict with other specific software and hardware permutations
plus all of the above combined with a specific workflow, codec or even specific media files

as such a definitive list of known good software configurations for OS and FCS alone might be hard to nail down, for sure someone somewhere would disagree (your own current situation would be a prime example)

all that said and done there is a list you can refer to over on Jon Chappel’s blog on the Digital Rebellion website although its still dated back to the end of January so may not have been revised for the latest versions:
https://www.digitalrebellion.com/blog/posts/recommended_quicktime_and_mac_os_configurations_for_final_cut_pro.html

hope it helps
Andy

[Toke]

Hmmm, I can’t login to Apple’s discussion so maybe I’m banned because this was too insulting to them:
“Pretty amazing that almost every update to QT has broken something in Pro apps (Apple’s own or Adobe’s) in last half a year.”

Andy,
would it be good idea if Apple just updated Pro versions later than noPro?
Or is it that most QTPro users want all the latest capabilies?
I feel a bit like beta tester to do all this reaserch “Will it work” after QT updates.

Have I understood right that in FCS2 & CS3 enviroment only problem with current QT is AC3 passthrough and some LT bouncing?

I need to playback 1 hr long document from my MP in next monday’s premiere in digital cinema theater and I’d really like to use DD5.1 sounds…

[Andy Mees]

Well. as I posted over there, from a technical standpoint I don’t see how they could facilitate this …

Separating the pro and non pro versions of quicktime would almost certainly require splitting it into two frameworks, either with the pro framework sitting on top of the regular qt framework host (and so inheriting any and all of the problems that come with the non pro releases) or as two entirely discrete frameworks for the same quicktime layer, and there is surely a whole heap of pain down that road

Then again, thinking about it afresh, I guess you could have the pro framework entirely replacing the standard framework so that it would not see or accept regular qt updates, only pro ones … but this is all just idle chatter as the OS developers are not likely to be heading in this direction any time soon (or indeed ever)

In reality the only feasible way to deal with the issues of beta testing updates is the same way that these things have always been dealt with in any pro production environment … that being that YOU (we) act as the gatekeeper …. never EVER update a working production machine until you have thoroughly tested the update on a non production test bed. Honestly its very basic stuff and has been rule 1) since time immemorial, and I don’t mean that simply as an off the cuff fanboy defense of Apples shoddy QC / limited beta testing.

As for your specific needs … well thats a perfect an example of what’s wrong with the current QC/Beta testing setup. i have no doubt whatsoever that AC3 passthrough and LT bouncing were NOT tested as they are probably too esoteric to have caught anyones attention, which of course doesn’t help you a bit.

Toke, if you haven’t done so already, post your thoughts (as politely as possible) over on the FCP feedback page. Its really only if enough folks make educated noise that things might change. I’m quietly optimistic that Apple will lead a new charge with FCP, and the better thought out comments they receive will help to mould that charge.

For now, clone your hard disc (discs are cheap). Install the updates and personally test your intended workflow, see if it works. If it doesn’t then clean reinstall stopping and testing as you go. Try to find the sweet spot for your setup and then stick with it until you have a chance to thoroughly test later updates to see if they are suitable for you. Always keep a clone before you commit to the upgrade of a production machine, even if you have already tested on a secondary machine. Agreed. its no fun … heaven knows we all like an update with all the tempting new bells and whistles it brings, but you have to turn off not just the madness of automatic software updates but also the mentality that drives it. Its the only sane solution.

Cheers
Andy