QuickTime isn't a codec, it's a multimedia framework.
Basically, don't use QuickTime anything and you're good.
However, for best export quality you'll want those preview files to be as high quality as possible, preferably Uncompressed or something lossless. I like the UT codec, which works under AVI for Windows. On a Mac, not sure you can do it, as any lossless would use QT.
Jim Simon's advice is only relevant for Windows users. hey Aaron is clearly using a Mac.
I export to QT often, and I use previews.
The correct answer is "Sometimes it uses the previews, others it just re-renders everything on export." It depends on what switches you throw in the Export window, and what your Sequence Settings for Previews is. If your Sequence Previews are the same codec as your export codec, then your exports should use your Previews, and go faster. It works more reliably on CS6 than previous versions, in my experience.
My sequence IS set to identical ProRes 422 settings as my export. Is there a switch I'm missing?
Yes, I'm on a Mac.
Is there a better workflow? Most of my content is all the same - ProRes 422 1920x1080 @ 29.97.
If your Sequence Previews are the same codec as your export codec, then your exports should use your Previews, and go faster.
They don't really need to be the same. Working properly, the preview file should be used to create the export, rather than rendering new frames from scratch during export. But I thought there was a problem when both preview and export were QuickTime. Is that no longer the case with CS6? It does seem Aaron is still have that same old issue.
It seems hit and miss when I use ProRes for the Preview codec and export h.264 for reviews. But, you're right, it should speed up exports regardless. That's the intended behavior. But, I've read a lot of posts here where it's not working correctly on Mac. CS6 and previous.
This isn't scientific, BTW, just recalling my own experiences.
It seems hit and miss when I use ProRes for the Preview codec and export h.264 for reviews.
That should work, since the export is not QuickTime. The failure comes when both preview and export are QT. I believe this applies to both Macs and PCs. It's a limitaion of QuickTime.
The problem is that you really do want lossless for the previews if you're going to use them for export, and I don't think you can get lossless previews on a Mac without using QT. Which means for a QT export, you simply can't Use Previews (or at least, it won't work if you do). On Windows, you can get lossless with an AVI, which should work for a QT export. You just can't get a ProRes QT on Windows.
All video movies on Mac are Quicktime, even uncompressed, which can be achieved with Quicktime None or Animation 100%. Both of those are 8-bit, though, which would defeat "Use Maximum Render Quality," if so desired.
IINM, image sequences may not require QT. But, then you migh have issues if the next app in the transcode process don't accept image sequences. And they're not available as a Preview File Format on Mac.
However, ProRes is a perfectly fine preview file format. It's just that Pr doesn't always use the Previews on export, the way it should.
I usually master to ProRes, and when doing so, Pr usually will use the Previews, and they are fast.
In any event, I don't normally experience the overly long exports from Pr. Looking back at the OP, a 2 hour export for a 5:30 sequence is outragous, and I believe is a sign of something else amiss, other than typical Pr behavior.
It's just that Pr doesn't always use the Previews on export, the way it should.
That's what I'm saying. QT previews to QT export has trouble, even on the PC side.
QT preview to any other export should always work. Any other preview to QT export should always work. Are you saying you have trouble even when one of them isn't QT?
a 2 hour export for a 5:30 sequence is outragous, and I believe is a sign of something else amiss, other than typical Pr behavior.
Quite possibly. Depends on the complexity of the sequence, effects used, Aaron's hardware, etc.
I turned off CUDA accelleration, because I was getting banding issues with my alpha channels on my lower thirds. After that, I re-rendered my previews withOUT CUDA, and viola. My export took the right amont of time - about 5 minutes. Almost real-time.
Updating now. (Although my current driver was up-to-date as of a week ago.)
Have you heard of the banding issues with CUDA cards? This is what I was experiencing: (not my project - but similiar issue)