Greetings all,

I'm a new user of Prospect HD (trying it out), and rather than asking a long laundry list of questions, I'll just lay out how I assume things are working, and somebody in the know can correct me where I might be wrong. My main concern in this is that I want to make sure I'm always working in a 10 bit workflow.

What I'm using: Prospect HD, PP CS3, AE 7.
File types: AVCHD, converted to CF.avi using HDLink

I grab the MTS files from my camcorder and convert them to CF .avi using HDLink. Import the files into PP CS3 and edit, then export in the CF format. Import into AE 7, edit and export in the CF format.

Two specific questions I have are, When working with CF intermediate files in PP CS3, does 'Maximum Bit Depth' need to be ticked in the project settings to assure 10 bit processing? Next question is, when importing the then exported files from PP CS3 into AE 7, is this a transparent CineForm import due to the CFHDIO.aex plugin? Or should I see something 'telltale' happening?

The funny thing about it is, there seems to be no difference in importing CF files even when I (for experimental reasons) remove the CFHDIO.aex plugin from my AE plugins folder. Shouldn't I not be able to import CF files without that plugin in there?

If you remove the CFHDIO.aex, it falls back to using the 8-bit Video for Window decoder. You don't need to check 'Maximum Bit Depth', unless you are using Adobe exporter. CineForm exporters use the depth control in the playback settings (the 32-bit float option.)

Sorry for the brief reply, on a shoot today.

Thank you for the timely reply, David.

Based on what you've said I would assume I'm in the clear provided that:

1. Prospect HD is installed (CFHDIO.aex available in AE plugins)
2. I am using a CineForm Preset when editing in PPCS3 and exporting in CF format.

As long as CFHDIO.aex in loaded with AE, CF files will be imported at 10 bits automatically and transparently rather than defaulting to the VFW 8 bit import.

What made me wonder is that there seemed to be no difference when importing CF.avi files into AE with or without the CFHDIO.aex loaded, (i.e. scrub, render, and RAM preview times seem to be identical regardless). I may have been erroneously biased to expect something different because of the CF Render Engine used in PP when using a CF Preset. And I wasn't sure if CFHDIO.aex instanced any sort of visible UI or added a context menu for a user requested import option (i.e. CF Import vs. VFW import).

In short, the import process to AE is completely transparent.

Mostly transparent. The Interpret footage "more Options" is available if you have the CFHDIO.aex module active.

Now that the Prospect HD installation has been fixed, I get the CineForm Loader UI when launching AE, and also the 'More Options' dialog is now available.