Beiträge von Vouk

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

I was not aware people run parallel instance of it, but anyway, that's a good and valid test.

I disabled the performance logging for now. Need to find a better solution for it.

Can you send me your DVR project with a short clip? a few frames is enough.

It looks like you have two audio output busses there, right?

It works here. no issues.

Can you try going to "add and remove software" and uninstall all VoukoderPro related items, then install the latest version again?

Investigating ...

Edit: Found the issue: Circular std::shared_ptr's - I finally found a use case to use std::weak_ptr

Can you try version 0.7.2.8?

I can reproduce this when encoding with CUDA.

Normal NVENC encoding seems to be okay.

Edit: Should be fixed in the next version.

Edit: Fixed with 0.7.2.7