Maybe this will be helpful for user users, too.

Zitat von artofcharly

The same situation.

Solved here: RE: 2x2080TI + NVLink

So maybe reinstalling the drivers fixed the issue?

The spikes are gone now.

Anyway, at least it's working again.

I'd recommend "Spline 36".

Điều gì không được như mong đợi? Vui lòng mô tả lỗi.

What exactly is the error?

Frame rate is okay now:

[01:14:49] Timebase: 1001/30000 (29.97 fps)

But are you sure you want to have interlaced video?

[01:14:49] Interlaced: Bottom first

Please select the correct framerate in the video settings in premiere. It can't be auto detected.

[23:28:23] Timebase: -1171676313/-1841018880 (1.57 fps)

Yes, render times look extremely good except for those spikes. It seems it uses one RTX 2080 TI for decoding the source material and the other for encoding the final video.

You should get around 80-90 fps normally.

Is it possible to check this with having SLI disabled?

What error do you see?

Sounds like implementing this could solve it?

https://ffmpeg.org/ffmpeg-filters.html#subtitles-1

Does version 6.1 fix this issue?

Zitat von Vouk

If this is the case please provide a voukoder logfile.

Version 6.1

If you like Voukoder and especially if it helps saving time and money in your business - please consider supporting the project by paypal or on patreon. Thank you.

I am also looking for sponsors and partners. I am doing custom encoder solutions as well. Please contact me if you are interested.

Important

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

Fixes

• Using proper release version of FFmpeg 4.3
• NVENC encoders appear for older (Kepler) GPUs again
• Fixed NVENC default options

Changes

• Updated to wxWidgets 3.1.4

Notes

For using NVENC (SDK 10) encoders driver version 445.87 or newer is required.

Credits

Thanks to my all supporters - especially the platinum tier patron Gronkh!

Download

https://github.com/Vouk/voukoder/…oukoder-6.1.msi

Can anybody confirm 6.1rc3 is working okay?

Video encoding with NVENC doesn't make use of SLI. It just uses one GPU. That's not a limitation by voukoder, its how NVIDIA designed it.

Furthermore frames need to be rendered first before they can be encoded. This step is done by premiere and can not be accelerated by any voukoder component. You might attach your logfile here.

You'll also find more details here: Voukoder Performance Analysis

(I should really do a youtube video about this)

I guess the 1030 was designed for cheap office systems. It is a simple, passive card with low energy consumption and with the only purpose to display video.

Version 6.1 - Release Candidate 3

RELEASE CANDIDATE - NOT READY FOR PRODUCTION

If you like Voukoder and especially if it helps saving time and money in your business - please consider supporting the project by paypal or on patreon. Thank you.

I am also looking for sponsors and partners. I am doing custom encoder solutions as well. Please contact me if you are interested.

Important

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

Fixes

• Using proper release version of FFmpeg 4.3
• NVENC encoders appear for older (Kepler) GPUs again
• Fixed NVENC default options

Notes

For using NVENC (SDK 10) encoders driver version 445.87 or newer is required.

Credits

Thanks to my all supporters - especially the platinum tier patron Gronkh!

It depends on the encoder what strategies are supported.

x264: ABR, CQP and CRF

h264 NVENC: CQP, CBR and VBR

You can use CBR with the encoders supporting it.

x264 uses ABR which might be off around 10%.

Bit bitrate issue has been fixed with 6.1rc2. You'd might need to clear your presets and flush the plugin cache (switch from Voukoder to i.e. AVI and then back to Voukoder).

The bitrate issue is solved. We now focus on the empty encoder /options selection.

voukoder_h Are the issues mentioned above solved with this version? https://github.com/Vouk/voukoder/…oder-6.1rc3.msi