Graeme Nattress
RED Problem Solver
16bit tiffs are great. But they're big. That's what Frankie shot, and moving those files around was pain indeed. So glad we have R3D files now....
Graeme
Graeme
Welcome to our community
Be a part of something great, join today!
Gamma space...linear?
- Thread starter Luca Immesi
- Start date
Dan Hudgins
Well-known member
- Joined
- Feb 16, 2007
- Messages
- 1,369
- Reaction score
- 0
- Points
- 0
- Location
- San Francisco, CA USA
- Website
- www.dancad3d.com
Moving TIFs around...
Moving TIFs around...
Moving the files is a time issue, so in my RED ONE workflow I have come up with is to just stick them on the workdrives in a shot folder in my programs project structure, then you do not need to move them around.
Rather than move the files between computers on a network, I have found it is better to just format the work disks with FreeDOS and to unplug them from the XP Home SP3 computer (or mac) running REDCINE and plug them into the basic PC boxes for processing in batch mode in my programs. You "pre-trim" in RED CINE and change the output directory so that each shot goes to the right project shot folder. In my program's Edit list you can move the shots around and trim them, but those are just pointers so there is about zero time taken up since the TIF frames are not loaded or moved during editing (the key frame is loaded for grading, and the TIF are read for making the proxy frames but those are done once or in batch mode overnight).
It just takes a minute to un plug the harddrive, where as it takes hours to copy or move the frames over a network or between folders.
I think I have worked out a way to use the 2K and 4K TIF frames without too much cost or time... anyway it seems to be working so far.
I picked support for 48bpp TIF rather than 10bit DPX since you want 10 good bits after CC and if you just start with 10 you get histogram gaps in the 10 that come out after any curve adjustments.
Moving TIFs around...
Moving the files is a time issue, so in my RED ONE workflow I have come up with is to just stick them on the workdrives in a shot folder in my programs project structure, then you do not need to move them around.
Rather than move the files between computers on a network, I have found it is better to just format the work disks with FreeDOS and to unplug them from the XP Home SP3 computer (or mac) running REDCINE and plug them into the basic PC boxes for processing in batch mode in my programs. You "pre-trim" in RED CINE and change the output directory so that each shot goes to the right project shot folder. In my program's Edit list you can move the shots around and trim them, but those are just pointers so there is about zero time taken up since the TIF frames are not loaded or moved during editing (the key frame is loaded for grading, and the TIF are read for making the proxy frames but those are done once or in batch mode overnight).
It just takes a minute to un plug the harddrive, where as it takes hours to copy or move the frames over a network or between folders.
I think I have worked out a way to use the 2K and 4K TIF frames without too much cost or time... anyway it seems to be working so far.
I picked support for 48bpp TIF rather than 10bit DPX since you want 10 good bits after CC and if you just start with 10 you get histogram gaps in the 10 that come out after any curve adjustments.