llyyr

> related issue with #13991 It is not, they say it works fine with --no-config and mpv could never saturate a RTX 2070 no matter what built-in options you used.

I can't reproduce this issue on sway master, would be interesting if OP is also on sway 1.8.1 as that would likely mean the issue is with sway/wlroots and has...

What does "unstable" mean and how are you checking your refresh rate? And what is your configured modeline?

> target-colorspace-hint=yes Is this relevant to reproducing the issue? Also I can't reproduce on sway, can you try another compositor?

Is this still an issue? I still can't reproduce this. If this only occurs with `target-colorspace-hint=yes` then the issue is most likely elsewhere

This is known, and not really a priority atm since the deprecated fields aren't going away anytime soon as far as I understand.

> Hm. Would it perhaps make more sense to put this under `ASS_OVERRIDE_BIT_BORDER` if you want to reuse one of the existing bits? After all, what exactly gets blurred is...

> Currently blur can already and also only be overridden by `ASS_OVERRIDE_FULL_STYLE`. Looking at the motivating mpv issue, wouldn’t `FULL_STYLE` be a good match for `override=force`? No, we don't want...

Hmm, I think ASS_OVERRIDE_BIT_BORDER makes most sense for mpv. FONT_SIZE_FIELDS is also fine. I'd prefer it not be part of ASS_OVERRIDE_BIT_ATTRIBUTES though.

> Can you elaborate on why not `ATTRIBUTES` ad why `BORDER` works for mpv, so the usecase is better understood? When you set `--sub-ass-override=force` with `ASS_OVERRIDE_BIT_ATTRIBUTES`, mpv will apply every...