Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Why use Log and Transfer?

It was introduced before RR... It provided a familiar interface to those familiar with FCP workflow and digital media sources, but who were hesitant to work with the other RED tools.

At this point, RR is far superior, I see no reason to use L&T. However, once true R3D support does come for FCP, I believe it will be in the form of the L&T interface. Instead of transcoding to ProRes, it will simply take a few seconds per R3D file and wrap in a QT wrapper -- as is done with P2 DVCPROHD footage, for example. The L&T window for R3D ingest will probably allow for transcodes to ProRes and other codecs as well as leaving importing and working with native R3D data.
 
Jeff Kilgroe said:
It was introduced before RR... It provided a familiar interface to those familiar with FCP workflow and digital media sources, but who were hesitant to work with the other RED tools.

At this point, RR is far superior, I see no reason to use L&T. However, once true R3D support does come for FCP, I believe it will be in the form of the L&T interface. Instead of transcoding to ProRes, it will simply take a few seconds per R3D file and wrap in a QT wrapper -- as is done with P2 DVCPROHD footage, for example. The L&T window for R3D ingest will probably allow for transcodes to ProRes and other codecs as well as leaving importing and working with native R3D data.
Click to expand...

thanks, just wanted to make sure I wasn't missing something important.
 
As long as you do hard cuts only: none. If you need any effect (any!) go ProRes or it'll be a PITA…
 
You must log in or register to reply here.
Back
Top