Strange... why did I make this change?

https://github.com/Vouk/voukoder/…74c6dcf13534e19

Please try this version: https://github.com/Vouk/voukoder/…oder-7.2rc1.msi

Maybe i'll have to use a more recent Plugin SDK to fix this issues. I'll take a look at it when I find some time.

I found the switch to tell VEGAS it can accept HDR10/HLG. Still struggeling getting VEGAS to tell Voukoder the correct:

• eMatrixCoefficient
• eTransferCharateristic
• eColorPrimaries
• eColorRange

Version 7.1

Over 25,000 users used Voukoder last month! An unbelievable number, equal to the number of inhabitants of a small town. But who are these users and in what areas does Voukoder make their job easier?

In a series of YouTube videos I would like to introduce your business / channel / company to the viewers while I'm unboxing a parcel with your merchandise. For information on how to participate please follow this link.

Fixes

• Had to update the NVENC SDK to 9.1 again to make multiple ref frames working. This unfortunately drops support for older GPU's (i.e. Kepler). In the Voukoder successor these can be supported again as encoders will be plugin based. If you are affected by this change please continue with version 7.0.

Notes

Make sure you are using the latest connector for your application(s)!

For using NVENC (SDK 9.1) encoders driver version 436.15 or newer is required.

Credits

Thanks to my all supporters, either by PayPal or by Patreon.

Platinum patrons

Gronkh

Silver patrons

Chris Woods, Kai_307 (Kai C. Ternes), Michael Wooldridge, Schauerland

Try this version: https://github.com/Vouk/voukoder/releases/tag/7.1rc1

The plan is the new voukoder is autodetecting this kind of settings from the GPUs driver software.

Can you please do a logfile with low-level debugging enabled?

I'm actually currently working on this one. But this might still take some months.

To be honest I lost track of this topic. I'm kind of overworked right now.

Edit: I have difficulties compiling FFmpeg with libass for windows. I don't find anything helpful on Google about this.

See, I'm doing this as a one-man hobby project after my regular work and also on saturday and sunday. Voukoder is currently free and I don't get much money from it. In fact if I wouldn't do the Voukoder I'd have more money. This means I have to focus on my day job and replying sometimes might be late. It might take 23h or even 3 weeks.

File size estimation doesn't work CRF/CQP so it got removed.

NVENC SDK > 9.1 would cause a breaking change in encoder settings.

Just be a little more patient and read my reponses carefully. The bug should have been fixed in this version.

Zitat von Vouk

Please try this version: https://github.com/Vouk/voukoder/releases/tag/7.1rc1

Happy new year to you too.

Please try this version: https://github.com/Vouk/voukoder/releases/tag/7.1rc1

Nice to hear its not a Voukoder bug.

Can you please stop making new topics for the same issue again and again? I already said in the first one that Voukoder is currently broken. about that "ref frames" setting.

Unfortunately I am currently extremly busy with my day job and can't provide a fix instantly. Sorry.

First advise, please try to write one response. You can edit it again, if you want to add something or correct it.

Multiple ref-frames seem to be broken right now.

I'm not an expert with this topic. Maybe somebody else has some experience with hardware decoders?

[13:00:27]   FFmpeg: Multiple reference frames need SDK 9.1 at build time
[13:00:27]   FFmpeg: No capable devices found
[13:00:27]   FFmpeg: Nvenc unloaded

Seems I really have to go with the latest SDK at some point (and drop support for old GPUs).

Where do I find the log file?

Zitat von visionicloud

If I do the Voukoder settings just like in H.264 is it alerting me as an error during export? What is this? Or is one setting wrong?

Please provide a low level voukoder log file.

Try to update/reinstall your NVIDIA driver software.

This is asked quite often and you'll find some answers in the existing threads:

TL;DR: Voukoder is only handeling the encoding part of the export. If Premiere is slow with rendering each frame before it's sending it to the encoder voukoder can't improve it.

[19:38:25] Frame #520: vRender: 76980 us, vProcess: 7 us, vEncoding: 13975 us, aRender: 57 us, aEncoding: 1188 us, Latency: 92275 us
[19:38:25] Frame #521: vRender: 64296 us, vProcess: 9 us, vEncoding: 13036 us, aRender: 53 us, aEncoding: 1080 us, Latency: 78492 us
[19:38:25] Frame #522: vRender: 53933 us, vProcess: 6 us, vEncoding: 13430 us, aRender: 56 us, aEncoding: 1140 us, Latency: 68601 us
[19:38:25] Frame #523: vRender: 83936 us, vProcess: 5 us, vEncoding: 13734 us, aRender: 90 us, aEncoding: 1135 us, Latency: 98920 us

Premiere already needs ~80ms to render (vRender) a frame (decompressing the sources, filters, effects, ...). That limits the export to 12.5 fps. The GPU is pretty much ideling because it is waiting for frames from premiere.