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

RELEASED: BETA REDAlert! (v3.3.5)

BTW, The 2k dpx button on the main window is busted. It'll be fixed quickly.
 
Thanks Deanan!

There has been some nice ALE work in this release to get all the metadata into the post workflow. This does remove MetaCheater from the process, but for the better as both time of day and edgecode are tracked all through post and exported as needed as well as long and short file names so EDL's can be 4 or 16 as needed.

The whitepaper on the process will be available in a couple weeks. But in the meantime, I made a video that is now on YouTube that shows the basic steps.

http://www.youtube.com/watch?v=Q7m26ay6AB8

Since this was an early version, the UI may not look the same, as it is missing the audio work done by Deanan. If the source files have audio, be sure to check the audio compatibility box.

I have attached the Automator that I made that accesses the actions.

Michael
 
Damn it. I stll can't get attachments to work.

Michael

Just realized there is a 97k limit and my file is 200k. Sorry.
 
Great work! Cheers to both RED and AVID on this.
 
Michael,

Will this also work with a SD workflow? Redcine does not output Avid DV codecs in the latest build, but hopefully that will be back soon.


MichaelP said:
Thanks Deanan!

There has been some nice ALE work in this release to get all the metadata into the post workflow. This does remove MetaCheater from the process, but for the better as both time of day and edgecode are tracked all through post and exported as needed as well as long and short file names so EDL's can be 4 or 16 as needed.

The whitepaper on the process will be available in a couple weeks. But in the meantime, I made a video that is now on YouTube that shows the basic steps.

http://www.youtube.com/watch?v=Q7m26ay6AB8

Since this was an early version, the UI may not look the same, as it is missing the audio work done by Deanan. If the source files have audio, be sure to check the audio compatibility box.

I have attached the Automator that I made that accesses the actions.

Michael
Click to expand...
 
Has the Qmaster functionality been improved at all? i.e. can I submit a job to a multi-node cluster and have Qmaster figure out which node to send it to? Or do I still have to have one cluster per machine and specify which machine I'm sending each render to?

pretty please... I'd love Qmaster to do the distribution work for me. (I still haven't figured out what, if anything, the 'Nodes' option does)

And... would it be possible to add Qmaster to the Automator actions?
 
It's very hard to provide good Qmaster functionality because the hooks to do so are just not there.

The nodes option lets you split up a render into multiple qmaster submissions. If you have 100 frames to render and 5 in the nodes field, then 5 jobs get submitted with 20 frames each. Unfortunately QT transcodes can't be split up because the quicktimes are rendered in one pass. It's possible to it like compressor does but we're not there yet.

Qmaster should be possible from Automator actions.
 
When I use the REdrender Action it seems it reads the IN-Point of the RSX file, but not the OUT-Point..... Mac didn't stop to render out DPXs.... :)
When you select the DPX output option, the Quicktime codec should be not highlighted.... but the new tools are great... really great....
 
If you just set the in/out points in RA, then the out point may not have been written to the file yet. Try doing something else in the UI to force the update... like stepping one frame forward or scrubbing.
 
YES Deanan, you are absolutely right.... if you set the out point and leave RA it is not updated.... now it works fine.....
 
The RSX updating for in/out is now better. It'll be in the next version.
 
Deanan said:
The RSX updating for in/out is now better. It'll be in the next version.
Click to expand...

Maybe this would fix the problem I've had which is an h.264 render that looped over the first frame for the length of the in/out clip I had selected. Like it knew how many total frames it was supposed to deliver.. or it was stepping to the out frame, but it kept rendering the first frame over and over. This was after an initial render was successful. I went back to tweak settings and the subsequent renders had this 1st frame looping problem.

I'll test again later this afternoon after a reboot to see if I can replicate it.
 
REDline multithreading performance doesn't seem to be great. We're seeing much better performance running four instances set to use two threads each vs. one instance set to use 8 threads.

Not a big deal if you're processing a large number of short shots through Qmaster, but when you have one hour-long shot (like we did for an art project we were working on last week) it's sort of a hassle. Though I guess we could segment long shots by frame ranges, render them out to four different QuickTime movies, and then combine them all at the end.
 
Chris Kenny said:
REDline multithreading performance doesn't seem to be great. We're seeing much better performance running four instances set to use two threads each vs. one instance set to use 8 threads.
Click to expand...

Hi Chris,

We haven't had a chance to optimize it yet but we're working on that now. We wanted to get the functionality out quickly first.
 
You must log in or register to reply here.
Back
Top