What files does Log & Transfer reference?

[Rob Powell]

Prior to build 16, L&T seemed to reference the _H proxies bringing in files that corresponded to those pixel dimensions (e.g. 4K r3d = 2K ProRess). I just tried the new L&T for build 16 today on a 3K file and ended up with a 3K ProRess file in my FCP browser. Is L&T now referencing the _F proxies or the r3d to create the new files. If so, that would be great.

I just need to know how this will work to be able to communicate with clients re post workflow.

P.S. Please hurry with an audio solution. Clients seem to be buying into the benefits of RED production, but audio is still a major stumbling block in post.

R. Powell

 

[Rob Powell]

My bad. Found the answer in the L&T release history notes.

 

[Reinhart]

Prior to build 16, L&T seemed to reference the _H proxies bringing in files that corresponded to those pixel dimensions (e.g. 4K r3d = 2K ProRess). I just tried the new L&T for build 16 today on a 3K file and ended up with a 3K ProRess file in my FCP browser. Is L&T now referencing the _F proxies or the r3d to create the new files. If so, that would be great.

I just need to know how this will work to be able to communicate with clients re post workflow.

P.S. Please hurry with an audio solution. Clients seem to be buying into the benefits of RED production, but audio is still a major stumbling block in post.

R. Powell

I see you answered your own question, but just to be absolutely clear, the L&T does not use the QT proxies at all. It only accessed the R3D files. As for ingest sizes, 4K clips will ingest at 2K (FCP restriction.) Anything smaller than 4K (e.g. 3K, 2K, 1K, etc.) will ingest at native size. 4-channel audio is included in the ingest as of the last release.

Craig