1 Reply by johngalt

(4 replies, posted in Using SVP)

Chainik wrote:

ah, and it only works with GPU acceleration enabled

Thank you, switching to rocm and gpu accel solved this issue (though my Polaris struggles a bit compared to CPU, possibly due to the scaling shaders already running on it). Perhaps it should be added to the 4k/hdr wiki page that 10 bit output only works with gpu acceleration enabled.

This thread can be closed :+1:

Edit: my performance issues were only from the separate chroma upscale shader I was using in combination with FSRCNNX. Disabled the chroma upscale shader, and getting solid performance no matter svp settings!

Go to forum: Using SVP

2 Reply by johngalt

(4 replies, posted in Using SVP)

Chainik wrote:

obviously you need a 10-bit source file

This is the source file: Stream #0:0: Video: hevc (Main 10), yuv420p10le(tv, bt2020nc/bt2020/smpte2084), 3840x1608 [SAR 1:1 DAR 160:67], 23.98 fps, 23.98 tbr, 1k tbn, 23.98 tbc (default)

Here you can see the script is given yuv420p10 source, and outputs yuv420p (as expected due to the generated script always having YUV420P8 as format): https://bpa.st/raw/ULFQ

Though this isn't the only issue since editing to YUV420P10 (generate.js) doesn't work either due to the SVSuper error posted as well (second link in OP), seemingly limiting to NV12.

I have a large library of UHD 10 bit content, and tested extensively to see if any files are handled as expected in svp, and unfortunately they all run into these issues.

Go to forum: Using SVP

3 Topic by johngalt

(4 replies, posted in Using SVP)

SVP on linux (using mpv) always outputs 8 bit video no matter if allow_10bit is true or false. The generated script also doesn't differ between the options, with format=vs.YUV420P8 always set. Full generated script: http://ix.io/2uD1

When attempting to force it by changing script/generate.js, I ended up getting the following SVSuper error complaining that the clip must be YV12: http://ix.io/2uD9

Go to forum: Using SVP