This page is for machines that already run OBS Studio. The short version: it is not touched, and you may not run both at once.
What the installation does to your OBS
Nothing. Not renamed, not reconfigured, not upgraded, not downgraded.
Ultimate Playout brings its own copy of the engine, in its own folder, with its own configuration. Your OBS keeps its scenes, its plugins, its settings and its own updates.
The one rule
Do not run them at the same time.
Both are built on the same engine, and two applications of that engine running together write over each other’s configuration. The setup checks for this and refuses to install while one is running, for the same reason.
In practice: close the one before starting the other. If somebody does run both, the symptom is settings that mysteriously revert — and the fix is to stop doing it, because there is no way for either program to protect against the other.
Why a separate engine at all
Three reasons, and they all come back to the same thing:
A pinned version. The program and the engine belong to one generation. Your own OBS updates when it likes; the playout’s copy must not — see the pinned engine.
Its own configuration. The playout’s outputs, scenes and settings have nothing to do with your OBS scene collections, and neither should be able to disturb the other.
Its own identity. The operator sees Ultimate Playout, not OBS — see your own name and logo.
For a control-room machine
The clean arrangement is not to have OBS on it at all. A machine that does one job on Sunday morning is easier to keep working than one that also does three other things during the week.
Where both genuinely have to be there, put a note on the desk: close the other one first. It is the only rule this program asks you to remember.