Trim r3d files

[Gavin Greenwalt]

So it's been 2 years since we were promised r3d trimming "soon" and the community efforts were stuffed.

Are we any closer to getting this?

It would be very very helpful. There are so many areas where having a full r3d file isn't useful such as VFX where you only need to send out or receive a single take or partial take but still have to ftp or fed-ex a drive for 10 seconds of footage spread out across 50GB of r3d files.

I guess I don't need to itemize all the applications of r3d trimming. They're the same as they were 2 years ago.
:beatdeadhorse5:

 

[Kwan Khan]

One More Vote For r3d trimming request...

 

[mikeburton]

Me three.

 

[N_Villers]

I'll jump on the trimming bandwagon too.

 

[Oliver Skibbe]

R3D trimming (and renaming) is desperately needed for documentary and archival footage.

 

[Gunleik Groven]

yup. needed.

G

 

[Peter Arnold]

Oh yes. The sooner the better.

Peter

 

[Nick Shaw]

Another vote here.

…VFX where you only need to send out or receive a single take or partial take but still have to ftp or fed-ex a drive for 10 seconds of footage spread out across 50GB of r3d files

But don't forget, you don't need to send 50GB for 10s from one take. Only the single relevant 2GB R3D is necessary. I know 2GB is still a big file to FTP, but it is possible, and Nuke, for example, will happily read from a single R3D.

 

[Johnny Friday]

YES!! R3D trimming, ability to rename if you want, and to keep the original file name.

AND---how about since you guys have so much time on your hands (almost finished with redcine-x and new firmware builds)...how about an archival program that can read r3d footage, make small proxies from each for viewing and archival sending pointers out to where they are stored? just saying----i got 10TB of footage and a crazy log on file maker pro.

 

[Gavin Greenwalt]

Another vote here.



But don't forget, you don't need to send 50GB for 10s from one take. Only the single relevant 2GB R3D is necessary. I know 2GB is still a big file to FTP, but it is possible, and Nuke, for example, will happily read from a single R3D.

The 10s isn't one take. I was exaggerating but not by much. We just worked on a sequence with 23 cuts. The edit pulled from many different takes.

So shot 1 might be 30 frames long but still need the entire r3d from that take. It's smaller to just send uncompressed in that instance. The longest cut was about 20 seconds long I think. When you have a lot of quick cuts from a full day of shooting you might need just about every r3d for only a few seconds.

 

[Martin Weiss]

In the Red Day thread it was mentioned that R3D trimming was not too far away.

Time to rejoice

 

[Martin Weiss]

EVA FRANKA ALEKSANDRA WEISS

(Sorry about that, but after a lot of patience my 4-year old demanded to be allowed to write something as well...)

 

[Paolo Tinari]

EVA FRANKA ALEKSANDRA WEISS

(Sorry about that, but after a lot of patience my 4-year old demanded to be allowed to write something as well...)

Hey Eva! :seeya::seeya::seeya:

OT finally an official voice regarding the R3d trimmer, those many threads about it were not unheard then

 

[Gavin Greenwalt]

In the Red Day thread it was mentioned that R3D trimming was not too far away.

Time to rejoice

Hip Hip!