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

What's the No.1 missing piece in the RED post software puzzle?

Nigel Stanford

REDuser Sponsor
Joined
Feb 26, 2008
Messages
347
Reaction score
0
Points
0
Location
wellington / new york
Website
www.rubbermonkeysoftware.com
Hi Guys, a bit of an open thread here. I've got a few ideas for new features / software to help smooth the Red post process, but want to get your thoughts.

What is the thing that takes up the most time in post? What's your pet peeve?
 
Converting from the R3D to 2K XYZ anything.
To read the R3D Nativity work with it and Color grade with it in say FCP Color or AE or something in expensive would be so special and be the biggest break threw in some time.

Once these things are figured out.
There is no doubt in my mind that Telecine houses and high end studios are going to feel the HIT.
 
The naming convention that red uses Is just not effective. I think if there was a way of baking Reel_Scene_take info from onset or during editorial/backup this would make life easier for picture and sound editors.
At the moment sound editors will get clips named A010_C005_080903.AIF and all they can do is reference that to a camera log and find the name of the slate from there.

Sound Devices and other audio recorders give slate info in the filename. makes life a lot easier.

I would like to See A010_SC34A_take003_.aif, even mic info or channel

A010_SC34_take003_CH1.aif this would still work fine for EDL conversions etc.

Thoughts?
 
I would make it tie in with standard camera log sheet . And get the 2AC to enter the clip name against the scene take info into a handheld device. Iphone or something then editorial can apply the data as the files are being backed up and imported into edit. Would be nice if there was wifi into the camera to accomplish this on set but maybe there is another way. the S-two systems do it from a handheld or laptop PC with a remote software which is pretty nifty.
 
as i mentioned in a other thread, it would be great to have a window with a list of the used files in the edl and by double clicking it, you will be able to do the onelight for example in RA to generate the needed RSX file...
also the header information on the dpx files at least the rollID should be edited to fit the rollID in the edl. I saw there problems when working with baselight 8.

thx
rainer
 
as i mentioned in a other thread, it would be great to have a window with a list of the used files in the edl and by double clicking it, you will be able to do the onelight for example in RA to generate the needed RSX file...
also the header information on the dpx files at least the rollID should be edited to fit the rollID in the edl. I saw there problems when working with baselight 8.

thx
rainer

Hi Rainer, those are Monkey Extract specific, I'm actually looking to see what other problems people have that we could perhaps solve with software.

But to your points, the DPX header rollID has already been completed and released in the latest version. The other idea is in development, and should be out in about a week. :)
 
fantastic, thats fast response.... thanks a lot... :)

saw the beta version on the page.... great.....

keep the good work....

rainer
 
The naming convention that red uses Is just not effective. I think if there was a way of baking Reel_Scene_take info from onset or during editorial/backup this would make life easier for picture and sound editors.
At the moment sound editors will get clips named A010_C005_080903.AIF and all they can do is reference that to a camera log and find the name of the slate from there.

Sound Devices and other audio recorders give slate info in the filename. makes life a lot easier.

I would like to See A010_SC34A_take003_.aif, even mic info or channel

A010_SC34_take003_CH1.aif this would still work fine for EDL conversions etc.

Thoughts?

We are actually working on a very elegant solution for this.
 
For me the missing piece is the Adobe Plug in.
Once that's out a whole new set of feedback will arise in the improvement of conforming software helpers.
 
We are actually working on a very elegant solution for this.

Do you have any plans to make it publicly available, Mark?

We are using Clipfinder for camera logging now - the comments section makes it easier to match audio and image files together, you can see the clip and listen to a reference sound file, and since you can save the document, it is easy to just keep the Clipfinder document with your directories of image files and port it anywhere. It has gone a long way towards eliminating our struggles with the RED naming conventions. Also, if you give the file a alternative name in the Clipfinder-provided "comments" section, you have the option of matching sound to that name, instead of relying on the RED naming conventions, which can be confusing and hard to decipher on the fly.

This is a good idea for a thread. I think we are all waiting on native R3D implementation in Adobe and Final Cut and would like to see ease of use integration with Color -- or, better still, the promised native R3D workflow.
 
I have no real complaints, as I sit here I am editing right now. I render my r3d files overnight to cineform and bingo, I'm ready to go.

If I had something I could wish for, I think it would be a product similar to Adobe BRIDGE that would read R3D files. So I could see what I have, move it around, etc.

That's my thought at this point.

Jay
 
This is yet another example of where an Apple Newton would be an ideal tool: fill out the log form on the Newton, with the camera info, then have a tool on the computer side to rename the clips after they are transferred, based on that log...

The Newton was too far ahead of its time and died an inappropriate death...

I like mine.
 
Back
Top