Comments

NickHope wrote on 10/11/2016, 12:29 AM

What version of Vegas?

 

trevorjharris wrote on 10/11/2016, 3:33 AM

Vegas Pro 14. Sorry I should have said.

NickHope wrote on 10/11/2016, 4:33 AM

This sounds like it might be related to the memory-handing bug(s) in VP14. https://www.vegascreativesoftware.info/us/forum/vp-14-win10-out-of-memory-problem--103767/ What OS are you using? What happens if you watch the Resource Monitor while it renders? See my post on that thread to see what to look for.

NickHope wrote on 10/11/2016, 4:35 AM

Also, the rendered file.... Is it the correct length but just flatlined after the first 20 mins? Is it silent after 20 minutes in other players? Does the waveform preview show it silent too?

trevorjharris wrote on 10/11/2016, 5:40 AM

Yes. I tried other players. I imported the file back into Vegas and I could see that there was no sound after about 20 mins.

trevorjharris wrote on 10/11/2016, 8:29 AM

Just tried exporting as a dolby aac3 file but got same problem.

Former user wrote on 10/11/2016, 8:31 AM

Does the waveform CUT out or FADE out?

trevorjharris wrote on 10/11/2016, 10:04 AM

The audio cuts out always on a clip boundary. The audio has not been modified in any way. I have found that I can render as 2 files by using the loop region. I can then join them together in Vegas Pro. It seems to have a limit on the number of clips in the track when rendering audio.

Former user wrote on 10/11/2016, 10:25 AM

AFAIK there is no limit to clips. Can you post a screenshot of the timeline and a close up of the clip boundary you are talking about?