Audio desyncs during editing in Vegas Pro 21

Hokinar wrote on 10/18/2024, 2:49 PM

New in the forums but a long time user of Vegas Pro. Didn't see any topics about this exactly so i decided to make this post. I keep getting this weird audio problem in Vegas Pro 21 (build 315). Every time i move the timeline slider or something, it bugs out the audio somehow. I don't know how to describe it properly so i made a video sample. Listen closely just before i pick up the box of ammo after rewinding 2-3 times. It kinda "resets" itself about 3 seconds in. Vegas Pro 19 doesn't have this problem.

Comments

RogerS wrote on 10/18/2024, 10:28 PM

Can you share MediaInfo for the media you are using?

Hokinar wrote on 10/19/2024, 8:29 AM

Sure, assumming u mean the video

Hokinar wrote on 12/20/2024, 7:32 AM

Has anyone looked into this? It's been over a month and i provided Mediainfo in my 2nd post.

RogerS wrote on 12/20/2024, 8:28 AM

@Hokinar We've looked into and reported other cases of audio desyncing. If you'd be able to provide a sample (<10 min?) that shows desyncing happy to test and report that as well.

Hokinar wrote on 3/24/2025, 1:03 PM

Update: I finally seem to have found a workaround/fix on this. Thanks to this thread:

https://www.vegascreativesoftware.info/us/forum/audio-out-of-sync-bug-vegas-pro-21-0-january-2024--144304/

i found out about an option called "Enale Legacy AVC decoding". I checked it and restarted the editor. Now the audio hasn't desynced anymore. I had no idea this is even a thing.

Speaking of desyncing, it was ridiculous last night. i was trying to edit some L4D2 clips but whenever i dragged the timeline pointer anywhere other than the end or beginning, the audio played back as if it was at the beginning. It also sort of reset itself several times

I'm using VP22 now btw. So glad i found that feature.

RogerS wrote on 3/24/2025, 6:32 PM

Can you provide a sample file? The legacy AVC decoder will be phased out at some point so it's preferable to fix VEGAS vs this workaround.

How was it captured? OBS? If so try good settings like AVC in MP4 with the keyframe interval set to 1 second vs 0 (auto).

Hokinar wrote on 3/24/2025, 10:02 PM

I don't like using OBS, i usually use Mirillis Action. I compiled another video showing the desync. Action doesn't have an option for keyframe intervals though.

(had to link that again, file upload ended up in an error)

Here are the Mediainfo files:

john_dennis wrote on 3/24/2025, 11:30 PM

I would be curious to know if the audio sync improves if you convert the audio sample rate from 96 kHz to 48 kHz in Shutter Encoder.

It should only take a few seconds.

Hokinar wrote on 3/25/2025, 3:09 PM

Dunno if i've heard of Shutter before. I suppose it's similar to Handbrake which i HAVE used in the past. Converting it to 48khz seems to have solved the problem. Just to be clear, i had system sounds set at 192khz 32 bit. I set it to 24 bit 48khz considering VP22 "only" seems to allow 24bit audio at highest. Dunno if i'm being a dumbass but i thought the settings in Windows Sound Control Panel meant higher sound quality the higher the kHz is, i guess it's not. I'm talking about the list below.

Side note: that screenshot is from a dedicated sound card, not a Realtek chip or whatever it's called. A Sound BlasterX to be more precise.

 

I recorded a couple of new videos with my typical settings in Action. So far, desyncing has stopped occuring with 48kHz.

john_dennis wrote on 3/25/2025, 4:32 PM

We all should learn something new every day. Then, we should try to understand what we just learned.

RogerS wrote on 3/25/2025, 7:36 PM

Could you provide a link to download a 96khz file that has desynced audio for testing?

Hokinar wrote on 3/26/2025, 8:29 AM

Could you provide a link to download a 96khz file that has desynced audio for testing?

I guess i could do that.

https://drive.google.com/file/d/13GQ4oL8wb9QabNpC7cq38Mh5vPLte45O/view?usp=drive_link

I should point out that media players like VLC don't have any sync issues with the video for some reason. It only occurs in Vegas Pro. And just as a reminder, i've had syncing issues with version 21 onwards. I don't have a copy of VP20 so i can't comment there.

RogerS wrote on 3/26/2025, 8:43 AM

@Hokinar Thank you! VEGAS isn't a media player but it should still be able to correctly decode many types of media. VEGAS gained a new decoder with build 300 of VP 21 which is much better in a lot of ways but isn't as well tested with certain media as the older ones were.

Let me take a look at this file.

john_dennis wrote on 3/26/2025, 11:07 AM

@Hokinar said: “ …i had system sounds set at 192 khz 32 bit. I set it to 24 bit 48khz considering VP22 "only" seems to allow 24bit audio at highest. Dunno if i'm being a dumbass but i thought the settings in Windows Sound Control Panel meant higher sound quality the higher the kHz is, i guess it's not. I'm talking about the list below.“

The fallacy of your thought process is that you selected a sample rate four times higher than humans can hear. Then, you used a lossy codec (AAC) at less than the typical bit rate even for a 48 kHz sample rate (192kbps vs 320kbps) and expected you experience to be better. Then, you expected the Vegas Creative Software team to accommodate you in spite of how ill-advised your actions.

RogerS wrote on 3/26/2025, 9:27 PM

I was able to reproduce the issue with this 9khz file. Thank you and if you could leave it online for a while I'd appreciate that.

I can understand wanting to get the best quality for your audio. That said for Windows 24bit 48khz should be sufficient for normal use. Audio for video is normally 48khz (at least when delivered). VEGAS should be able to work with higher rates and used to as when I tested in 21.208 it was fine. So that suggests an issue with the newer decoder as I expected.

Hokinar wrote on 3/28/2025, 1:20 PM

I was able to reproduce the issue with this 9khz file. Thank you and if you could leave it online for a while I'd appreciate that.

Will do. I'll upload a new link if necessary if the earlier one goes down for whatever reason. Facilitating (dunno if that's a proper word for this case) help for future developments is always good.

For the topic itself, i consider this issue solved. I feel practically zero difference in the lower kHz so might as well keep it that way.