Thanks Eric (and greetings from Wgtn - I see your pohutukawa!).

My Win11 was a fresh install back in June (24H2) and I moved from VP22 to VP23 about a month back, with no problems until yesterday. The AC-3 audio is playing just fine in Vegas, the only problem being that it's 17 frames out of sync with the video.

Regardless, following your hunch, I have installed the K-Lite codec pack and restarted several times. But no improvement, sadly.

Are there any other things that occur to you?

Your help is greatly appreciated - thanks for taking the time!

Hi, Auckland here.

Installing K-Lite is usually not recommended as it can conflict with VP's codecs.

Can you shoot a short clip of something say a minute long. Check it still has the problem and then post somewhere like Google drive. Others can then download to see if they have the same problem and if so the file can be forwarded to Vegas developers. Thanks.

Thanks for the K-Lite advice - that's now uninstalled.

So I've recorded several short clips using three of the problem cameras and (of course..) I can't replicate the problem upon importing to VP23. Existing problem clips remain unsynced upon importing them in to fresh VP23 sessions. The problem clips are, of course, much larger in file size and duration - around 2GB and 12 minutes - perhaps that makes a difference? I can always upload one of these 2GB ones to Google Drive - would that be acceptable? Again - your help is valued!

@Chris-Watson said: "I can always upload one of these 2GB ones to Google Drive - would that be acceptable?"

Please do. I'm always interested in audio sync problems.

Thanks John et al. Here's a link to download a 1.85gb file. It plays just fine natively, but when dragged into a VP23 timeline the audio is 17 frames late.

https://drive.google.com/file/d/169oCYC6SpaL2etfSCUbSE6zHQhhRe3T4/view?usp=sharing

Really interested to know if this is replicated in other peoples' setups and if anyone has ideas about why this might be happening.

@Chris-Watson I can confirm that there's a de-sync in VP22/23, but not in Davinci Resolve and Powerdirector, my two other NLE's on my PC.

MTS from my old Canon camcorder works perfectly.

The one supplied from @Chris-Watson

Is this video from a DVD?

MTS from my old Canon camcorder works perfectly.

The one supplied from @Chris-Watson

I think it has to do something with the length of the videofile, even when I use shutterencoder to make a mp4 out of the file of @Chris-Watson, the result is out of sync in Vegas.

MTS from my old Canon camcorder works perfectly.

The one supplied from @Chris-Watson

Is this video from a DVD?

No, it's not from a DVD. I shot this a week back using a Sony CX900. I'm experiencing the same MTS de-sync issues with a second CX900 and a bunch of other (even worse) legacy Sony camcorders.

It opens correctly in my VP21B315 using Win11 with MS AC3 codec. So it again makes me wonder if its VP's new AC3 decoder that's the problem. But @3POINT you have the problem with a Shutter Encoder mp4 file which presumably is AAC audio. Of interest could you post MediaInfo on your mp4 file.

Looking at the MediaInfo of Chris's mts file that I downloaded I note the Duration varies.

General shows 11 mins 47 secs
Video shows 11 mins 46 secs
Audio shows 11 mins 47 secs.

Could it be that it's not an audio problem but a video stream length issue?

@Chris-Watson

Vegas 13 handles the audio in the sample file properly.

Vegas 22 slips the audio

My knee-jerk Shutter Encoder fix for this sort of thing failed miserably. I have to go do some actual work though. I'll be back later.

I have 314 GB of MTS files (through no fault of my own).

@Chris-Watson Were these files copied directly from the camera storage or re-combined from 2GB split files?

@john_dennis This file/clip comes directly from the SD card with no processing at all. It's the third and last clip shot consecutively by the camera on the night (being locked-off and left to run - I'm elsewhere in the concert hall). So it's shorter and with a smaller file size than the two clips that precede it (I manually end the clip).

@Chris-Watson Are the camera cards formatted FAT32?

Please post Mediainfo report for all of the files on the camera card where the sample file came from per @EricLNZ's assertion: "Could it be that it's not an audio problem but a video stream length issue?"

VideoReDo Quickstream Fix had a terrible time with this file...

I thought it was only files over 4gb that were a FAT32 problem. But my 12 year old Canon AVCHD camera shoots mts. I rarely shoot long clips but checking back the only time I did my mts had a 2gb limit. I always use my Canon Pixela Video Browser to download via USB from my camera. My long shoot was in two files which I tried unsuccessfully to join on the timeline but the audio or video didn't give a smooth join. I then discovered that Video Browser had seamlessly combined the files into one which was placed in a separate folder which I hadn't noticed. This file, over 2gb, was perfect on my timeline.

So in summary what John is wondering, as am I, is whether possible file joining is behind the problem. But that doesn't explain why it's only VP23 that appears to have the problem with the files.

@Chris-Watson

Download and try this file in Vegas Pro 23.

https://drive.google.com/file/d/1T80MCQ-LmMAYdDKiQgakSGWnQ8-lXpjB/view?usp=sharing

If it works, I'll 'splane what I did.

I'm blown away by everyone's responses and am deeply appreciative!

Confirming that the SD card is set to exFAT.

These Sonys automatically begin a new clip roughly every 2.07gb - about 12.5 minutes of run time. When I drag a bunch of them into Vegas they've always just butted perfectly up against one another with no visual interruption (there is a tiny drop out of audio). So, @john_dennis and @EricLNZ, the problem doesn't seem to be with file joining - indeed, I can drag them onto the timeline individually and it's the same issue.

@john_dennis, thank you for the file. It opens and is in sync in VP23. What's the secret?

I opened your sample file in Vegas 13 and rendered to XDCAM EX MXF. All other interventions were out of sync on my machine.

Imo it's Vegas that should be corrected to accept those files correctly (like any other NLE do) and not that those files should undergo an extra shutter Encoder treatment to be accepted correctly by Vegas. The need for using shutterencoder means extra time, extra storage space and probably a degradation of quality, a no go for a serious editor. It's the tool that should be corrected and not the source.

Thanks @john_dennis. Appreciated, and so strange that it was only this specific XDCAM format that was successful.

But I tend to agree with @3POINT that I shouldn't have to re-encode. Vegas has always been so good at whatever your throw at it and I can't understand why, after using these exact cameras, file types, specs etc for so many years that all of a sudden it's out of whack. For orchestral music I can be working with up to 14 cameras in a multicamera environment and extra prep work would make for a much longer process.

For now I think I'll simply slip everything by 17 frames and hope this doesn't introduce issues in multicam. It's an extra step for a number of cameras, but it seems it has to be done. But it would be good to think that Vegas could consider a fix. Is there somewhere that I could lodge a request?

Again, thanks @EricLNZ, @john_dennis, @3POINT and @Reyfox for your kindness. It's a nice community you have here.