tytan652
tytan652
> This feels a little out-of-scope for this PR, and feels like it would make more sense as a follow-up PR. It is not out of scope since the change...
> I think `common` would be a better name for these specific cases. There is this thread https://github.com/obsproject/obs-studio/pull/9350#discussion_r1453982017 in the PR, about the name. It was resolved, so I guess...
> What do you want to use the API for / what concerns do you have? I was trying to see how feasible it was to replace the use of...
> Input overlay still uses x11, I am still wondering why they didn't use evdev though. It does need permissions, but polkit can handle that right? No, the author/maintainers of...
Tested with Flatseal, Input Overlay will/still crash with this kind of change.
@univrsal You should check if you are on X11/Xorg since it's the only supported "platform" (and more future-proof). ``` obs_get_nix_platform() != OBS_NIX_PLATFORM_X11_EGL ``` We deprecated `_GLX` since a while so...
Remove "codec agnostic" related content, some output require to be prepared to enable a new codec.
Added `get_info` for Services API
Pushed an updated still working through the review.
> In addition to codec compatibility, we might want to have a flag in the services file to indicate compatibility with HDR (None/PQ/HLG/Both). > > Services may support HEVC or...