Beiträge von Vouk

Does it work when you start VEGAS with admin rights?

If I correct the file paths so they match my system I got it working:

But I had to run the Designer.exe as administrator. Can you try this?

In the encoder node change the format from YUV 420 to CUDA.

0.7.2.3 brings initial CUDA support!

Note: In the encoder node you need to set the pixel format to CUDA.

Great this issue is solved now!

Thanks for your feedback.

1. I removed that popup message box.
2. The problem was with the YUV 422 (10 bit) format. The other formats work fine. I removed it in the latest build until I find the reason why it produces a larger file size than the source material.

[11:44:27] - Video -------------------------------------
[11:44:27] Frame size:      5472x3078
[11:44:27] Pixel aspect:    1:1
[11:44:27] Timebase:        1001/24000 (23.98 fps)

[11:45:41] - Video -------------------------------------
[11:45:41] Frame size:      5472x3078
[11:45:41] Pixel aspect:    1:1
[11:45:41] Timebase:        1001/60000 (59.94 fps)

[11:46:43] - Video -------------------------------------
[11:46:43] Frame size:      5472x3078
[11:46:43] Pixel aspect:    1:1
[11:46:43] Timebase:        1001/60000 (59.94 fps)

[11:48:11] - Video -------------------------------------
[11:48:11] Frame size:      5472x3078
[11:48:11] Pixel aspect:    1:1
[11:48:11] Timebase:        1001/60000 (59.94 fps)

The first one was started with 23.98 fps. The other 3 ones with 59.94. Voukoder uses the framerate you have set in your NLE. Can you double check it's really set to 23.98 fps in DVR?

This is most likely not a Voukoder issue.

auluswang You might try 0.7.2.1. I'm setting color space, etc there.

What framerate did you select in your NLE? Can you share your voukoder logfile? (See the sticky post in this thread.)

I'm checking this ...

It's available in the downloads section now.

Zitat von Abd

I found a bug: the latest 13 or 12.1, in Davinci studio 18.5beta or 18.5, the data level (Auto, Video, Full) is missing. However, in Studio 18.1.4, it is ok.

Zitat von dream

Same thing for me. Im using 13.1 Voukoder with the latest connector.

Can you try updating DVR to 18.5.1 build 6 (Latest version) and see if this is fixed? I don't have control over that setting. DVR decides if it shows it or not.

I have tried to reproduce it, but in my case it works:

Can you provide an example clip with steps on how to reproduce it?

Zitat von auluswang

1. VoukoderPro created mov file, during checking by MediaInfo app, the mov files cannot show 'color range' and so on parameters, any plan to add the showing function to VoukodePro ?

If I just could remember why I removed these lines from the code ... AFAIK there was an issue with HDR export ...

Need to check this.

Zitat von auluswang

2. During the similar "bit rate" level compare DRS (18.5.1) created mov file with VoukoderPro (0.7.1.11) created mov file, during playing from image quality perspective, DRS created is visiablely better than VoukoderPro's.

I strongly suggest to avoid bitrate based encoding until it is absolutely neccessary. It's better to use quantizer parameter based strategies. The Voukoder presets are complex and quite more than just the bitrate.

Yes, I need to bring that into VoukoderPro ...

Sure. will do.

Made another fix regarding the filesize / compression. There was in fact an issue some settings were not applied.

I used your scene to export the file which was playable with MPC HC, MPC BE and VLC.

Can you provide an example DVR project I can use to investigate the crashes?

You can try to holding SHIFT-CTRL during startup and clear the plugin cache.

I have checked (and fixed) this.

"Main 10" requires "YUV 420 (10 bit)" to be set. I have added this option to the format dropdown.

Can you test if the build below fixes this for you?

Zitat von Abd

I found a bug: the latest 13 or 12.1, in Davinci studio 18.5beta or 18.5, the data level (Auto, Video, Full) is missing. However, in Studio 18.1.4, it is ok.

I am using DVRS 18.5 and the data level control is visible to me. I also have no control whether it is visible or not. That's in DVRS' control.

Zitat von Abd

By the way, I hope the voukoder can establish a Linux release. Linux can use the Nvidia 12bit 4:4:4 h265 8K hardware decoding, while windows only 10bit 420.

VoukoderPro is designed to be working on Windows, MacOs and Linux. Once it is working on Windows i'll work on the other builds.

Zitat von Abd

in voukoder pro, the lack of x265 an x264 is a pity, while nvenc 4:4:4, no matter how I choose 12bit or 10bit, it can just be 8bit. that's a problem.

Yes. I'm working on that.

Do you mean this one?

Encoder ffvhuff [Huffyuv FFmpeg variant]:
    General capabilities: dr1 threads
    Threading capabilities: frame
    Supported pixel formats: yuv420p yuv422p yuv444p yuv411p yuv410p yuv440p gbrp gbrp9le gbrp10le gbrp12le gbrp14le gbrp16le gray gray16le yuva420p yuva422p yuva444p gbrap yuv420p9le yuv420p10le yuv420p12le yuv420p14le yuv420p16le yuv422p9le yuv422p10le yuv422p12le yuv422p14le yuv422p16le yuv444p9le yuv444p10le yuv444p12le yuv444p14le yuv444p16le yuva420p9le yuva420p10le yuva420p16le yuva422p9le yuva422p10le yuva422p16le yuva444p9le yuva444p10le yuva444p16le rgb24 bgra
ffvhuff AVOptions:
  -non_deterministic <boolean>    E..V....... Allow multithreading for e.g. context=1 at the expense of determinism (default false)
  -pred              <int>        E..V....... Prediction method (from 0 to 2) (default left)
     left            0            E..V.......
     plane           1            E..V.......
     median          2            E..V.......
  -context           <int>        E..V....... Set per-frame huffman tables (from 0 to 1) (default 0)

Yes, I might add that.

Edit: Added it to VoukoderPro.