…wait, how does one even manage to have chroma siting problems in 4:4:4?
-
-
-
Replying to @marcan42
this sounds like it might be somehow either an OBS bug or a libavcodec bug? like, I cannot fathom a way for this to be an issue with the ProRes format itself, you couldn't fuck that up if you tried
1 reply 0 retweets 2 likes -
Replying to @11rcombs
I bet at some point it's going through yuv420p, badly.
1 reply 0 retweets 3 likes -
Replying to @marcan42
that or some 4:2:2 intermediate? (is it vertical, horizontal, or both?)
1 reply 0 retweets 0 likes -
-
Yeah. yuv422p *and* bad scaling? Looks like every second chroma sample gets dropped/clobbered with the first. qtrle top, prores bottom, via OBS. mpv/ffplay show the prores file properly (same as the top).pic.twitter.com/JOweWvAn61
1 reply 0 retweets 3 likes -
Oh and there's definitely a colorspace conversion issue too.
1 reply 0 retweets 3 likes -
Confirmed that it's a yuv444p16 problem. yuv444p works. yuv422p works as intended (better than that messed up yuv444p16 output)... but crashes OBS after a few source restarts. lol.
1 reply 0 retweets 4 likes -
Opened a bug, we'll see what they say.https://github.com/obsproject/obs-studio/issues/3057 …
1 reply 0 retweets 6 likes
Apparently the problem was SWS_FAST_BILINEAR. I'm not sure if that's expected behavior or a swscale bug...
-
-
Replying to @marcan42
if you set the fast flags I feel like nothing's guaranteed quality-wise
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.