Both right! It is important to differenciate if you play that video locally (before you upload it to YT) or if you play it on YT. But in both cases it is not a bug in voukoder. It is just a question of the used settings.

Can anybody else reproduce this? Works fine for me.

So you basically need to opposite of what i've shown above?

Unfortunately this is a different filter "adelay". They could've really combined this in one filter.

Maybe it doesn't really make sense to pass through FFmpegs filter 1:1. Maybe I need to put more logic in voukoder to make this more user friendly.

With this setting I was able to correct it:

In Audacity it looks okay:

P.S.: Yes, currently only times are working, specifying samples seems to be broken...

Normally the FPS is taken from the project settings. Maybe you can copy&paste the voukoder logfile?

Can you try to reproduce this with FFmpeg on the command line?

This will be fixed in the next version.

Can you try to reproduce this with FFmpeg on the command line?

It is most likely an AMD driver issue. You might also post the Voukoder log file.

It has float data as input. This means values from (theoretically) -1.0 to +1.0. (Over/Undershooting is still possible).

32bit here is the precision (simplified: the number of decimal points) of that value, not the resolution like with PCM (integer).

"float" as a type has always a size of 32 bits (or four bytes)

In some formats you have also 64bits of precision available, which is actually called "double"

Regarding FDK AAC: RE: A better AAC encoder: FDK-AAC

Voukoder 4.1 has fixed the presentation of the list of available encoders and formats/muxers with Video/audio dis- or enabled.

VEGAS users: Please update to connector 0.7.0. There is now an option to disable or change audio settings.

Release Notes 4.1

Just a small bugfix release fixing the small issues below.

Fixes

• Fixed encoder filtering based on selected stream types
• Removed double file extension from some encoders

Notes

For using NVENC encoders driver version 436.15 or newer is required.

Credits

Thanks to my all supporters - especially the platinum tier patrons ValnirÆsirsson and Gronkh!

Download

https://github.com/Vouk/voukoder/releases/tag/4.1

• So the audio data (float32) from premiere is pretty much okay.
• float32 -> s16le (pcm) is okay too
• float32 will be directly send to the aac encoder as "fltp" (no conversion)
• it has to do with the aac encoder

Maybe it has to do with the options?

-aac_coder <int> E...A.... Coding algorithm (from 0 to 2) (default fast)

anmr E...A.... ANMR method

twoloop E...A.... Two loop searching method

fast E...A.... Default fast search

-aac_ms <boolean> E...A.... Force M/S stereo coding (default auto)

-aac_is <boolean> E...A.... Intensity stereo coding (default true)

-aac_pns <boolean> E...A.... Perceptual noise substitution (default true)

-aac_tns <boolean> E...A.... Temporal noise shaping (default true)

-aac_ltp <boolean> E...A.... Long term prediction (default false)

-aac_pred <boolean> E...A.... AAC-Main prediction (default false)

-aac_pce <boolean> E...A.... Forces the use of PCEs (default false)

Does this happen with the Fraunhofer AAC encoder too? Did you test this?

What about if you export raw pcm?

I guess there might be an issue with the 32 bit float data coming out of premiere.

I am working on an update making this possible. It is in the testing phase now.

Voukoder 4 can correct this with the "atrim" filter (both in milliseconds and in number of samples).

Yes, from what i've found 1536 kbps is the max. limit.

Zitat

[23:45:36] FFmpeg: InitializeEncoder failed: invalid param (8): Invalid Level.

It is rather the NVIDIA driver that complains about the issue. I remember we've had this issue since the first days of Voukoder. Strange that you report other version don't have this issue ...

Unfortunately I can't do anything about it. I am always using the latest FFmpeg version.

You might turn on low-level logging and provide the voukoder log file. There should be more info about the issue. But i guess it is an FFmpeg limitation.

shamo42 If you keep it busy, does it continue after a longer time? Maybe after 1 minute?