How to disable autoconvert for video filter chain?

[CrendKing]

If I have a VapourSynth script that only takes RGB float format (such as most models from vs-mlrt, I have two ways to give it: 1) Use the VapourSynth Resize filter to convert to vapoursynth.RGBH from within the script before feeding to the model, or 2) use the format filter from mpv.

From my understanding, if hwdec is on and I do 1), autoconvert kicks in and first convert nv12 to yuv420p, then feed it to the script, then the script has to do the second yuv420p -> rgb conversion. But if I do 2) with options like --vf=format=fmt=gbrpf16,vapoursynth=<script>, I see autoconvert also kicks in, first convert nv12 to gbrpf16, then immediately convert gbrpf16 to yuv444p16, then feed it to the script. Either way the VapourSynth script never gets a RGB float input clip.

Is there somehow a way to disable autoconvert either by option or automatic when certain filters (e.g. VapourSynth) that have potential to convert formats are in the chain?

Relevant log section:

[   1.502][v][user_filter_wrapper] Setting option 'fmt' = 'gbrpf16' (flags = 0)
[   1.502][v][user_filter_wrapper] Setting option 'file' = 'D:/vsmlrt.vpy' (flags = 0)
[   1.502][v][vapoursynth] using 16 concurrent requests.
[   1.566][v][vf] User filter list:
[   1.566][v][vf]   format (format.00)
[   1.566][v][vf]   vapoursynth (vapoursynth.00)
[   1.566][v][cplayer] Set property: vf="format=fmt=gbrpf16,vapoursynth=\"D:/vsmlrt.vpy\"" -> 1
[   1.566][v][vf] [format] 1920x1080 d3d11[nv12] bt.709/bt.709/bt.1886/limited/display CL=mpeg2/4/h264 crop=1920x1080+0+0 A=none
[   1.566][i][autoconvert] HW-downloading from d3d11
[   1.566][i][autoconvert] Converting nv12 -> gbrpf16
[   1.569][v][swscale] using 14 threads for scaling
[   1.573][v][swscale] Using zimg.
[   1.574][v][vf] [vapoursynth] 1920x1080 gbrpf16 rgb/bt.709/bt.1886/full/display CL=mpeg1/jpeg crop=1920x1080+0+0 A=none
[   1.574][i][autoconvert] Converting gbrpf16 -> yuv444p16
[   1.574][v][swscale] using 14 threads for scaling
[   1.576][v][swscale] Using zimg.
[   1.582][d][vapoursynth] initializing...

[CrendKing]

Also, it seems the RGB format in VapourSynth are actually packed instead of planar, so instead I need rgbf16? Tried it and it doesn't work: can't find video conversion for nv12. Not sure why since I believe both mpv and VapourSynth use zimg to do the conversion.

[hooke007]

Either way the VapourSynth script never gets a RGB float input clip.

Wait, from my memory. The last pr of vs is created by you and you mentioned ...

Still restricts to only YUV formats. YUV formats are tend to be the most structured and consistent color family. Also the most popular.
#14326

Or i mixed up sth?

[CrendKing]

No, you didn't. You are correct. I didn't even mention about supporting RGB colorspaces since it wasn't supported before. I should've known that autoconvert is inserted due to the filter img format declaration. Besides, these float RGB packed formats are mainly for GPU usage (as for the vs-mlrt use case), and VapourSynth is usually focused on CPU side, so there is no good reason to support the RGB colorspaces in mpv anyways.

Thanks for the help!

[kasper93]

I don't know if the conversion you see make sense, would have to look at details. But there are two important things to remember 1. downloading hardware frame is limited to formats supported by hardware/driver 2. input to vapoursynth filter is limited by accepted formats by current implementation.

The autoconvert logic tries best to minimize conversion and select best format to avoid losing data. If you see anything particularly wrong please report issue, autoconvert logic could be improved if needed.