Welcome to our community

Be a part of something great, join today!

  • 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 :)

New Log & Transfer Crashing?

Great, thank you.

I noticed one thing, maybe my imagination, but does L&T takes longer with 16:9 clips?

If this is true, it would be a quicktime code issue, not an L&T issue. L&T does no
image processing, it's merely an interface tool.
 
If this is true, it would be a quicktime code issue, not an L&T issue. L&T does no
image processing, it's merely an interface tool.

I don't remember 2:1 footage L&T taking this long. My impression was it's about 5 times faster than encoding 1080 from REDCINE. It could be something to do with 3K/60p footage being ingested at 3K maybe.
 
works!

works!

works for me. no crashes. both r3d files checked - from build 15 and 16. L&T is working normally. i do not see longer transfer time that usual.

25 frames, 2:1 and 16:9. works normally.

thank you R3D team.


filip
 
WHOO HOO

put 60 clips in last night and no crashes, way to go team!! thanks
 
I used L&T for pretty large project yesterday (200GB worth R3D) and ingested the whole thing without a problem. With my 3Ghz x8 Mac Pro took about whole day to ingest them.

The clips look darker with L&T than proxies as somebody else mentioned and I'm thinking not worth the wait, so I'm leaning towards proxy editing more, but there's a playback issue with longer takes with proxy, so I probably have to combine the two. Was REDALERT! be able to create M size proxy?

It would be nice in L&T preference, if you can choose to ingest as various proxy sizes to over come this issue.
 
Back
Top