exeldro
Endless video file creation and encoder initialisation
When using nested scenes in OBS Studio with studio mode, each transition creates a new video file as well as a new encoder instance, ultimately creating GPU/CPU and disk bottlenecks after a certain amount of transitions.
This issue seems to only appear in studio mode while transitioning using following scene setup in my case e.g. i have 2 scenes utilizing the source record filter, one for game and another for overlay capture, those scenes are nested within a "master" scene rendering my livestream. Within the game and overlay scene i have several scenes like "Starting Soon Scene", "Stream Ending Scene" etc., based on what i want to display i hide or show those nested scenes.
As soon i want to show a new scene and do a transition with studio mode, the plugin creates a new encoder instance and accordingly video file for the nested scene even though only the parent scene inherits the filter.
This behaviour is fully reproducable and can be stacked infinitely as long you have enough nested scenes within your parent scene utilizing the filter. While not using studio mode, this issue does not pop up and i can show/hide as many scenes without any drawbacks.
It would be great If you could adress this issue as i have been really enjoying the plugin and i would like to prepare scenes before showing them on stream, which is impossible resource wise with the current state of implementation. If you require more information or sccreenshots i would love supplying those to you!
Kind regards, Arkt1c0.
Work around is setting studio mode to not duplicate.
I will look into preventing duplicated private sources to create a new recording.
Can you verify if this test build fixes it for you? https://github.com/exeldro/obs-source-record/actions/runs/12711314004
I really tried to push it with test iterations, but the fix seems to work perfectly! No new files or unplanned files created neither are additional encoder instances started. Furthermore i can't register any additonal or unusual CPU/GPU usage, thank you very much for the quivk response and fix, much appreciated! I guess you can close the issue already :)