Beiträge von Vouk

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?

Added.

Zitat von Joe24

So there is no actual problem.

Nice!! Well, you've still got the improvement of a named device dropdown instead ofentering the device number

Zitat von Joe24

It would certainly be nice to run multiple GPUs from a single Vegas render, but if this is in fact an FFmpeg limitation, I guess there's not much anybody can do about it except to run multiple Vegas instances, each controlling it's own GPU. Unless VoPro could run multiple FFmpeg instances from the same Vegas output buffer?

Voukoder(Pro) doesn't use an FFmpeg binary (as most other tools do), it's using its DLL variants. So for each export it creates a new instance. But you can test your filter chain witz the command line ffmpeg version.

In line 65 of your previousely posted log file you can see the text representation of the filter chain:

buffer@9309cf357e4c40e3b1334754fe21a3f3=width=1920:height=1080:pix_fmt=yuv420p:time_base=1001/24000:pixel_aspect=1/1,hwupload_cuda[673157b8b5c94fcbb6460873239f5e54];[673157b8b5c94fcbb6460873239f5e54]split=2[split_74972bd9eab84782948d76fe847c9664][split_21f42936466e4121b3817c10e2155724];[split_74972bd9eab84782948d76fe847c9664]scale_cuda=w=1920:h=1080:interp_algo=3:force_original_aspect_ratio=1,hwdownload,hwupload_cuda=gpu=1,format=pix_fmts=cuda,buffersink@a5bebec201e640c6940a6f7d9caca738;[split_21f42936466e4121b3817c10e2155724]scale_cuda=w=1280:h=720:interp_algo=3:force_original_aspect_ratio=1,format=pix_fmts=cuda,buffersink@bc23b883870a452fa61cea7d0d361e4c

Just append it to the ffmpeg.exe command line using -filter_complex.

Zitat von Joe24

it would make more sense to have each node 'inherit' the GPU assignation of the previous (upstream) node

Yes, and setting the encoder pixel format automatically to CUDA. I might add that later.

Please check out 0.7.3. Please tell me if this works. (I don't have multiple gpus in my machine)

Please check out version 0.7.3.

Supporting these variables in the file name:

Please check out version 0.7.3.

I have already implemented something like this which you will be able to test soon.

Just want to finish the other tasks and then do a new build.

Encoders:

Upload filter:

I'll look into this again.

Thanks for pointing out these edge cases. It's really helping to improve the software.

Will look into that.

Yes, I will add VP9.

Yes, this will come soon!

[19:07:28] Frame #103383: vRender: 2035282 us, vProcess: 0 us, vEncoding: 22269 us, aRenderEncode: 301133 us, Latency: 2358705 us
[19:07:29] Unable to encode video frame #103384! Aborting ...
[19:07:29] Exported 103384 frames in 34233 seconds. (avg. 3 fps)
[19:07:29] Flushing encoders and finalizing ...
[19:07:29] Video and audio buffers flushed.
[19:07:29] Trailer has been written.
[19:07:29] Closing encoders ...

Can you enable "Low Level Debugging" in Voukoders Settings? This should log more data (and the actual error). Sorry, I know that's a 10 hrs encode ...

Are you sure there's enough drive space left?

Out of curiosity: Does this also happen when performing a Scene Test (Play button in VoukoderPro) multiple times? Or only if VEGAS Pro is involved?

Okay, so the issue is solved?

Updating now ...

Edit: You're right. With the latest version these option won't show up. Seems it's a DVR issue.

Some people are reporting this from time to time, but I'm not sure why this is happening. I have no possibility to turn this on or off.

On my side all options are there:

Can you post a screenshot of your GPU memory of these multiple renders in a row again?

Did this export with the 'doesn't work' scene:

Are you using the YUV 420 8 bit template too?

Can you tell me the CUDA filters that do not work?

Win 11, same Nvidia drivers (non patched) and VEGAS Pro 21 here.

To be honest: I don't really see the huge memory leak you have shown in the screenshots. It looks like this on my system.

I (re-)started the render about a dozen times, but the memory usage is not accumulating. Sometimes it's 300 MB more, but Windows and VEGAS are using GPU memory too.

I don't have a Citrix environment available to test the scenario you've mentioned above.

Edit:

One more test with UHD footage:

6,3 GB when rendering

4,3 GB when finished