mirh

Parsing source code still seems exponentially less wasteful (for as much as instead, there is more complexity in the code to write)

Mhh.. well, how could I say it. The long story short is that ffmpeg is fuuuuuucked with color management. https://github.com/n00mkrad/flowframes/issues/84

https://github.com/n00mkrad/flowframes/issues/123 It's absolutely a bug. But the culprit is ffmpeg technically.

Yes, I literally provide them in my link.. (even though whether it will work or not, depends on the mood of the half-assed flowframes workaround)

No, that's completely wrong. Only extraction to jpeg is broken. Png is fine. But what you have in mind is surely the *other* bug, i.e. the one in the encoding...

Oh, FFS I want to die. I'm speechless. >_< great @ValZapod I summon you Yes, there seems to be a small difference even when you remove gAMA.

Sigh... Am I going to assume this is https://trac.ffmpeg.org/ticket/9672? Or is the sRGB chunk/handling unrelated to ICC?

So.. then.. am I correct in believing there's no bug report about this issue on the tracker? EDIT: https://trac.ffmpeg.org/ticket/10000 > Well, that BUG is technically fixed, because we added support...

If your issue is a big SD/HD difference, that must necessarily be the lack of [tagging](https://trac.ffmpeg.org/ticket/9167) that I hinted from my first post. You may have been headbanging while trying...

The [tool](https://itch.io/profile/christianundco) is pretty cool, if rough. But that only helps you with (duh) *choosing transitions*. In other words, ***how*** they happen, as opposed to ***when***/***if***.