4k 16:9 in FCP via Log & Transfer

[Manuel Wenger]

I´ve a shooting coming up where we would like to go 16:9, since there is still the issue with broken Proxies in QT and Redalert, is it possible to import to FCP via log & transfer, or will that also show up corrupted ? Don´t have 16:9 r3d´s arround here to try out.

Manuel

 

[Kaku Ito]

I have finished editing in 16:9 with FCP and Color, but we kinda thought cool to provide RED 2:1 as 16:9 letterbox (16:8 if I may call it).
In this case, we brought in most of the clips via Log and Transfer, that will make the clips at 2048 x 1024 (16:8) and didn't have any corrupted files. We found out that when R3D files gets larger than 2GB and start to be saved in multiple files for longer clips, the proxy won't work in FCP.

When the editor used zooming then I looked into the in and out points then used the framing in the REDCINE to output 2048 x 1024 prores422HQ files to compensate the resolution.

If you wanted to do real 1080, then I would recommend to do simple cut edit in REDCINE then output as real 1080/Prores422HQ, then edit in FCP.

 

[James Brundige]

If you are distributing in 1080 for TV, you can shoot 2:1. Then color grade in Red Alert and export 16:9 Pro Res HQ to FCP. You crop a bit off the sides, but 2:1 seems to be more stable in the Red flow than shooting 16:9.

 

[Jerry Hofmann]

I have finished editing in 16:9 with FCP and Color, but we kinda thought cool to provide RED 2:1 as 16:9 letterbox (16:8 if I may call it).
We found out that when R3D files gets larger than 2GB and start to be saved in multiple files for longer clips, the proxy won't work in FCP.

I suspect that you have a 2 gb limit set in the file size limiting found in your Scratch Disk settings, or (just as likely) your drives are not formatted Mac OS Extended. If they are and there is no limit to file size set, you'll find that the system doesn't start breaking up larger than 2 gb files.

Jerry

 

[Manuel Wenger]

I shot several times in 2:1 4k wich worked fine every time, but in this particular case we really want to keep as much resolution as possible.

 

[Kaku Ito]

I suspect that you have a 2 gb limit set in the file size limiting found in your Scratch Disk settings, or (just as likely) your drives are not formatted Mac OS Extended. If they are and there is no limit to file size set, you'll find that the system doesn't start breaking up larger than 2 gb files.

Jerry

Jerry,

Be aware that RED is the one dividing files in the RED Drive. My system has nothing to do with.

 

[Kaku Ito]

If you are distributing in 1080 for TV, you can shoot 2:1. Then color grade in Red Alert and export 16:9 Pro Res HQ to FCP. You crop a bit off the sides, but 2:1 seems to be more stable in the Red flow than shooting 16:9.

We heard that 16:9 recording crashed at this point so we went with 2:1 recording, too. Hope it fixes on build 16.

 

[Justin McAleece]

Wtf 16:9

Wtf 16:9

We heard that 16:9 recording crashed at this point so we went with 2:1 recording, too. Hope it fixes on build 16.

still sucks big time for me. I cannot get audio or any QT based program to read the 16x9 4k and I think it's f'ing ridiculous. (i got screwed on this pretty hard on a shoot last week.)

we REALLY need this fixed ASAP. If the sensor cropped the sides and didn't offer an increased FOV vertically then this wouldn't be as much of an issue but sometimes I NEED that vertical height. PLEASE FIX THIS.