Yeah I see what you mean. Maybe editing "keyer" in the OBS config to "3" would override it to actually allow RGB. But I'm not sure.
-
-
Replying to @der_rod
It's a Decklink Mini Monitor 4K, so only 1 output. I have no options at keyer.pic.twitter.com/ttFmZaMnf0
1 reply 0 retweets 0 likes -
Replying to @Qun
Yeah that's why I suggested editing the config (not sure what file it's in though). Only valid modes are 1 and 2, but it only checks if the number is greater than zero where it decides between RGB and 4:2:2. So setting it manually *might* work.
1 reply 0 retweets 0 likes -
Replying to @der_rod
Found the file. Setting the keyer to 3 and and making it autostart (so it doesn't overwrite the CFG). It's confirmed 4:4:4 now in my stream PC OBS, but I'm getting major encoding lagpic.twitter.com/Ag1GtvuOGC
1 reply 0 retweets 0 likes -
Replying to @Qun
Mh that's unfortunate but I can't really tell you why that happens. Colin is the main guy for DeckLink stuff so if he can reproduce what you're seeing he might be able to nail it down. With my shuttle I may still be able to figure out the 709/601 issue though.
1 reply 0 retweets 0 likes -
We've used the Decklink extreme with K/F on a few shows, and it while it renders in RGB, the colorspace is still wonky. Depending on your final destination (hardware), sometimes 601 partial gets you the most accurate colors. Regardless, RIP 444 either way
1 reply 0 retweets 0 likes -
Replying to @tomberino @Qun
Yeah I think the colorspace is just never set so blackmagic's SDK defaults to 601. Not sure why RGB is doing so poorly though.
1 reply 0 retweets 0 likes -
Replying to @der_rod @tomberino
I don't understand the encoding lag at all on 709/RGB. I don't see increased CPU or GPU usage, my hardware is strong enough (i9-7900X + RTX 2080) and it's only 1080p25 (my capture card on other PC doesn't accept 4:4:4 above 1080p30).
1 reply 0 retweets 0 likes -
Replying to @Qun @tomberino
If you post an issue on github include a log from that happening *after* OBS has been closed. The profiler might help nail down where the bottleneck here is.
2 replies 0 retweets 0 likes -
Oh, thats not encoding lag. That's a straight up failure of the encoding engine. You're pretty much not pushing anything usable out of OBS at this point. any failures in the encode just shows up as dropped frames. In that SS, your CPU is not even being used
3 replies 0 retweets 0 likes
I've run into Decklink driver/hardware failure before as well as thats what OBS translates it as.
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.
