Hi Vouk
I noticed that there is an audio drift in the file rendered in Vegas using the Voukoder encoder.
It is a deviation of about 3-5 frames, which corresponds to about 45ms. Tested on Voukoder versions 4 and 5.
I took a screenshot showing the problem and I am also sending the original file used in the test. You can download it from this link.
I think you mean this ?
I believe it is. But in my case it is the other way around. The audio rendered in voukoder starts 3-5 frames (45ms) earlier when compared to the original audio. I tried to use the Atrim filter, but it didn't solve the problem.
There is also the possibility that there is a problem with Vegas, as I tested the same file in Adobe Premiere and this problem did not occur.
I am also a user of HOS (Happy Otter Scripts) who also has coding tools that use ffmpeg and I can confirm that this problem does not exist in the renderings made using HOS encoders.
In the official forum of Vegas there is a discussion on this subject and the developer of HOS who also develope encoders for Vegas shows the cause and also the possible solution to this problem.
https://www.vegascreativesoftware.info/us/forum/vouko…-right--120698/
I'll put it on my list.
Hm, I thought it is already on the list as I reported the issue:
Actually there is no physical "list".
But I will look into it again.
At some point I really don't understand this behaviour anymore ...
With FFmpeg AAC only STEREO mode seems to be affected.
FFmpeg AAC is -1024 samples off:
With FDK AAC all modes are affected.
They are +1024 samples off:
I would like to help more with technical information, but my knowledge is quite limited on this subject. There is a discussion in the official Vegas forum on this topic and there is some useful technical information. Maybe that will help something.
https://www.vegascreativesoftware.info/us/forum/vouko…-right--120698/
With FFmpeg AAC only STEREO mode seems to be affected.
In the topic I started (link above), I rendered to AAC 5.1 and it was also affected (source -- m2ts from camcorder with AC3 5.1).
While comparing, I removed all audio tracks from project but front channel only for simplicity (otherwise it would be 16 audio tracks in comparison project: source, wav, Sony AVC, Voukoder -- a bit too messy) . However, other channels are also affected.
I can upload project + source again if needed.
Can you guys please test if this connector helps?
Hi Vouk,
I did some tests with the new connector 0.7.1 for Vegas Pro and realized that now the audio is just 1 frame ahead of the original audio.
I do have the same issue with 5.1 audio: only 1 and 2 channels shown in audio config.
Rolled back to version 0.5.1: no audio config, but it rendered as per project settings.
Please don't mix up the issues here. Lets talk about the audio sync issue in this topic. Please create a new topic for any other issue.
For me it was working nicely:
I used 48kHz AAC audio. What setting did you use?
I've found my footage with Stereo (1080-59.940p, AC3 Stereo) and only see 1 frame offset after rendering (audio 1 frame behind original audio. I do not know why other member says it is ahead, based on his screen shot I'd say it is 1 frame behind).
Then I was able to correct it further using atrim filter (Start = 0.033, start in frames did nothing):
In my view the audio rendered in voukoder is 1 frame AFTER the original audio, just see that the peak of the audio signal is on the right, when compared to the original audio. This happens in mine and in your screenshot.
O que outras pessoas estão dizendo
Vegas Pro 17 has the built-in native so4compoundplug encoder. Apparently Voukoder works correctly with this encoder and that is the reason why your test audio is normal without any displacement.
However, if so4compoundplug is disabled in the internal Vegas preferences, you will notice that the audio will be 1 frame deslocated in camparation with the original audio.
This is because when disabling the so4compoundplug encoder, Vegas will use the old compoundplug encoder to read mp4 files on the timeline. Many Vegas users prefer to work with so4compoundplug disabled as it is a very problematic and buggy encoder.
My first test was done on Vegas Pro 14 which does not have the internal encoder so4compoundplug. It still uses the old compoundplug encoder and apparently that's the reason the audio rendered in Voukoder was 1 frame out of step with the original audio.
Phew ... Why do I get the impression VEGAS is so full of hacks and workarounds? 
Currently I have no clue how to detect which compoundplug is active? ...
It is not impression. It is the reality of Vegas users today. Vegas was not like that before. It was excellent software. It was solid and efficient. Unfortunately the latest versions leave a lot to be desired. For that reason I am still using version 14.
To find out which encoder is being used, do the following:
1.Right-click on the timeline video.
2. In the pop-up menu that appears go to Properties/General.
There will be all the information of the file including which encoder Vegas is using to recognize and read the file.
To disable the so4compoundplug encoder you will need to access the internal Vegas preferences which are hidden by default. To do this, do the following:
1.Hold down the shift key
2. Go to Options/Preferences and choose the option Internal
3.In the window that appears, type "so4" in the search field
4. In the options that appear, go to Values and replace the value TRUE with FALSE
5.Click on apply
6.Close Vegas and Restart for the settings to be applied
To enable again, just redo the same procedure and in Values replace FALSE with TRUE.
I made a short video showing the step by step. I hope this helps.
Yes, I tested it already.
I'd need a programmatic way to determine this.
I made some changes to my last comment and also added a video showing the process step by step, in case you need.
