I think this must be a bug or an oversight.

Reported: [Ticket#2017121017000306] and added to the known issues post.

[[MENTION:72786]] interesting! yes I'd love a system where you could 'background prerender' stacks of clips or at least parts of some that don't contain transitions do do a little work when the system load is low to a more system friendly (intra) format, so that not all work has to be done at the final render, or when changes occur.

[[MENTION:undefined]] Nick, thanks for the Add & being on the ball, this could be important for the big family of Sony users.

--- this could be important for the big family of Sony users.

MAGIX users as well, as we're talking about Vegas Pro 15?

yes the one's using XAVC mostly being Sony cameras, former Sony Vegas now Magix Vegas, yes yes VP15

This was indeed an oversight. Parts of the current render dialog were written for Movie Studio 13 and then ported over to Vegas at a much later date. At the time that this section of the code was written, XAVC wasn't fully integrated into the software code base and thus removed from the pre-render options. We should have this remedied in one of the next few updates.

Thanks @VEGASDerek , very much appreciated! Besides the missing codecs, will be interesting to see if the whole background rendering mechanic can get a more functional overhaul; I think Edius is working on something there in their current V9..

Agreed. This function could be super useful. It needs a better system/algorithm for deciding what really needs to be re-rendered. For instance:

1) If you remove/add 2 seconds at the beginning of the timeline, the pre-renders should just shift with it (like ripples do).

2) If you make changes to a section and then re pre-render that section it shouldn't wipe out other pre-renders.

3) There should be a smart render - concatenate function to simply add all the pre-render files together to make the final render without re-rendering.

I have no idea how difficult this is to implement so maybe asking too much! But for anyone working on low powered systems it offers (IMHO) a great way to improve final render speed simply by altering your workflow. I often find that I have to pre-render or RAM preview in order to accurately judge my edits; it would be nice to utilize some of this CPU effort.

I was just having a day where a client would like all clips with a certain lut applied...I wished I could have 'prerendered' all clips whilst maintaining some file name integrity and then exported those as individual clips in an archive...but now, I'm rendering out one 35' clip in 4K and hope that my old mule doesn't crash in the next few hours...and then, what

 

Reported: [Ticket#2017121017000306] and added to the known issues post.

 

But when will this be solved?

It will be resolved in the next update, which will be coming soon.