Schicke es mir (oder je nach Größe einen DropBox o.ä. Link) an daniel@voukoder.org.
Beiträge von Vouk
-
-
Kannst du mir ein kleines Beispiel-Projekt mit den Audio-Spuren schicken damit ich das genauer untersuchen kann?
-
-
It should be present in Voukoder classic.
But I've also added it to VoukoderPro in version 0.7.7.
-
Added the potential fix also to the VEGAS Pro connectors 1.7.0 for Voukoder classic.
-
Can someone please try if the alpha channel now works with version 0.7.6 of VoukoderPro?
-
I reinstalled the voukoder.org webserver and updated all software components to the latest version.
Let me know if there are any issues.
-
Voukoder is for Windows only.
VoukoderPro - once it is finished - can be also built for Mac.
-
You don't need to worry about the hardcoded settings. They match up with the encoders default settings (on the command line).
-
Are you sure you want to encode in 10 bit and not 8 bit?
It'd help to use a faster preset. p2 and p1 would even use both encoding engines of the 4090.
For some reason the cpu is the bottle neck here.
Code[12:53:01] Frame #171: vRender: 695781 us, vProcess: 15423 us, vEncoding: 21569 us, aRender: 116 us, aEncoding: 1115 us, Latency: 735244 us [12:53:01] Frame #172: vRender: 21765 us, vProcess: 10612 us, vEncoding: 18021 us, aRender: 84 us, aEncoding: 2170 us, Latency: 54566 us [12:53:01] Frame #173: vRender: 98124 us, vProcess: 18532 us, vEncoding: 25001 us, aRender: 171 us, aEncoding: 14 us, Latency: 143620 us [12:53:01] Frame #174: vRender: 363 us, vProcess: 13767 us, vEncoding: 21068 us, aRender: 92 us, aEncoding: 1331 us, Latency: 39040 us [12:53:01] Frame #175: vRender: 3343 us, vProcess: 10310 us, vEncoding: 18882 us, aRender: 192 us, aEncoding: 565 us, Latency: 36057 us [12:53:01] Frame #176: vRender: 65775 us, vProcess: 15046 us, vEncoding: 30791 us, aRender: 137 us, aEncoding: 2444 us, Latency: 116458 us [12:53:02] Frame #177: vRender: 837611 us, vProcess: 11949 us, vEncoding: 23436 us, aRender: 244 us, aEncoding: 1192 us, Latency: 876397 us [12:53:02] Frame #178: vRender: 218 us, vProcess: 9556 us, vEncoding: 17262 us, aRender: 86 us, aEncoding: 6 us, Latency: 28865 us [12:53:02] Frame #179: vRender: 37892 us, vProcess: 10338 us, vEncoding: 15881 us, aRender: 89 us, aEncoding: 575 us, Latency: 66451 us [12:53:02] Frame #180: vRender: 47363 us, vProcess: 18529 us, vEncoding: 34612 us, aRender: 124 us, aEncoding: 1708 us, Latency: 104267 us
vRender (The time premiere needs to render the frame) is constantly changing between 0.2 ms and almost 700 ms. What's your cpu doing?
-
-
-
Great! Nice to hear!
-
Found it. For the hwupload_cuda filter the parameter name is device not gpu. Fixed it in 0.7.5.
You might have to edit each hwupload_cuda node, select the gpu and save the scene again to make it work.
-
Yes, as far as I know there are also USB3 to PCIe x1 adaptors (for mining equipment).
Can you test such a complicated workflow that includes 2 or 3 gpus with plain ffmpeg.exe? Just to check if it is actually an FFmpeg limitation?
-
This issue occurs because there is no preset saved in Scene Design.
This is fixed in 0.7.4.
-
I'll investigate this issue.
-
Anyway, when I click this botton nothing happen. Why?
Difficult to tell. Normally the Scene Designer should open. Does it open if you start it from the desktop icon?
-
Yes, I fixed this in the next version so $(OutputFileName) does not contain the extension anymore.
Edit: This is fixed in 0.7.4.
-
I'm absolutely not familiar with this render server setup.
Can you give me instruction to setup a system like this so i can develop for it and test on it?