ls-milkyway

Now ffmpeg ...i guess also supports dssim & ms_ssim

> @ls-milkyway Why do you think FFmpeg supports DSSIM? Note that VMAF already includes an MS-SSIM computation. I mean you can [now build ffmpeg with DSSIM](https://github.com/m-ab-s/media-autobuild_suite)...yep MS-SSIM is included; example:...

**Please Note:** You can add/remove support for more native ffmpeg quality metrics...but **please do not change the JSON output structure** as I am using it extensively as an input to...

> That seems to be a [third party addon](https://github.com/m-ab-s/media-autobuild_suite/blob/b984784516ea25b925cbd38757681d659be80681/build/media-suite_compile.sh#L211-L218) not provided by FFmpeg itself. Yep, but I guess [MS-SSIM is better evaluation than SSIM OR DSSIM](https://videoclarity.com/PDF/Advancing-To-Multi-Scale-SSIM-Final.pdf)...hence you can include MS-SSIM...

Simply ...some TV fail to play VBR encodes use CQP instead.

I guess Nvencc works only with nvidia encoding options available according to nvidia's development guide.If chromaloc 2 is not mentioned then it simply cannot be incorporated.....if any time later it...

Use staxrip with proper DAR SAR AND PAR values and auto/smart crop.

Some x264 commands cannot work with nvencc because it strictly close to the commands available with nvidia hardware...check nividia encoding guide. It will bound to fail or throw errors. If...

Try: **spleeter separate -o output my_song.mp3** instead of "spleeter separate -p spleeter:2stems -o output my_song.mp3" as default commands automatically uses 2 stems......plus I am also facing problems when using switch...

hmmm.. this may be the reason why memory utilization is poor causing: [Bug] numpy.core._exceptions.MemoryError #728