Hi - hope someone has answer… I suddenly starting having a problem with CS6 not detecting quicktime, though CS4 does detect it… any suggestions? I’ve seen threads online about this problem; have rebooted/reinstalled QY latest version, and have paid for pro, using v 7.7.2 latest release. Any ideas? thx…
error during cs6 bootup is “Quicktime is not installed on this system, some components will not work correctly”…
The latest version of Quicktime is currently 10.2. It’s possible that 7.7.2 is too antiquated to function properly with CS6, which might be caused by the fact that there is no more Pro version of Quicktime that can be purchased.
So then I’m assuming you’re on a PC? Quicktime is now built directly into MacOS (hence there being no more “pro” version) and is currently on v10.2.
I recently had an issue with Perian being installed, and had to uninstall it to allow After Effects to start up. It kept hanging while trying to launch the Media Core.
I’m not too familiar with the system structure of Windows these days, but if you have any 3rd party importers/exporters in your system library’s Quicktime folder, try removing them, restart your computer and open AE to see if that fixes the issue. It may be an issue with one of the codecs.
true, the importers can be a problem too, esp. 3rd party.
troubleshooting, problem solved, it was in fact my firewall; after finally uninstalling and reinstalling it, ae cs6 now works w/QT. called adobe tech support, the guy eventually was helpful, there’s a Lot that can go wrong with quicktime and AE for the new post cs5 versions, from firewall/permissions/other issues; eg qt32 server has to run properly and other details
MotionRevolver: I recommend that you read the blog post linked to above. QuickTime 10 does not count. It is an entirely different kind of software than QuickTime 7.
Quicktime is now built directly into MacOS (hence there being no more “pro” version)
ToddKopriva said
MotionRevolver: I recommend that you read the blog post linked to above. QuickTime 10 does not count. It is an entirely different kind of software than QuickTime 7.
MotionRevolver: I recommend that you read the blog post linked to above. QuickTime 10 does not count. It is an entirely different kind of software than QuickTime 7.
That’s pretty much the point I was trying to make. Mac users who try to download QT are presented with a page saying it’s already built into the OS, with no active software download link.
MotionRevolver: I recommend that you read the blog post linked to above. QuickTime 10 does not count. It is an entirely different kind of software than QuickTime 7.
That’s pretty much the point I was trying to make. Mac users who try to download QT are presented with a page saying it’s already built into the OS, with no active software download link.
QT 7 was supplied on an additional software DVD with my mac. Couldn’t manage without it.
QT 7 was supplied on an additional software DVD with my mac. Couldn’t manage without it.
I used QT Pro for years and freaked out when they stopped offering it as a Pro app. Luckily the Adobe Creative Suites come with Media Encoder, which I’ve been more than happy with.
QT 7 was supplied on an additional software DVD with my mac. Couldn’t manage without it.
I used QT Pro for years and freaked out when they stopped offering it as a Pro app. Luckily the Adobe Creative Suites come with Media Encoder, which I’ve been more than happy with.
Confused…? I just bought a new macbook pro and I have Quicktime 7 upgraded to Pro version. Should I not have been able to do that?
looks like it’s back to it’s old nonworking status, despite manually adding all the exceptions… for now I’ll have to uninstall my firewall before CS6 is usable, then reinstall… grrr. It’s a known issue, the qt32server and other things that cs6 needs to communicate with, for QT to work. That by the way is just another reason why prerenders aren’t optimum since they’re .mov files for import in ae… png series or tiffs or whatever is always best for both import/export vs movie files i think…? i could be wrong. gotta love this technology stuff.
looks like it’s back to it’s old nonworking status, despite manually adding all the exceptions… for now I’ll have to uninstall my firewall before CS6 is usable, then reinstall… grrr. It’s a known issue, the qt32server and other things that cs6 needs to communicate with, for QT to work. That by the way is just another reason why prerenders aren’t optimum since they’re .mov files for import in ae… png series or tiffs or whatever is always best for both import/export vs movie files i think…? i could be wrong. gotta love this technology stuff.
Image sequences generally make much more sense for proxies / pre-renders / renders in general. Mainly, simply because you can patch an image sequence. You can actually even work with a part rendered image sequence in Ae and Ae will fill in the missing frames as it renders in the background. I haven’t actually tried this with CS6 and global performance cache yet though.
There are a couple of drawbacks with image sequences though that mean I still fairly often use QTs.
I'm often delivered QTs as input material.
Movs read in to Ae a shade faster than most image sequence formats. (I'm hoping for improvements on this in the future).
Image sequences take more management on the desktop, more folders etc.
hey that’s a smart analysis, thanks… good points about still image sequences vs movs… I remember you’d mentioned benefits of image sequences a long time ago; good to know the exceptions. I still like rendering to .mov for ease of use, though if my qt is wonky with cs6 i may go to avi or pngs instead