@DrSupermanShadow What koala said.
What you're asking for is how you support a single-function app that does nothing beyond that one pre-defined thing with almost no options. OBS allows anything and everything that someone might want to do, and so it's inherently technical with no way to avoid that. If you can't handle the technicality, go somewhere else. Use a single-function thing.
---
The "wrong" settings that you have, whatever they are, might be exactly what someone else needs to do what *they* want. There's no universal "right" or "wrong" setting. If everyone is supposed to have the same setting, why is it even a setting? Why not hard-code it?
Kinda like people that insist on keeping the faders/sliders of a mixing console at 0dB/unity all the time, always, as if they're glued there. Then they end up mixing on the preamps or somewhere else, which messes things up that are supposed to be unaffected by normal mixing, like the performers' monitor mixes. That's already a problem, but it makes even less sense when you consider that the faders are the most expensive controls on the board, in terms of both parts cost and real estate. Why go to all that expense, if they're "supposed to" stay in one specific position? Why not hard-wire that bit of processing behind the panel and not have those controls at all?
(yes, that *is* a real point of contention in the audio-production world)
Likewise for any other physical control or software option. If it exists, then it should be expected for all of its possibilities to be useful in some context. Just, "set it here," with no more explanation than that, *might* solve the immediate problem...*might*...but it'll certainly cause others, in different contexts that need a different setting.
Your one situation is tunnel-vision. That doesn't work for the wide variety of situations that OBS is used in. And because we've seen a lot of that variety on the forum, it also doesn't help to tell us, "it doesn't work," with not much more than that. What you have may very well work perfectly for someone else's rig, and with nothing to go on, we don't know yours from theirs.
What you're asking for is how you support a single-function app that does nothing beyond that one pre-defined thing with almost no options. OBS allows anything and everything that someone might want to do, and so it's inherently technical with no way to avoid that. If you can't handle the technicality, go somewhere else. Use a single-function thing.
---
The "wrong" settings that you have, whatever they are, might be exactly what someone else needs to do what *they* want. There's no universal "right" or "wrong" setting. If everyone is supposed to have the same setting, why is it even a setting? Why not hard-code it?
Kinda like people that insist on keeping the faders/sliders of a mixing console at 0dB/unity all the time, always, as if they're glued there. Then they end up mixing on the preamps or somewhere else, which messes things up that are supposed to be unaffected by normal mixing, like the performers' monitor mixes. That's already a problem, but it makes even less sense when you consider that the faders are the most expensive controls on the board, in terms of both parts cost and real estate. Why go to all that expense, if they're "supposed to" stay in one specific position? Why not hard-wire that bit of processing behind the panel and not have those controls at all?
(yes, that *is* a real point of contention in the audio-production world)
Likewise for any other physical control or software option. If it exists, then it should be expected for all of its possibilities to be useful in some context. Just, "set it here," with no more explanation than that, *might* solve the immediate problem...*might*...but it'll certainly cause others, in different contexts that need a different setting.
Your one situation is tunnel-vision. That doesn't work for the wide variety of situations that OBS is used in. And because we've seen a lot of that variety on the forum, it also doesn't help to tell us, "it doesn't work," with not much more than that. What you have may very well work perfectly for someone else's rig, and with nothing to go on, we don't know yours from theirs.
