Rendered Video & Audio out of Sync from Vegas Pro 13 b545

Cliff Etzel wrote on 7/4/2017, 10:18 AM

Once again, at one of those critical points in meeting a deadline, Vegas has shown a side of itself again that has kept me away from using it for several years. I rendered out a video using both the Vegas2Handbrake script and directly rendered using one of the internet MP4 templates - in all instances, the video and audio are out of sync - even though on the timeline everything is in sync. I exported out the Vegas project to a Premiere Pro project file, opened the project in PPro CS6, rendered out the videos and low and behold - perfect video & audio sync.

If I were using nothing but Vegas, I'd be S.O.L. in delivering on time. Now I'm back to PPro CS6 as the random crashes in Vegas along with this have me questioning my decision of committing fully to Vegas.

Now to investigate Media Composer First in addition to using PPro as it seems stability and reliability supersede ease of use.

If anyone has a suggestion in finding a fix for the out of sync video and audio issue I'd appreciate it. I thought I could finally settle on Vegas Pro - instead I'm back to where I was a couple of months ago for my post production tools. 😞

Back to post

Comments

Cliff Etzel wrote on 7/5/2017, 12:39 PM

Looking at the Vegas build number I assume you are using a Magix version of Vegas and not Sony's last version. Have you tried downloading VP14 trial and open the same project with it?

Since it worked before, was there a driver update since?

@OldSmoke - you are correct in that I'm using the Magix build of Vegas Pro 13 - build 545. I reverted back to what's been thought to be the best nVidia Quadro driver on my laptop (I'm having to edit remotely this week) - 297.03 driver to be precise. I've been able to reproduce the issue in the latest VP14 trial I downloaded. What confuses me is that Vegas2Handbrake has worked beautifully for me and now I'm experiencing the audio drift issue. I'm needing to edit a revision for another client project and I'm kind of left scratching my head. I exported out the Vegas project to a PPro project file and now PPro is crashing if I do anything to the clips like try to copy them to a new sequence. I'm totally flustered as I REALLY don't want to edit in PPro any longer - it's cost me a fair amount of time recently and is the reason I am trying to stick with Vegas Pro. I'm hoping when VP15t is released that there has been some serious overhaul of the code (even redo the code completely to make it rock solid) to make it first in its class as an NLE.

I'm stuck right now...

Marco. wrote on 7/5/2017, 2:55 PM

Any chance to share such a clip with drifted audio?

Cliff Etzel wrote on 7/5/2017, 3:22 PM

Here's a 6 second excerpt - do you see the audio drift while the subject is speaking?

https://vimeo.com/224376195/e91e6fe8df

Marco. wrote on 7/5/2017, 3:31 PM

Hardly. When I look closely to the part where he says: "personal" the "p" seems to be pretty perfectly synched, maybe audio 1 frame before video but it is really hard to see this way.

No chance to upload an original Vegas Pro MP4 output, best would be together with the original source file?
It needn't be out of this project but it would be much more helpful to have the media files on the own system rather then watching an online presentation.

Former user wrote on 7/5/2017, 3:39 PM

Looks right on to me.

Cliff Etzel wrote on 7/5/2017, 3:41 PM

Grrr... I think the client must have had something wrong on her end... She convinced me the video has drifting audio but now that I rewatch, I don't see any audio drift... THANKFULLY!

Back to using Vegas - I'm a happy shooter/editor again.

xberk wrote on 7/5/2017, 4:06 PM

Lip sync is really hard to see with some people (talking heads). I learned to do it on a moviola long ago. Sync in those days was not exact and to some degree a matter of judgement. Now we are slaves to the waveform of the camera audio (which we assume is dead on) But I think you still have the option of throwing something out a frame or two to make it look right.

As to "drift" .. It must be a problem with "dual audio" as you call it because PluralEyes now corrects for it. So I assume some NLE's combined with certain recorders have the problem on longer takes .. But it was never a problem for me using my good old H1 Zoom on takes up to an hour long and using good old PE 2.

Cliff Etzel wrote on 7/5/2017, 7:20 PM

Lip sync is really hard to see with some people (talking heads). I learned to do it on a moviola long ago. Sync in those days was not exact and to some degree a matter of judgement. Now we are slaves to the waveform of the camera audio (which we assume is dead on) But I think you still have the option of throwing something out a frame or two to make it look right.

As to "drift" .. It must be a problem with "dual audio" as you call it because PluralEyes now corrects for it. So I assume some NLE's combined with certain recorders have the problem on longer takes .. But it was never a problem for me using my good old H1 Zoom on takes up to an hour long and using good old PE 2.

Well, each of the takes from the video weren't more than a couple of minutes at most and I'm using PluralEyes 3.5 and it supposedly does correct for drift. I process my clips in PE3.5 first before ingesting into Vegas or PPro btw. I think it's some wonky thing for the clients end because as I watch the clips on the timeline, they appear to be in sync in addition to outside any NLE. I reviewed a couple of other projects I recently edited in Vegas Pro - no drift whatsoever so not sure what the deal was with this particular project.

I eagerly await the announcement/release of Vegas Pro 15

dxdy wrote on 7/5/2017, 8:34 PM

I am reminded of a similar complaint a few years back, where it turned out the client had provided the editor with Friday's performance's video, and Saturday's performance's audio. They were real close, but not quite the same.

Lukasz wrote on 7/6/2017, 4:43 AM

I had such problems with vegas 13 and GPU Nvidia that I decided to switch to radeona R9 and a lot of problems disappeared though not all. Magix should issue a correction to vegas 13 and do not force it to update to 14 and it's for a fee. Due to the policy of magix I will not buy vegas 14 the more that it has quite the same defects as vegas 13. I have recently tested vegas 14 and the same error I have as vegas 13. I am irritated that magix has left customers with problems in vegas 13

Cliff Etzel wrote on 7/6/2017, 1:21 PM

I had such problems with vegas 13 and GPU Nvidia that I decided to switch to radeona R9 and a lot of problems disappeared though not all. Magix should issue a correction to vegas 13 and do not force it to update to 14 and it's for a fee. Due to the policy of magix I will not buy vegas 14 the more that it has quite the same defects as vegas 13. I have recently tested vegas 14 and the same error I have as vegas 13. I am irritated that magix has left customers with problems in vegas 13

I am bypassing VP14 and will wait for when VP15 is released. My understanding is MAGIX is rewriting alot of the underlying code to better reflect today's hardware. Let's hope that in the process, Vegas becomes an even better platform for editing video.