VoukoderPro + Vegas Pro 22 -- premature audio stream end

fifonik

I'm still evaluating VoukoderPro for Vegas 22 and noticed premature audio stream end in rendered file.
The same Vegas Pro project was rendered twice: with Voukoder Legacy (13.4.1 + connector 1.0.0) and Voukoder Pro (2.0.10).
Then I've put rendered files into the same project at tracks below and here what I see at the very end of these tracks:

MediaInfo tells similar story. Rendered with Voukoder Pro:

Rendered with Voukoder Legacy:

Any suggestions how this can be fixed?
Or, if this is a bug, what other details should I provide so it can be fixed?

Thanks.

P.S. You may also notice one frame offset in audio for both Voukoder renders. This is known issue that I'm living with when rendering from Vegas with Voukoder and it was discussed in the forum already.

P.P.S. You may notice bigger video stream size for legacy render on MediaInfo. That was final render so I added a bit of sharpness on the whole video track so higher bitrate with the same CRF value. No other changes were made in the project.

Vouk

It's the return of this issue. It's a VEGAS bug, not a Voukoder Pro bug. The audio is delayed by 0.0444 seconds (Vegas Pro: Audio Shift in rendered video).

Voukoder Classic added a hidden filter with this specification:

Code

const float delay = 44.4F;

std::stringstream ss;

if (strlen(config.audio.filters) > 0)
	ss << config.audio.filters << ",";

ss << "filter.adelay#delays=";
ss << std::round(((float)m_pTemplate->Audio.Render.wfx.nSamplesPerSec * delay) / 1000.0F);
ss << "S:all=1";

strcpy(config.audio.filters, ss.str().c_str());

Alles anzeigen

This is not present in Voukoder Pro anymore because the filter chain has been entirely reworked, but you can add a filter after the audio input node:

This is currently untested, but you can give it a try.

fifonik

Thanks for reply. I will give it a try (need to understand how to do whan you suggested) and report back.
You mentioned 1958.04. If I understand correctly, this is for 44.1kHz project. For 48kHz project I should use 0.0444 * 48000 = 2131.2. Is it correct?

Thanks.

Vouk

Correct! But don't forget the uppercase S at the end.

fifonik

I've just tried your suggestion:

Tested it with small fragment and unfortunately, it does not work as I expected.
With adelay 2131.2S the audio offset is way too big (the the bottom track).
With adelay 0.044 (without S) the audio looks in sync, however in this case video stream becoming longer. A few black frames were added at the very beginning of the video stream and a lot of frames were added at the very end of the stream.

Audio stream is also become longer with some silence in it.

Vouk

Ah, maybe the thousands of this value is correct. Can you try 2S (2 Samples) (as it is actually 1.98912S) for 48KHz?

fifonik

I've tried the 1.98912S and it gives the same results as 0.048

Re-testing everything.

Ignore my previous messages about black frames at the beginning and at the end. I failed during experiments.
However, there is still premature end of audio when I rendered all the project with adelay 1.98912S:

And I do not see any delay here at all.

Vouk

Please try rounding the value to 2S as I asked above. I don't know if FFmpeg rounds it down to the nearest integer value.

VoukoderPro + Vegas Pro 22 -- premature audio stream end

fifonik 30. März 2025 um 01:35

Benutzer online in diesem Thema