Ich fürchte das liegt dann wirklich am AMF encoder in FFmpeg. Es ist leider auch der am wenigsten getestete Encoder.
Hast du es mal auf der Kommandozeile mit FFmpeg direkt getestet?
Beiträge von Vouk
-
-
When adding b_ref_mode=middle it struggles and drops frames.
Since everything works fine unless you change this single setting, it is most likely FFmpeg related. Can you try to reproduce it with FFmpeg on the command line? If so you might report this issue to the FFmpeg team.
-
Actually this depends on the implementation of FFmpeg's "ac3" encoder - I'm just using it. Maybe you can ask them for the right combination and values of options?
-
From my Point of View you'd have two options:
1. You could install a second (cheap) GTX GPU you use just for interlaced encoding
2. You could deinterlace your files first and then encode it as progressive.
-
A special bonus for all my patrons on Patreon (https://www.patreon.com/voukoder)!
A preview version of the upcoming Voukoder version 4:
Changes
- Increased floating point values precision to 3 decimal places
- Added animated GIF support
- Added still image support (BMP and TIFF)
Fixes
- Fixed loading the correct order of filters
- Added low-level logfile for debugging
- Fixed sequential exports with different frame sizes are failing
- Showing video and audio pages only if they are selected in the NLE
Notes
For using NVENC encoders driver version 436.15 or newer is required.
-
NVIDIA dropped interlace encoding for RTX cards.
So: No interlaced video with NVENC.
-
Can you provide the logfile please?
-
Lots of people (incl. me) would like to have this in DaVinci Resolve. But I guess this would be against their product strategy. It is free for a reason: Get people used to that software and if you want hardware encoding buy the bigger versions and the required equipment from BM.
I once sent them an email and they wanted to contact me, but never did.
-
The error message indicates that voukoder does not get any audio samples from premiere.
Does this happen with all your projects or only with a specific one?
-
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 ...
- Created an audio file with Audacity. First tone is 100%, second is 50% and third is 25% (First two mono tracks)
- Adobe AAC created this stereo track. Amplitudes look okay
- Voukoder (Connector 1.2.0, Voukoder 3) with AC-3 also created same looking results.
Can you try to reproduce?
