Vegas 16 - Failure to Render AVHDC video clips

jtczere

Member
I shoot theater plays, around 2hrs long. In the past I was using Vegas 13/14 and could just pull the 1080 60P clips onto the time line, add title and then using the "Tools" drop down "Burn DVD" command go ahead and burn the 2hrs on to an 8.5 GB DVD+R DL disc. A few hours later I would have my finished DVD and could then make copies.

I installed Vegas 16, and now the rendering of the "Burn DV" stops any where from 3% to 71% completed on the burn. I have uninstalled and reinstalled the V16 software as well as having installed on two different computers...same problem with both computers.

When the "Burn DVD" command is given, the format changes from 60P to 29.9 Interlaced, with the older Vegas (12/13/14/15) this was not a problem and I could get the "Burn DVD" command to work.

I have also tried to just "render" the clips using render Main:embarasseConcept MPEG-2, same problem occurs.

Any ideas how to fix this problem.
 
I have not upgraded to Vegas 16 but I know that having the temp folders on drives with lots of space is important.
 
I shoot theater plays, around 2hrs long. In the past I was using Vegas 13/14 and could just pull the 1080 60P clips onto the time line, add title and then using the "Tools" drop down "Burn DVD" command go ahead and burn the 2hrs on to an 8.5 GB DVD+R DL disc. A few hours later I would have my finished DVD and could then make copies.

I installed Vegas 16, and now the rendering of the "Burn DV" stops any where from 3% to 71% completed on the burn. I have uninstalled and reinstalled the V16 software as well as having installed on two different computers...same problem with both computers.

When the "Burn DVD" command is given, the format changes from 60P to 29.9 Interlaced, with the older Vegas (12/13/14/15) this was not a problem and I could get the "Burn DVD" command to work.

I have also tried to just "render" the clips using render Main:embarasseConcept MPEG-2, same problem occurs.

Any ideas how to fix this problem.

If it's consistent behavior, it sounds like a bug. You probably want to report it to MAGIX.

https://www.magix.com/us/support/technical-support/
 
Back
Top