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

Transcoding Software/Workflow

munchausen

Member
Joined
Sep 19, 2008
Messages
9
Reaction score
0
Points
0
Okay, Fearless Readers,

You have advised me one and all to transcode the Redcode files myself, but now the question is: what software should I use to transcode the Redcode files and what should the destination file format be if I'm trying to edit in Final Cut Pro (and want to be able to relink them back to the Redcode files later on)?

Redrushes? Redalert? Redcine? I have a feature's worth of footage (3.2Tb), so I need a batch-based solution.

Note: I DO NOT need to do a preliminary color grading at this stage - I simply want to transcode the files to a format that can be readily edited on a Macbook Pro.

Thanks in advance,

T
 
Okay, Fearless Readers,

You have advised me one and all to transcode the Redcode files myself, but now the question is: what software should I use to transcode the Redcode files and what should the destination file format be if I'm trying to edit in Final Cut Pro (and want to be able to relink them back to the Redcode files later on)?

Redrushes? Redalert? Redcine? I have a feature's worth of footage (3.2Tb), so I need a batch-based solution.

Note: I DO NOT need to do a preliminary color grading at this stage - I simply want to transcode the files to a format that can be readily edited on a Macbook Pro.

Thanks in advance,

T

USE REDRUSHES!
 
Try Clipfinder 2.0.2 and Redrender to 720X576 Prores HQ for PAL or 720X480 for NTSC using debayer quality of 1/8th for offlines. This provides the quickest transcode times for me on a Macbook Pro - about 15% faster than Redrushes with the same settings.
 
I simply want to transcode the files to a format that can be readily edited on a Macbook Pro.

Well, there you go. Your first 3 responses give you 3 completely different answers. Any one of them will work. Pick your poison.

Here's another tip that in your case is a bit late. Always convert files as you shoot. Never let it build up to the point where you now have 3.5 TB of R3d files and have to ask what you should do with them. The answers you get as to how to handle that will never even come close to matching your likely expectation that it will be quick, easy, and efficient. Because it won't be, not with 3.5 TB of files staring at you. But it might have been if you had converted the 150GB or so you probably shot each day. Something to keep in mind next time.
 
Try Clipfinder 2.0.2 and Redrender to 720X576 Prores HQ for PAL or 720X480 for NTSC using debayer quality of 1/8th for offlines. This provides the quickest transcode times for me on a Macbook Pro - about 15% faster than Redrushes with the same settings.

Russ, do not see and option with my current Clipfinder 2.0.2 that has the Redrender. Can you point me to this? Lim
 
Redrender is one of the RED Automator actions. Load up Automator, look in the movies section. Drag across and save as a workflow. Point to this workflow from 'Run workflow with selection'. The help section of clipfinder documents this pretty well.
 
Redrender is one of the RED Automator actions. Load up Automator, look in the movies section. Drag across and save as a workflow. Point to this workflow from 'Run workflow with selection'. The help section of clipfinder documents this pretty well.

Thanks Russ. Does this workflow ie through the Automator, include Audio? Lim
 
Clipfinder?

Clipfinder?

Russ, do not see and option with my current Clipfinder 2.0.2 that has the Redrender. Can you point me to this? Lim

Is Clipfinder a Red download? If so, I can't find it...
 
Huh?

Huh?

Redrender is one of the RED Automator actions. Load up Automator, look in the movies section. Drag across and save as a workflow. Point to this workflow from 'Run workflow with selection'. The help section of clipfinder documents this pretty well.

And what is "Red Automator"?
 
Thanks Russ. Does this workflow ie through the Automator, include Audio? Lim

I'm not sure if ClipFinder uses REDline or not, but anything that does will have audio support. Likewise, they'll all have similar render times. (if you're seeing different render times with REDrender vs REDrushes, it's because RR is doing two files at a time and sometimes the output disk can't keep up).
 
I'm not sure if ClipFinder uses REDline or not, but anything that does will have audio support. Likewise, they'll all have similar render times. (if you're seeing different render times with REDrender vs REDrushes, it's because RR is doing two files at a time and sometimes the output disk can't keep up).

Deanan, it is using Automator with RedRender. Will test . Yes, RR doing two files is definitely slower than if we do one at a time. This is so when using MBP even with using attached Esata connected RAID 0 drive through express card. Is there an option to do one file at a time? Lim
 
Deanan, it is using Automator with RedRender. Will test . Yes, RR doing two files is definitely slower than if we do one at a time. This is so when using MBP even with using attached Esata connected RAID 0 drive through express card. Is there an option to do one file at a time? Lim

I can add an option to set how many renders to do in parallel. When I tested it, I got better performance with two but that could certainly vary with how your system is setup (ram, disk speed etc) and what resolution you're outputting to.
 
I can add an option to set how many renders to do in parallel. When I tested it, I got better performance with two but that could certainly vary with how your system is setup (ram, disk speed etc) and what resolution you're outputting to.

Deanan, that will be great -Lim
 
When I'm using RR on a MacPro without a RAID, I get better speeds by rendering from one SATA-disk to another one. With a small RAID it doesn't seem to matter much.
 
Hmmmm...

Hmmmm...

Well, there you go. Your first 3 responses give you 3 completely different answers. Any one of them will work. Pick your poison.

Here's another tip that in your case is a bit late. Always convert files as you shoot. Never let it build up to the point where you now have 3.5 TB of R3d files and have to ask what you should do with them. The answers you get as to how to handle that will never even come close to matching your likely expectation that it will be quick, easy, and efficient. Because it won't be, not with 3.5 TB of files staring at you. But it might have been if you had converted the 150GB or so you probably shot each day. Something to keep in mind next time.

Frankly, we were too run-and-gun to possibly transcode as we went, unfortunately. Cameraman, producer and actor/director on a three-week odyssey across the country.

This is why we're doing it now.

But thanks for the heads-up - the equivalent of doing actual dailies (or something like it). You would obviously have to transcode as you go if you were to take advantage of having an editor on set. Next time I do a feature with a budget, it's definitely what I'll opt for.
 
Back
Top