[Help] Exported Video has Audio Cut Off On Last Frame | Vegas Pro 14

Hoaxx wrote on 2/2/2017, 11:21 PM

I am exporting a short video clip that I want to be able to play seamlessly when looped in a video player.

The issue I'm experiencing is that the last frame of my exported clip does not have audio - it's muted / cut off. 

I do have the Fade Out Offset on the audio clip set to 00:00:00. Are there any other settings (Preferences or Track FX) that might cause a cut off to the (exported) audio?

Sometimes there is also a pop / click / glitch noise right at the end as well (noticed it in 44100Hz files, whereas 48000Hz seem to be free of the pop - still cut off though). The click is audible when played in a player as well as when imported back to Vegas.

Additional Info: 
FPS for project and export are matching (@25), and the end of the sound clip is aligned with a frame in the timeline. Settings also match the source file as closely as possible (bit rate and depth of source file exceed those of Vegas').

The only workaround I found so far is to export with several additional frames and trim the clip with 3rd party software, but that is a cumbersome solution.

I have put together an example project (Sony Vegas Pro 14.0), download link below. I have exported the first segment in the timeline and reimported it further to the right. I marked the frames in question - the last frame of the source track has audio, in the reimported part it does not.

Hope someone can help me with this. 

Project files: https://mega.nz/#!AMFDGJKD!q8bZ1UqHakoNeCgVTT11el0lBWJm9KZdlE2YU7QKBtg

 

Software: Sony Vegas Pro 14.0

OS: Windows 10 x64

Comments

Marco. wrote on 2/3/2017, 2:48 AM

What are your export settings?

NickHope wrote on 2/3/2017, 4:10 AM

I can confirm this with a 1080-25p 44.1kHz MainConcept AVC render and it's worse with a Sony AVC render. I've seen this before with AVC and possibly other long-GOP formats too. I've come to mostly ignore it, but it's definitely a bug. An uncompressed AVI renders the audio correctly.

NickHope wrote on 2/3/2017, 4:29 AM

Worth pointing out that exactly the same error occurs with both those encoders in VP13. Also that it's not an exact frame that has no audio. It's between 1 and 2 frames.

Musicvid wrote on 2/3/2017, 7:50 AM

Padding to align ends with an empty event is SOP at this house; with some TS source you might need 2-5 frames.

For player looping AVC/h264, render 0 b-frames with Fast Start or Web optimized ON.

You will never see seamless looping with long-gop source.

Hoaxx wrote on 2/3/2017, 3:00 PM

Padding to align ends with an empty event is SOP at this house; with some TS source you might need 2-5 frames.

For player looping AVC/h264, render 0 b-frames with Fast Start or Web optimized ON.

You will never see seamless looping with long-gop source.

Does "SOP" = Standard Operating Procedure? (English is not my first language... ) - i.e. my workaround actually is a valid approach?

What are "b-frames", "Fast Start", "Web optimized ON" or "long-gop source"?

"You will never see seamless looping"

I add an ample amount of frames at the beginning and at the end, then trim with FFMpeg and stitch the result, again with FFMpeg into a long clip. Result is seamless. I hoped I could do without trimming, but now that I figured out a workflow, it's no real bother anymore. I just have to figure out what i-frames are I guess, as those were mentioned in regards to the method a lot.