Re: DPX in FCS3

Yeah, gluetools will help you with DPX management and essential if using LOG footage and want to export LOG, but being able to RENDER DXP sequences natively is what I would like to see.

Having FCP studio import DPX sequence, made a transition or dissolve, then you look in your render bin and their is 48 dpx frames that is your dissolve. Not a QT encapsulator.

Right now GlueTools can import then export DPX, but its not a true DPX management, say I import LOG DPX files, you can't edit then export to COLOR because the DPX sequences do not exist, the GlueTools codec holds all the DPX information and can export DPX with proper meta data, color space etc... but their are no DPX files on your computer from your FCP changes. Apple COLOR will look at the gluetools quicktime and get totally confused, and other programs that work with DPX sequences, since its a QT holder not a DPX sequence.

The whole workflow has a lot to be desired, and that is something I hope Apple can figure out with QT. If they do that, FCP studio is getting closer to a true DI system and can work on a network of programs that just want to see DPX sequences, not proprietary glue-tools codec that encapsulates a DPX sequence.

If I am doing an online DPX conform, I don't want the editor to just export a DPX sequence for me, I want an auto matic creation of DPX files internally.

This is why large studios haven't switched from Smoke or Quantel and other big players because there is no true DPX management in Apple products.

Also part of the problem is memory, if I am working on a feature and have a bin with 60,000 or 100,000 DPX files, I have worked on projects where Apple Finder has taken a face plant when it sees that many files. Not all the time, but once in a while. Maybe when Snow Leopard comes out, DPX file management will be added since it will have so much 64bit memory?

Dunno.. my 2cents.