mirh

Ok, I see it now. You can tinker with that after you enable *Show Pics Player*. Too bad that I cannot get it to work with the flowframes ini, but...

Ok, actually, nevermind. I'm still getting this even with 1.35 (and yes, I did disable autoencode and enabled scene detection) Count of scenescuts in INI and scenecusts of png folder...

Ok, actually the magenta cloud link is updated behind the scenes. Latest version is 13.0, which has no problem with my current flowframes. It's pretty nice and smooth looking in...

Mhh no? Putting aside the somewhat academical argument on whether -crf=0 is really any practically inferior to qp=0, or if instead the difference couldn't be eventually just mathematical navel gazing......

This is probably a duplicate of https://github.com/n00mkrad/flowframes/issues/52 In the developer options for ffmpeg, add `-bsf:v h264_metadata=matrix_coefficients=6` as additional argument.

-.- Just follow the links and you see everything explained thoroughly. There's also an additional ffmpeg bug when importing jpeg pictures.

"AI engines" work internally with RGB for simplicity reasons (and VS makes no effort to hide that), and that's ironically the deal here. They don't do anything with chroma themselves,...

> This sucks, but we can at least report this to the devs I reckon. https://trac.ffmpeg.org/ticket/9167 https://trac.ffmpeg.org/ticket/979 https://trac.ffmpeg.org/ticket/9693 https://trac.ffmpeg.org/ticket/9672 > It's redundant I know - The examples I provided are...

 The videos are pretty different actually, inside (putting even aside their source.. I'm not sure what kind of platform would be delivering you H265 clips) Anyhow, the problem can...

Pretty odd, especially considering the [lack](https://urlebird.com/video/ayo-sock-is-dancing-again-6981520224210144517/) of watermark. Anyhow, I just found out that ***even*** disabling "Import HQ JPEG instead of PNGs" still isn't enough to fix the problem. ffmpeg.exe...