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.
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.
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
In the video encoder node switching from CUDA to YUV 420 should help.
This feature was one of the main goals of VoukoderPro.
I'm always open for improvements / suggestions.
Can you export and send me that scene file?
Yes, but I had to add that muxer formats.
This is a strange one.
VoukoderPro brings all components and dependencies with it in it's installer. It does not need FFmpeg to be installed, it has its own ffmpeg dlls in system32.
Can you share your VoukoderPro logfile %LOCALAPPDATA%\VoukoderPro\logs\*
You can try reporting this issue in the blackmagic forum or ask their support.
Yes, in the NLE you select the format the NLE is sending to VoukoderPro. In VoukoderPro you need to select the actual format you want to have in the file.
You can upsample YUV 420 8 bit to 10 bit, but the visible data is sill 8 bit.
You should even have a shortcut icon on the desktop to start the designer.
So why not have a dropdown menu in the Vegas template itself which allows you to select which pixel format to use? Perhaps accompanied with a helpful hint that if you use YUVA with certain CUDA functions, you're screwed! See below for a mockup of what I mean.
This is how VEGAS Pro works. Some important parameters have to be defined in the template.
What video/picture format does Vegas pass to Voukoder?
I'm using I420, P010 and A410. All uncompressed of course because that's how I can feed the frame into FFmpeg.
I noticed VoukoderPro receives the frame data as 'yuva444p16le', which means you are most likely using this preset:
When using the CUDA pixel format I guess it chooses a pixel format for output that matches the input format. I have not found a way to say 'Once you have finish scaling it encode it as nv12' to the file.
But does it work if you select the 'YUV 4:2:0 (8 bit)' template? This is 'nv12'.
P.S.: I'll also add the 'hwdownload' bilter, but I doubt it makes much sense to upload the frame to gpu, scale it, download it to the cpu, then upload it again to encode it ...
P.P.S: I need to find a way to set the target pixel format if i just send 'CUDA' to the encoder.
Can you paste the voukoderpro logfile (%LOCALAPPDATA%\VoukoderPro\logs\ ...) entry?
What exact encoder are you trying to use?
If it's NVENC try to update you driver software.
Does it work when you start VEGAS with admin rights?