VEGAS Pro 18 Update 1 (Build 334)

[Ron Lindeboom]

That’s funny, James, I got called yesterday with apologies for your overstating of things and stating that the last thing Magix wanted was for us to turn off the VEGAS Pro forum here. You might want to dial it back a few decibels.

Best regards,

Ron Lindeboom
Co-Founder, Creative COW

[Steve Rhoden]

Also the other thing that you fail to realize James Ollick, is that Moderators like myself and many experienced users do participate actively on both this forum and the Magix Vegas official forum!

Anyway back to the topic at hand. Steve, does this error pops up only when you have MP4 content on the timeline? And what are your render settings?……. Many settings were tweaked in this update for Vegas to automate itself more based on individual system specs, so this may be the cause of your issue and can be adjusted to get this error to go away.

[James Ollick]

Good to hear Steve. I see your posts on both platforms. Have a blessed day.

[Steve Shelton]

Hi Steve, thank you for asking. There will probably be other MP4s in the timeline yes but as the fault has been intermittant on a number of .veg renders I haven’t been keeping a close eye on it, as said they all render fine, if I get this error, if I then close the sony vegas and open up the same .veg file again (it’s like the old IT support answer of have to turned it off and back on again!). I have only been using 2 rendering formats with this update XDCAM EX for what I call lossless submixes and MAGIX AVC/ACC MP4 for general finished viewing. I’m in the UK so I use 25 fps and keep to 1080p but everything else is as per default. In my timeline, as well as the XDCAM mp4s, I have been using some 3840x2160x32 intermediate .mov (created in and rendered from a sony vegas .veg) as it seemed the easiest way to do zoom ins for items that contain one feature lots of other moving videos embedded in. Thing is this never caused any problems before the update; I was using the same files.

[Steve Rhoden]

With what you have mentioned then, that could be a Vegas memory leak issue somewhere.

Your best solution then is, after you finish your editing and saving your project, you simply restart Vegas and do your rendering….. Surprisingly that is my workflow everyday, although im not having the issue you described, but i find that’s the best way to have flawless renders in Vegas. You see, during your edits and ram preview etc, etc. memory gets depleted dramatically and if you go directly into rendering without a restart, you know you can get errors….. So try that method, even if you did not have that issue, its the same i would recommend.

[Steve Shelton]

Thank you Steve for your time and having a think about this. In fact that makes sense as I often had to do that on my old laptop (8Gb ram) with an older Vegas version as it would often crash midway through a big veg file render but be ok with a reboot. My new workstation has 32Gb ram and a 6 Gb video card for GPU so I thought I’d be OK! That said it’s good and interesting for intermediates like me to know what the experts do with tips and techniques like that – reboot before big renders. I’m ok at living with that, as at least if it ever has this issue it stops the render straight away rather than wasting time getting halfway through it and Vegas reboots quick enough which, as you say, is probably a habit I should think of doing regardless! Thank you very much.

[Steve Rhoden]

You are most welcome….