|
|
06-25-2008, 01:41 AM
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.
06-25-2008, 02:02 AM
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....
06-25-2008, 02:17 AM
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.
06-25-2008, 02:24 AM
YES Deanan, you are absolutely right.... if you set the out point and leave RA it is not updated.... now it works fine.....
06-25-2008, 02:36 AM
The RSX updating for in/out is now better. It'll be in the next version.
06-25-2008, 10:17 AM
Thanks Michael.
Very Exciting, we'll be doing some beating on the process to check it out as im sure you've already done to death!
06-25-2008, 11:09 AM
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.Originally Posted by Deanan
I'll test again later this afternoon after a reboot to see if I can replicate it.
06-25-2008, 11:12 AM
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.
06-25-2008, 11:51 AM
Deanan, do you think the Automator actions for Qmaster could be added in the near future?
06-25-2008, 12:22 PM
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.
| « Previous Thread | Next Thread » |
