Beiträge von Howard Vigorita

Riguya's encoders use ffmpeg libs and have almost every option working for the various gpus. Many of which are difficult to get working with an ffmpeg command line unless you know the trick. The quality for more typical 4k settings isn't as high, however. Not sure why that is. Math libs or data width, maybe?

Zitat von Vouk

No. They are incompatible with the new license.

Perhaps a workaround might be for the Pro version to tap into x264 and x265 from the Classic version if both are install.

The vp22 connector is already in Voukoder Pro released 7/24/24. and is reported on the Vegas site to work.

I think the issue with Vegas previewing goes beyond Voukoder. Preview since vp18 is for a full-range display, best matching projects set to full-range. Renders are generally video-range. To view video-range renders to match the Vegas preview, they have to be converted back to full-range by the viewer. I do this with MPC-HC by adding the 16-235 to 0-255 preset to its Active pre-size shaders list. YouTube auto-converts uploads to full-range. So YouTube also matches the Vegas preview.

Another possibility is to render full-range. Those will match the Vegas preview without a view transform. But if you upload those renders to YouTube, it will auto-convert them even though they're already full-range. And it won't look good.

One slight problem I notice is that Pro puts up it's own Windows app tab. If I go back to the nle tab (Resolve or Vegas), I see a "Not Responding" error in the window header, and eventually a terminate or wait for response message-window from Windows. Cannot happen with regular Voukoder whose Show Dialog does not put up a new Windows app tab.

No luck with v0.7.2.6 in Vegas.

I changed the install options to install all the plugins and Vegas versions and that seemed to work on my laptop which has Nvidia 3060 & Intel Iris graphics. Voukoder Pro shows up as a render option in Vegas 19, 20, and 21 as well as Resolve Studio 18.5 b41. I can get into Pro in each Vegas but nothing happens when I try to open the Scene Designer. Won't let me do anything without a scene.

Also tried Resolve and that does work for me. Scene Designer looks pretty nice. Tried Nvenc Hevc render and it looks good. Odd that 10-bit does not show up as an option in the Resolve drop-down but does show up in the Scene Designer which in fact renders 10-bit. Another oddity is that Amd hardware render options show up in the Scene Designer but my laptop does not have that hardware. The Test Scene option detects it however.

Just upgraded Resolve to 18.5.1 b6 and Pro works still for me.

update: Just tried Vegas again and Scene Designer now works in all the versions I have installed. Seems to be using the scenes I created with Resolve. Maybe the initial install fix is to provide a default empty scene for Vegas.

Thanks, I gave all the options a try measuring with ffmpeg6 psnr, ssim, amd vmaf. Your hb options do make a difference. I'll send you the analysis.

I don't have Premiere to test with but if that's i416 format, I imagine the quality is pretty good. Hopefully some of the other NLEs will come across with similar support. Fwiw, I've also been studying frameserver output into ffmpeg and qsvencc and it seems to have the same feed as you, get getting similar quality with a v210 format from Vegas.

Curious about the Video Input block. Are you having any luck getting a 32-bit floating point feed from any of the supported NLEs? I'm particularly interested in Vegas but also use your plugin with Resolve Studio.

Tested v13 on my laptop and it works great with Vegas vp20. Tried all the qsv renders including vp9 to avi. Surprised to see the hevc accelerated renders yielding ffmpeg quality measurements comparable to x265. i9-12900hk, Nvidia 3060 gpu, Intel IrisXe igpu.

Why not solicit financial support from the commercial NLE companies who are benefiting financially from the added value your Pro plugin might add to their platforms?

Alternatively, if your plan includes tapping into ffmpeg6 decoding, your Pro product could have a stand-alone mode for transcoding . With options for 64-bit data width tapping into ffmpeg6 avx512 and/or double-precision math. You might be able to sell a small connector app within the constraints of ffmpeg licensing if it only taps into the free library used by your free plugin. Or work out commercial ffmpeg licensing for the connector app if that's the way Resolve Studio does it.

Here's a presentation that mentioned things to come in ffmpeg 6:

https://fosdem.org/2023/schedule/event/om_vlc/attachments/slides/5695/export/events/attachments/om_vlc/slides/5695/FFmpeg_VLC_js.pdf

I explained how to do it on the Vegas forum here. Works the same way with Resolve 18 Studio. Win11 22h2 adds Specific Gpu to the Windows settings without reference to power saving.

Btw, ffmpeg.exe v5 also works like that but only for decoding with Intel or Amd. Ffmpeg,exe ignores the Win setting for encoders which I detect from the command line like this:

ffmpeg -encoders | findstr "qsv"

Just tried 12beta4 with Vegas20 & Resolve 18. Now see render choices for qsv again. Have not seen them since 11.1

More for qsv h264 and hevc on my various systems with igpus, which I use allot. But right now your 11.1 plugin is the only tool I've got to do av1 or vp9 hardware encoding with the a380 whose quality metrics compare very favorably to slower software encoding.

Here's the Voukoder dialog/codecs I get on a 9900k/uhd630/Radeon7 system with Voukoder 11.1 running Vegas 20:

The Intel Qsv stuff goes away if I update to 11.3.2. Same deal on my 11900k/Arc380/6900xt system except I see more qsv with 11.1... adds qsv av1 and qsv vp9. But only if I point windows to Intel in display/graphics entries for the host app... set either to power saving (win10) or specific gpu (latest win11). When I run ffmpeg 5.1 itself, it is only influenced by the windows setting for decoding, not encoding. It just doesn't have av1_qsv and vp9_qsv but it's got the other 2 encoders no matter what the windows setting is.

Thanks. Also, for some reason not seeing h264_qsv or hevc_qsv encoders on my systems with uhd630 or uhd750 igpus if I install 11.3.2. But they do show up if I install 11.1. Can also encode with them in Win releases of ffmpeg 5.1 from gyan and btbn.

Just tried Voukoder 11.1-IntelARC with an Intel Arc a380 board and was able to do hardware renders for AV1(Intel QSV) in both Vegas 20 and Resolve18 Studio. But not with 11.3.2. Curious what ffmpeg is used for 11.1... I cannot find an ffmpeg with "av1_qsv" as an encoder... only as a decoder in 5.1-full.

Unfortunately hevc lossless does not seem to be implemented in Voukoder even though it is implemented perfectly in ffmpeg with a transcode script such as this:

ffmpeg -i "INFILE.MOV" -c:v libx265 -x265-params lossless=1 "OUTFILE.MOV"

x264 cannot actually achieve lossless. It's lossless setting is close but ProRes422 is generally a little better quality, faster rendering, and smaller. MagicYUV is another possible option.

Tried the 9.4rc1 "HEVC (Intel QSV)" codec with no other dialog changes in Vegas 19 and it rendered fine showing substantial Intel decoder utilization in Task Manager. That selection does not appear in my 9.3 dialog. The system I tested 9.4rc1 has a 9900k cpu with a Radeon VII gpu. The system still running 9.3 in which the selection did not appear is an 11900k with a 5700xt.