John, That's great to hear! I'm sure many AVCHD users will be glad to know that timecode is now available in a project; it wasn't that way before, as I recall. My guess on the ProRes "hangs" would be due to the fact that ProRes is 32-bit and, as far as I'm aware, the QuickTime components that Adobe uses are 32-bit, as well. Since Premiere Pro CS5 is a 64-bit application, this presents a bit of an issue; for example, with the AVI container, a codec MUST have a 64-bit flavor in order for Premiere to be able to import, playback, and export to that codec. Any more, 32-bit just doesn't cut it (pun somewhat intended). With QuickTime being 32-bit, and no choice but to support the format and its multitude of codecs that are used frequently in the post-production industry, Adobe created a bit of a "bridge" between CS5 and QT. You're on a Mac, so I don't know how to (or if you even can) look at currently running processes, but on the Windows version of CS5, when importing a QuickTime file, a program/process called "Adobe QT32 Server" runs in the background. Basically, this is a sort of interpreter between the two architectures, and thus, enables the 64-bit application to work with the 32-bit codecs. Now, with any sort of translation or interpretation, there's bound to be some overhead when it's taking place, so I would surmise that the hangs you were witnessing were a result of this hand-off. This is, of course, based on no real knowledge of program coding, so take it with a grain of salt! If one of our increasingly-regular Adobe haunts wanted to chime in, we'd love to hear from you Not so sure on the gamma issue, but QuickTime has long had a history of gamma shifts--though that usually pertained to QT on Windows. Perhaps the FCP forums might have some better idea :shrug: Anyway, glad you're finding the workflow, um, workable. Good luck!
... View more