In the countless times I tried the audio sync tool, it worked literally only once. In this particular instance, both cameras were next to each other at the beginning of the shoot so the recorded audio was almost identical.

I have also tried using audio sync in Vegas 18 (this is the main reason I upgraded) but it doesn't work. When I try to use it, it stays at 0% and nothing happens.

I used to use Plurayes (and it kinda worked good, sometimes it sucked) with Vegas 14/16. I thought it should have worked also for 18 but it doesn't appear. Any tips?

I don't use the auto sync feature, I'm accustomed to zooming in at the frame by frame waveform and align my external audio to my scratch audio, with perhaps a clap to have it be more obvious.

So the real question is why did you copy my original post? Weird...

https://www.vegascreativesoftware.info/us/forum/has-anyone-been-able-to-do-automatic-audio-sync-vp18--124143/

Anyways, the audio sync feature seems pretty useless right now.

I'm only a million years late, but I have an open-source tool that does this. Choose your video file, choose your audio file(s), and it will sync them up, and create a project file you can import into Vegas.

https://github.com/kerryland/auto-sound-sync

I'm only a million years late, but I have an open-source tool that does this. Choose your video file, choose your audio file(s), and it will sync them up, and create a project file you can import into Vegas.

https://github.com/kerryland/auto-sound-sync

@kerryland

Thanks for this great tool! I tried it just out of curiosity, as I usually work with timecode.
I really like, that it is so incredibly fast, but there are some things that I noticed:

1. The XML project video properties always seem to be 720p @25 fps. Is this hard coded or can it be changed somewhere? Why not use ffprobe to get the actual properties from the video files analyzed?

Or even better: Why not export the synced data as an EDL? An EDL is perfect for getting high precision timing information of events into Vegas, instead of using an XML with unused information and only frame precision.
 

2. In case there is a long reference audio file (say 2 h), only files that start quite at the beginning of the reference audio are synced properly. Files that start later (say 1 h) are put near to the beginning (where similar noise patterns are). Looks like the syncing algorithm only uses the beginning of the files? Not a problem for me, but maybe an important information...
 

3. When I use a stereo audio file (only tried FLAC) as reference (HQ audio source), the resulting Vegas track is always in mono. The only way to fix this, is to export everything as an EDL and reimport the project via EDL.
 

4. What about giving the option to keep the audio of all other source files, to check the sync quality later in Vegas manually? Deleting the redundant audio tracks after checking is not a big deal.

Thanks again,
NIls

@NoKi

Thanks for the feedback. Apparently I have to put in a little more effort now!

I'll convert your feedback into tickets on github, so you can follow along there if you like, but with regard to your second issue, you might like to try again using a different "Synchronizer" algorithm, which you can select from the "File | Options" dialog.

I hasten to add that I did not write any of the clever synchronization algorithms -- I just glued them together and added the "Export Project" function.

@NoKi do you have a specification for the EDL file format?

@kerryland

Wikipedia has a list of helpful links https://en.wikipedia.org/wiki/Edit_decision_list

and also a link to the old original CMX3600 standard for reference. Though, for just positioning some events, reverse engineering of the Vegas EDL might be the easiest way, as it is just a plain text file with ";" separated columns and a header line.

