Hi,

Can anyone explain please (or tell me it doesn't matter) - what happens regarding colorspace when I use the batch file conversion option for R3d files (in this instance I'm using the HD 422(YUV) example).

If I should be choosing an input workspace curve in First Light to match the cineform file colorspace generated by the script, don't I need to know what that is? I did try to find out by looking at the custom script using the edit function as per the cineform note, but could not understand it.

On the subject of scripts and R3d conversion, when can we expect to see a menu based batch system (with all the options available in the command line version) , so that normal mortals can work flexibly with batches of files, without the need to understand command line syntax?

It is all handled by FirstLight / Active Metadata, you can use any output type, 422, 444, RAW And the colorspaces will be all matched. So it doesn't matter.

One do intend to replace HDlink one day with a tool designed for flexibly for file conversions (like ReMaster on the Mac.) R3Ds didn't fit in the existing conversion design of HDLink, so they put in scripts.

Thanks David,

If that's the case, what's the point of the various encode & decode options in the R2CF command line tool then?

Some are for controlling of the Active Metadata defaults, but those are non-destructive so you can change them in First Light. All for maximum flexibility. The main non-AM controls, resolution, color formating YUV, RGB, RAW, do have to selected by switches. Maybe I don't understand your original question.

That explains things fine thanks. I didn't appreciate that the options I mentioned (within the Red scripts) were metadata functions, which are of course non-destructive. So FL reads all this and allows me to change them. Great.

Should also add...

Good forum, good support, good product!