Sugestions on how to reduce network render stitching time?

johnmeyer wrote on 8/1/2004, 1:21 PM
I haven't used network rendering since upgrading to Vegas 5.0b. Today I tried it for the first time. No problems installing, and the automatic file mapping is a big step in the right direction.

Thanks, Sony.

However, now that the render (91 segments) is complete, I am once again waiting for the darn thing to stitch together. The render of 1:30 (one hour thirty minutes) of color-corrected video (that was the only fX, and there was no compositing, etc.) took only a little longer than real time. However, it looks like the stitching is going to take at least forty minutes.

We had discussions, shortly after 5.0 was released, about various ideas for how to speed up stitching, or possibly even eliminate it.

Question: With 5.0b are there any hints or techniques for speeding up this mostly unnecessary step?

Ideas discussed before, but which 5.0 and 5.0a did not allow, included being able to specify the temp directory to a different drive (to speed the copy process that is part of stitching). The best idea was to create a VEG file that merely pointed to all the stitched files, and you could then print to tape or render to MPEG directly from this VEG file, thus eliminating the need for stitching altogether. That idea was posted here:

Liam_Vegas Stitching Idea


Comments

Liam_Vegas wrote on 8/1/2004, 9:41 PM
Hmmm... regarding that "veg" file instead of stiching idea.... did I send this in as a product suggestion? I have a sneaky feeling that... I FORGOT!!!

Oops!
johnmeyer wrote on 8/1/2004, 11:20 PM
Liam,

Definitely send it in. It is a brilliant idea and would save a TON of time.
Liam_Vegas wrote on 8/2/2004, 12:44 AM
Done