"ID";"Track";"StartTime";"Length";"PlayRate";"Locked";"Normalized";"StretchMethod";"Looped";"OnRuler";"MediaType";"FileName";"Stream";"StreamStart";"StreamLength";"FadeTimeIn";"FadeTimeOut";"SustainGain";"CurveIn";"GainIn";"CurveOut";"GainOut";"Layer";"Color";"CurveInR";"CurveOutR";"PlayPitch";"LockPitch";"FirstChannel";"Channels"
1; 1; 0.0000; 10101.5965; 1.000000; FALSE; FALSE; 0; TRUE; FALSE; VIDEO; "F:\Captures\AR test 2.mp4"; 0; 0.0000; 10101.5965; 0.0000; 0.0000; 1.000000; 4; 0.000000; 4; 0.000000; 0; -1; 4; 4; 0.000000; FALSE; 0; 0
2; 1; 10101.5965; 14978.2293; 1.000000; FALSE; FALSE; 0; TRUE; FALSE; VIDEO; "F:\Captures\AR test 2.mp4"; 0; 19419.4485; 14978.2293; 0.0000; 0.0000; 1.000000; 4; 0.000000; 4; 0.000000; 0; -1; 4; 4; 0.000000; FALSE; 0; 0
3; 1; 25079.8258; 9650.9460; 1.000000; FALSE; FALSE; 0; TRUE; FALSE; VIDEO; "F:\Captures\AR test 2.mp4"; 0; 40232.2207; 9650.9460; 0.0000; 0.0000; 1.000000; 4; 0.000000; 4; 0.000000; 0; -1; 4; 4; 0.000000; FALSE; 0; 0
4; 1; 34730.7718; 9317.8520; 1.000000; FALSE; FALSE; 0; TRUE; FALSE; VIDEO; "F:\Captures\AR test 2.mp4"; 0; 10101.5965; 9317.8520; 0.0000; 0.0000; 1.000000; 4; 0.000000; 4; 0.000000; 0; -1; 4; 4; 0.000000; FALSE; 0; 0
5; 1; 44048.6238; 5834.5429; 1.000000; FALSE; FALSE; 0; TRUE; FALSE; VIDEO; "F:\Captures\AR test 2.mp4"; 0; 34397.6778; 5834.5429; 0.0000; 0.0000; 1.000000; 4; 0.000000; 4; 0.000000; 0; -1; 4; 4; 0.000000; FALSE; 0; 0
6; 0; 0.0000; 10101.5965; 1.000000; FALSE; FALSE; 0; TRUE; FALSE; AUDIO; "F:\Captures\AR test 2.mp4"; 0; 0.0000; 10101.5965; 0.0000; 10.0000; 1.000000; 2; 0.000000; -2; 0.000000; 0; -1; -2; 2; 0.000000; FALSE; 0; 0
7; 0; 10101.5965; 14978.2293; 1.000000; FALSE; FALSE; 0; TRUE; FALSE; AUDIO; "F:\Captures\AR test 2.mp4"; 0; 19419.4485; 14978.2293; 10.0000; 10.0000; 1.000000; 2; 0.000000; -2; 0.000000; 0; -1; -2; 2; 0.000000; FALSE; 0; 0
8; 0; 25079.8258; 9650.9460; 1.000000; FALSE; FALSE; 0; TRUE; FALSE; AUDIO; "F:\Captures\AR test 2.mp4"; 0; 40232.2207; 9650.9460; 10.0000; 0.0000; 1.000000; 2; 0.000000; -2; 0.000000; 0; -1; -2; 2; 0.000000; FALSE; 0; 0
9; 0; 34730.7718; 9317.8520; 1.000000; FALSE; FALSE; 0; TRUE; FALSE; AUDIO; "F:\Captures\AR test 2.mp4"; 0; 10101.5965; 9317.8520; 10.0000; 10.0000; 1.000000; 2; 0.000000; -2; 0.000000; 0; -1; -2; 2; 0.000000; FALSE; 0; 0
10; 0; 44048.6238; 5834.5429; 1.000000; FALSE; FALSE; 0; TRUE; FALSE; AUDIO; "F:\Captures\AR test 2.mp4"; 0; 34397.6778; 5834.5429; 10.0000; 10.0000; 1.000000; 2; 0.000000; -2; 0.000000; 0; -1; -2; 2; 0.000000; FALSE; 0; 0

I found this example here. AFAIR, all time values are ms, so no information on framerate or timecode is needed. Vegas will translate it into proper timecode values according to the project settings.

Nils

@NoKi. Hmmm. I had found similar information, but examples aren't really documentation. There are a lot of columns with unusual values. I'll ask Magix support if they have a formal specification. They must, surely!