Beiträge von Kleinrotti

Do you mean ffmpeg 4.1? I used 4.2

uff, I finally got it after hours of problems

I could compile ffmpeg static libraries with svt-av1. So svt-vp9 and svt-hevc should also be possible.

My compiled libraries also work in voukoder

Zitat von Vouk

Did you build ffmpeg with it compiled in already?

I'm currently working on it.

Wow, even AV1 is pretty fast and usable I would say. RAM usage is also higher (about 13GB) ^^. With my TR1950X I get around 10 fps encoding speed with a 1080p video (enc-mode =5). Important is when compiling with visual studio that 'Release' mode is used. When compiling in Debug mode the encoding speed is MUCH slower. On a high core count intel processor with AVX-512 support it should be even faster

In general this is right yes, but if you if a high core count system like a TR1950X disabling Cuda will speed up frame rendering time. I have tested a lot of conditions and only if I apply many effects like color correction, blur effects or other filters, rendering with cuda is faster. If your project hasn't many effects disabling cuda speeds up the rendering (in the voukoder log you can also see that rendering with cuda enabled causes very high latencies because copying the frame to the gpu takes time).

Here is the license information.

Yes, the codec can be build in ffmpeg with a patch which is descriped on the github page.

SVT-VP9 uses 100% of my CPU power for one encoding (AMD TR1950X). With standard VP9 I only get around 5% CPU usage. Thats pretty nice. But it needs a lot of RAM ^^.

If you save a preset in Premiere with advanced video encoder option set and edit it later, the advanced options are lost after clicking "OK".

Here is a small video which shows this issue.

I'm currently testing the SVT-VP9/AV1 codec which are performance optimized and faster than standard VP9 and AV1. The codecs can be build in ffmpeg so I think Voukoder can use it easily. Here are some benchmarks. What do you think Vouk ?

If you think it could fit in Voukoder, maybe I can implement it.

Zitat von Digeridoo

Aditionally about window size. Seems you are designed it for compatibility with HD (720p) screens. I am not sure if somebody use Adobe products with such low screen resolution. Maybe it make sense to rise requirements higher up to FHD (1080p) screens and it will allow to increase default size of main window

A better way would be to calculate the window size depending to the current monitor resolution. Something like 30% of the current resolution could be used and fits for everyone.

Maybe it would be useful to create an extra icon below "General" for "Filters" because its huge amount of items and its fact that it is not a general setting. Furthermore many users don't need filters I think and they have a better overview in the general tab.

Can you please append the Voukoder logfile?

You can find it in the Voukoder Settings Tab->Logfile.

I also not be able reproduce it.

Zitat

Die Lösung

//Schnell (könnte gehen)

Die Instancen so zu starten, dass sie nicht mehr auf eingaben hören. Geht nicht in two pass encodings

//Elegant

ffmpeg verfügt über eine multi encoder Funktion das könnte bei so was helfen.

https://trac.ffmpeg.org/wiki/Creating%20multiple%20outputs

läuft aber auch nur so schnell wie der Langsamste encoder

Alles anzeigen

Voukoder nutzt die native C API von ffmpeg, da wird das so denke ich nicht funktionieren.

Have you applied many effects from frame 150? Because at this time the latencies are much higher.

[10:58:10] Frame #144: vRender: 147 us, vProcess: 6 us, vEncoding: 1986 us, aRender: 32 us, aEncoding: 389 us, Latency: 2427 us
[10:58:10] Frame #145: vRender: 147 us, vProcess: 6 us, vEncoding: 2150 us, aRender: 8 us, aEncoding: 175 us, Latency: 2620 us
[10:58:10] Frame #146: vRender: 147 us, vProcess: 6 us, vEncoding: 2163 us, aRender: 8 us, aEncoding: 138 us, Latency: 2646 us
[10:58:10] Frame #147: vRender: 147 us, vProcess: 6 us, vEncoding: 2408 us, aRender: 73 us, aEncoding: 155 us, Latency: 2668 us
[10:58:10] Frame #148: vRender: 147 us, vProcess: 6 us, vEncoding: 2361 us, aRender: 6 us, aEncoding: 311 us, Latency: 2938 us
[10:58:10] Frame #149: vRender: 147 us, vProcess: 6 us, vEncoding: 2178 us, aRender: 77 us, aEncoding: 159 us, Latency: 2447 us
[10:58:10] Frame #150: vRender: 362477 us, vProcess: 8 us, vEncoding: 2886 us, aRender: 12247 us, aEncoding: 265 us, Latency: 378254 us
[10:58:10] Frame #151: vRender: 245 us, vProcess: 7 us, vEncoding: 3480 us, aRender: 250 us, aEncoding: 803 us, Latency: 4849 us
[10:58:10] Frame #152: vRender: 19795 us, vProcess: 11 us, vEncoding: 1926 us, aRender: 24 us, aEncoding: 6005 us, Latency: 28296 us
[10:58:10] Frame #153: vRender: 49 us, vProcess: 10 us, vEncoding: 1733 us, aRender: 87 us, aEncoding: 331 us, Latency: 5677 us
[10:58:10] Frame #154: vRender: 152 us, vProcess: 6 us, vEncoding: 1341 us, aRender: 100 us, aEncoding: 393 us, Latency: 2028 us
[10:58:10] Frame #155: vRender: 20 us, vProcess: 4 us, vEncoding: 1207 us, aRender: 16 us, aEncoding: 297 us, Latency: 2046 us
[10:58:11] Frame #156: vRender: 570155 us, vProcess: 7 us, vEncoding: 1468 us, aRender: 111 us, aEncoding: 477 us, Latency: 572278 us
[10:58:11] Frame #157: vRender: 30 us, vProcess: 7 us, vEncoding: 1892 us, aRender: 54 us, aEncoding: 381 us, Latency: 3014 us
[10:58:11] Frame #158: vRender: 9425 us, vProcess: 12 us, vEncoding: 4250 us, aRender: 265 us, aEncoding: 550 us, Latency: 14575 us
[10:58:11] Frame #159: vRender: 14435 us, vProcess: 5 us, vEncoding: 2689 us, aRender: 23 us, aEncoding: 548 us, Latency: 18441 us
[10:58:11] Frame #160: vRender: 24448 us, vProcess: 8 us, vEncoding: 2345 us, aRender: 136 us, aEncoding: 644 us, Latency: 27627 us
[10:58:11] Frame #161: vRender: 19 us, vProcess: 4 us, vEncoding: 2219 us, aRender: 16 us, aEncoding: 629 us, Latency: 3450 us
[10:58:11] Frame #162: vRender: 480712 us, vProcess: 8 us, vEncoding: 2354 us, aRender: 22 us, aEncoding: 382 us, Latency: 484164 us
[10:58:11] Frame #163: vRender: 44089 us, vProcess: 6 us, vEncoding: 2392 us, aRender: 161 us, aEncoding: 639 us, Latency: 47345 us

Is your graphics driver up to date?

A log file would help to find the problem. You can find find it in the Voukoder Settings Tab

Already discussed here

I have also added some more Dolby options. Testing functionality now.

What sample rate are you using?

Looks good so far. I am also testing Dolby TrueHD