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

Red Tools

im.thatoneguy said:
khmuse made me think of one other thing to request.

Ideally I would like for this tool to be a bucket full of command line modules. That way if someone needs just the EDL parsing subroutine they could integrate it into say a Nuke TCL script. It would also allow modules to be swapped out and used interchangeably with RED's features as they develop and... IMPLEMENT A COMMAND LINE REDCINE HINT HINT... (nice and subtle huh ;)
Click to expand...


Oooh, oooh, yes!! Command line! Yes!!!
 
RED has maintained that tools which assist in data management are part of "conforming" and that they won't touch it.

I strongly disagree with that position and I wouldn't expect them to include support for anything beyond full clip pull list support. Which is ok... but still exporting a 4 minute clip for a 5 second take is not in my opinion part of conform.
 
im.thatoneguy said:
RED has maintained that tools which assist in data management are part of "conforming" and that they won't touch it.

I strongly disagree with that position and I wouldn't expect them to include support for anything beyond full clip pull list support. Which is ok... but still exporting a 4 minute clip for a 5 second take is not in my opinion part of conform.
Click to expand...

Gavin -

You can beta Red Tools in Jan. for me if you want.

My preliminary tests now make me 99% sure I can pull this off.
 
We highly recommend not writing tools to truncate or trim r3d files at this point. Things are still in flux with both metadata and file structure as we
continue to refine the camera and software. It's almost guaranteed
to break various parts of current or future software releases.
 
Deanan said:
We highly recommend not writing tools to truncate or trim r3d files at this point. Things are still in flux with both metadata and file structure as we
continue to refine the camera and software. It's almost guaranteed
to break various parts of current or future software releases.
Click to expand...

Deanan -

100% understood. And this (IMO) is the primary reason there is no SDK or command line tools released that many here want.

I know there will be more meta-data (don't have audio yet, or iSeries, etc.) AND I know you are going to make changes - (I got a few ideas I will email you offline for a change or two that IMHO would be very strategic) - AND I want to LINK and ADD my own meta-data ... so ...so I have TWO choices -

#1: Wait. Discover and create workarounds and hacks to get done what I need to get done. And ASSUME I will get all the tools I need for professional work-flows and data management from Red. Or ...

#2: Design and (try to) build a foundation for a tool set - and in that process, provides feedback to Red.

As I said in my original post - the TRIMMING r3d would be the LAST thing I would do - because I am sure you are going to make a few changes (and yeah, I got a few suggestions)

Just being able to COPY only the .R3D FOILDERS USED IN AN EDL to another volume will get me VERY far for a while - and you can NOT parse an EDL and do that without a DATABASE of meta-data - and one needs to design that to CHANGE and SCALE.

Bottom line, if I manage to have an impressive "proof of concept" - I would obviously show you first.

And again ... I could fail. Much of this revolves around a programmer I am seducing into coding for me starting Jan. 3rd - so, it is still possible that I will not have the resources to do this - if that happens - I'll just keep thowing ideas at you.

I do think that NOW is the time to work on a design and foundation for these tools because you ARE still changing spec/file/data - so, feedback saying - "if you guys could put a tag here or a value there - then I could do this" -

I have two feature films shot 100% on Red in post under Offhollywood's roof - so, it's pretty clear to me what could empower the workflow potential of Red.

I'm not trying to cause any trouble. I am just trying to help.
 
Deanan said:
We highly recommend not writing tools to truncate or trim r3d files at this point. Things are still in flux with both metadata and file structure as we
continue to refine the camera and software. It's almost guaranteed
to break various parts of current or future software releases.
Click to expand...

I am certain that you are correct that a haphazard approach to "hacking" up .r3d files would "break" things down the road. However, there must be a header that represents the minimum necessary information if footage shot today is going to be usable by future tools. It would seem that as long as people are only reading their current .r3d files and generating a new truncated output, then about the worse thing that could occur is to force them to go back to the original versions. A simple command line tool that allows one to name an input file, name an output file, set an input frame and set an output frame is an essential tool. We already have one user here that is reporting a working (at least partially) tool, others (including myself) have spent time looking into .r3d files to try to learn the structure of the header and confirm the frame boundaries.

I too am not trying to cause problems, but this is something that I will need very soon. Again, I agree, hacking up original files is foolish, but creating new ones that might or might not work in the future seems a reasonable interim solution.

Kevin Halverson
 
im.thatoneguy said:
Since when were those mutually exclusive? ;)
Click to expand...

LOL!
We are building a "proof of concept" of RED TOOLS to show the gang at Red.
Design is done. Xcoding has begun.
Until that's done (assuming I pull it off) - I am going to "lay low" off of this thread.
Cross your fingers ... back on this thread mid-Jan.
 
im.thatoneguy said:
Wait a second Xcode? Why aren't you doing it in a cross platform environment?
Click to expand...
Just to drive you crazy.

Actually, Xcode is the fastest way across the finish-line with resources I have and to quickly get the GUI I want. And I have one PC and 20 macs.

Don't worry, if I do something exciting, I'm sure we can port it to the dark side for you.
 
Gnu

Gnu

if you're going to GNU left/right the source, i'll thrown down with some perl/csh/bash hacking. especially if you're going to target linux. maybe even some hard-core fortran or C..
 
Mark,

This is a most excellent endeavor despite a file spec in flux. Since I will be in DIT mode for two months starting Jan 18th, I would be most pleased to help beta this on a PC. I wouldn't attempt to actually use it in my pipeline but as a side project.

Best,

Michael
 
im.thatoneguy said:
Linux is going to be highly desireable for people who want to integrate it with render farms and the like.
Click to expand...

ah my dream of a yellow dog super cluster.... ahhhh
 
You must log in or register to reply here.
Back
Top