Audio is indiscriminately 15 frames off from HD video after importing

Greg-Otterholt wrote on 12/4/2024, 10:29 AM

I recently "upgraded" from Pro21 to Pro22 and have had a multitude of problems with the new software. I feel I got duped into a poorly vetted new version and that I'm the lab rat they're discovering all their cancers on.
The latest issue is that often times (but not always) the HD 1920x1080 / 29.97fps footage I drag onto the timeline or import into the project... the audio will sometimes be 15 frames off from the video. These are videos shot with the same settings and same camera I've used for a decade in every previous version of Vegas Pro without ever having this issue. I drag the same file into Vegas Pro21 and it works perfectly.
These are all shot sequentially in 1 continuous recording... though the camera (Sony HDR-PJ710V shooting Highest Quality 60i footage 1920x1080) breaks the event into 1.97gb/17+minute file segments. So far, the first segment seems to work and line up fine... then every file after that, the audio occurs 15frames (1/2 second) too early.

I drag the same files in the same exact way in Vegas Pro21 and they're all perfectly lined up. If I copy from the perfect 21 timeline files and paste them into 22... the video is now off and late again. If I start a brand new project in 22 and drag the first file in the sequence in... it works fine. If I drag any subsequent files in before or after that... the timing is off.

BTW... haven't had any timing issues with my 4k footage.

Does anyone know of a fix for this?

Thank you in advance!

Comments

rraud wrote on 12/5/2024, 10:15 AM

Does the same behavior exist if the file is imported from explorer. I recall this issue occurred when I dragged a file to the timeline but no issue when importing. However, it was a long long time ago and I think it was specific to a file type, nor do I recollect what VP version

Greg-Otterholt wrote on 12/5/2024, 10:53 AM

Thanks Rraud... Yep, does it regardless of which way I bring it into the project. I remember that being an issue several versions back as well so I tried importing it every way possible in both brand-new and existing VP projects.

VEGASDerek wrote on 12/5/2024, 11:17 AM

@Greg-Otterholt would you be able to provide a piece of media to us for the team to analyze and help us fix this problem you are seeing?

Greg-Otterholt wrote on 12/5/2024, 6:58 PM

Thank you Derek!
Here's a link to a short piece of footage that's having the timing issue. When I bring it into VP 22... the audio doesn't match the video. Sound occurs 1/2 second too early.
https://u.pcloud.link/publink/show?code=XZ3Il05ZLmICwUQNv4447h1eeQLsPFVttmUy

john_dennis wrote on 12/5/2024, 8:01 PM

@Greg-Otterholt I can reproduce the Vegas Pro 21-194 bug.

That's a big reason that I work to keep VideoReDo TVSuite alive even though the programmer is dead.

If you need to get your work out the door before VegasCreativeSoftware has a fix for Vegas Pro, there are many quick and easy ways to convert your media to something Vegas Pro accepts without issue in Shutter Encoder. Download Link: https://www.shutterencoder.com/

john_dennis wrote on 12/5/2024, 8:25 PM

@Greg-Otterholt said:  "These are all shot sequentially in 1 continuous recording... though the camera (Sony HDR-PJ710V shooting Highest Quality 60i footage 1920x1080) breaks the event into 1.97gb/17+minute file segments. So far, the first segment seems to work and line up fine... then every file after that, the audio occurs 15frames (1/2 second) too early."

Long ago in a land far, far away there was a Sony application (Play Memories?) that would combine files that had been split when they were longer than was allowed by the file system of the media or some silly 29 minute, 29 second limit imposed by regulators to differentiate between professional and consumer cameras for tax purposes. You may be working with files that were split and not recombined correctly. If Vegas Pro 21 worked in the past, that's way cool.

john_dennis wrote on 12/5/2024, 8:46 PM

@Greg-Otterholt A very old program called tsMuxer makes light work of repairing your files.

Download from here: https://www.videohelp.com/software/tsMuxeR

UltraVista wrote on 12/5/2024, 9:02 PM

It's a bug with the new decoder, VP20 also plays it fine.

john_dennis wrote on 12/5/2024, 10:59 PM

Some work is required with Loudness Log interpretation, too.

Vegas Pro 13-453

---------------------------
Results:

Mom. (max):     -20.58 (LUFS) at 00:02:20.459
Short (max):     -23.73 (LUFS) at 00:02:21.653
Integrated:     -30.60 (LUFS)

Vegas Pro 21-315

---------------------------
Results:

Mom. (max):     -10.36 (LUFS) at 00:02:20.459
Short (max):     -13.19 (LUFS) at 00:02:21.653
Integrated:     -19.80 (LUFS)

Vegas Pro 22-194

---------------------------
Results:

Mom. (max):     -15.02 (LUFS) at 00:00:04.608
Short (max):     -17.94 (LUFS) at 00:00:06.997
Integrated:     -21.37 (LUFS)

 

Greg-Otterholt wrote on 12/6/2024, 1:24 AM

Wow! Thank you john_dennis for doing the deep dive there with your great diagnosis and analysis! I really appreciate you taking the time to help with this! It's so odd that the file works on all the older versions of Vegas Pro but not the "latest and greatest upgrade." Hmmm
So thankful for the video you made and the link you posted above as well!
Curious what your thoughts are after editing on the best VP22 render settings for HD 1920x1080 video to be uploaded on Youtube. Thank you again!

john_dennis wrote on 12/6/2024, 1:51 AM

@Greg-Otterholt said: "It's so odd that the file works on all the older versions of Vegas Pro but not the "latest and greatest upgrade." Hmmm"

The Vegas developers are rewriting the "video engine" as the old one that worked well for older formats has gotten long in the tooth for some of the new formats. The rewriting process is like a grass fire. It doesn't all burn at once. By definition, "burning all at once" is better known as an explosion.

I use Voukoder for rendering. It's too late for a description of my settings for youtube.

RogerS wrote on 12/6/2024, 3:34 AM

The default MagixAVC settings are fine for YouTube. If you see compression artifacts with the rendered file, increase the bitrate.

Personally I avoid QSV encoding with AVC and AV1 in VEGAS for quality reasons. If you really want those do them through Voukoder.