Beiträge von Vouk

Tested 5.1 (only compared fl and fr):

It has to be some meta settings making the player plays it louder.

Checked their issue page on github. Too many issues still there. The issue we have could be related to https://github.com/OpenVisualCloud/SVT-AV1/issues/937

It is strange. Voukoder normally doesn't drop frames as it takes all the time that it needs to write a frame unless there is an issue with really writing the frame to disk. Does this also happen when you export this file to the desktop on drive c:?

Yes. Forgot its only the release build that has issues. I'll write a very small test program and try to reproduce it with it.

Zitat

I had to remove everything again. Whenever one SVT encoder was implemented premiere always crashed. So no AV1 included in the next build.

When something is not working I remove it of course.

Interesting. It seems premiere doesn't crash anymore with using AV1 in Voukoder with the latest builds.

Kleinrotti can you confirm?

Ok, didn't test 5.1 so far. But will do now.

I have to say that I am not an expert in encoder configuration options. I try my best but what I currently do is compare this on a technical, programmers level.

But what I've also found is:

• Premiere renders a mono audio track of 100% amplitude to only 70%
• Stereo is 100%

I really don't understand this. Why does mono get rendered to 70% only?

scarbrtj What do you use? Stereo or 5.1?

So from the encoder and decoder point of view everything looks alright. So no bug in premiere and/or voukoder.

Ergo: It has to do with how the player plays it and thus it should be the metadata in the encoder settings: https://www.ffmpeg.org/ffmpeg-codecs.html#AC_002d3-Metadata

Zitat

-dialnorm value

Dialogue Normalization. Indicates how far the average dialogue level of the program is below digital 100% full scale (0 dBFS). This parameter determines a level shift during audio reproduction that sets the average volume of the dialogue to a preset level. The goal is to match volume level between program sources. A value of -31dB will result in no volume level change, relative to the source volume, during audio reproduction. Valid values are whole numbers in the range -31 to -1, with -31 being the default.

Sounds very much like it could be the cause.

Maybe you can try?

Please share the voukoder logfile with us.

I will deal with this on the weekend.

Edit: Or even before the weekend ...

1. Created an audio file with Audacity. First tone is 100%, second is 50% and third is 25% (First two mono tracks)
2. Adobe AAC created this stereo track. Amplitudes look okay
3. Voukoder (Connector 1.2.0, Voukoder 3) with AC-3 also created same looking results.

Can you try to reproduce?

Is it maybe an AC-3 encoder setting that defines what a max. peak of float 1.0 means? AC-3 has quite a lot of settings: https://www.ffmpeg.org/ffmpeg-codecs.…d-ac3_005ffixed

I'm not at home so I can't try it out yet.

Maybe it has to do with how premiere decompresses the audio signal from ac-3 to float values. I feed them straight away to FFmpeg.

Need to investigate this more.

Edit: It has one parameter "Clipping true/false". Currently it is set to false always (as I don't want to cut any peaks - that what expect it is used for).

I've already investigated this some months ago, and yes, if you extract the streams it looks exactly like this, but ...

Each stream (audio, video and subtitles) has a timestamp associated with each frame, sample, sub, ... These timestamps are set during the encoding process. So when you extract all the streams (timestamps are ignored) and compare them, they might have different offsets, but once you are playing the file in a media player the demuxer "realigns" the streams and makes sure all timestamps are perfectly in sync. That's why it is perfectly okay for streams to have different offsets and it is fully within the specification - if the timestamps are correct, of course. (And if the demuxer is working correctly).

So you can only compare and check this using a proper player (hardware or software). Like with the good old clapperboard.

But I agree, when importing such a file in an NLE it should look correct, yes.

I fully agree and would really appreciate help with this.

Yes, I do rely on the product strategies of these companies. I guess it is the same with BlackMagic / DaVinci Resolve. The want to get popularity with the free version and want to sell their hardware encoders with the pro version. So it is difficult to get voukoder into these products.

For VirtualDub2 I use a fork of https://sourceforge.net/u/vouk/vdfiltermod which should be pretty recent.

Wrote to them on Twitter some weeks ago, but they never contacted me back. You can still write to their support and refer to me. I would like to write a connector for it.

Are you using Connector 1.2.0 and Voukoder 3?

Please be aware, that you can't just test for transparency by playing it with MPC-HC or any other player. You need to import it in a project again. In MPC-HC the transparent video looked faulty to me too.

It worked for me.

I created a MOV/prores file with default settings:

And imported it again with transparent background: