[27.0.1] UI bugs (serious)

[Mishasama]

1. My mic is stereo, and it was displayed correctly in the 26.0.2-ME, but not now. It always shows as 7.1 channels even after restart obs. (My general channels settings is 7.1)

2. Settings -> Advanced -> Hotkeys

3. Menu -> Tools -> OBS WebSocket

[pkviet]

Not a bug ! It's as intended; I've changed the meters display per this commit: https://github.com/pkviet/obs-studio/commit/5a382f86dce7a4e405bba9de78658583a4536d54 The reason is quite intricate but it solves an old bug in original obs; context is explained here: https://github.com/obsproject/obs-studio/pull/1540 I'll summarize:

• obs processes audio in the pipeline: audio -> resample to output number of channels -> filters -> input meter
• so what is displayed in obs input meter is NOT a clean input but it's been upmixed from stereo to 7.1 in your case.
• why did it show previously only two channels ? because Jim (obs main dev) decided to hide the excess output channels. It works for stereo input but in some more general cases it does not (for instance mono source routed to channel 3 or later).
• so what you are seeing now is the real result of the upmixing of your stereo source; two channels are active (the first two) while the others are not because the resampler matrix for stereo ==> 7.1 is written like this in ffmpeg swresample library.
• there's NO difference in the audio processing so don't worry. It's just a different more accurate display.

[Mishasama]

Okay, got your intend and agree, it's much clear now.

What about another two? Do I have to build it myself in the future? Or even have to sync codes to the last release myself? 😅

[pkviet]

Ah for 2 and 3 that's just the ini files which need to be updated with the strings. They're in obs-data folder. You can do it manually with a text editor. No big deal. No need to compile anything.

[Mishasama]

Er... What's your plan for the future update? I saw you say you won't release any more in the future. The original OBS will be updated in the future. Should I have to learn how to sync and compile it now for preparation? (If I want to fix it for other people?)

[pkviet]

Well, I think it's not maintainable by somebody else because each obs update requires extensive rebasing with non trivial, usually, adjustments to obs ME code .... If you want to try your luck, you're welcome of course. But the learning curve will be super steep. You not only need familiarity with obs code but also with our changes to libobs and UI. Frankly it had become too much of a hassle so that's the main reason I don't want to maintain. Each obs update breaks stuff in obs ME which I'd have to fix.

On Mon, Jul 19, 2021, 12:17 Misha @.***> wrote:

Er... What's your plan for the future update? I saw you say you won't release any more in the future. The original OBS will be updated in the future. Should I have to learn how to sync and compile it now for preparation? (If I want to fix it for other people?)

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/pkviet/obs-studio/issues/59#issuecomment-882428639, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACG2OT5IYQIOR2HBKBUZW7TTYP3R5ANCNFSM5AQPDKPA .