scenes collections getting "messed up"

[Mike666]

Sorry if that sounds a bit vague. I'm here and new to OBS, but seem to have hit something a bit weird. I don't see that I can be doing anything wrong (always possible :-{) I'm supposing a "scene collection" is intended to be independent of other scene collections.

Anyway, this is with OBS 25.0.3+dfsg1-2 (64 bit) running on Mint 20.

I started by deleting the ~/.config/obs-studio/basic and then starting OBS, to ensure a completely fresh start. OBS starts with a collection "t1" (the last active collection name - saved in global.ini) and a single scene, which I rename to "red1", then add scenes red2 and red3 (all empty). I create a new collection "t2", and rename the single scene "green1", and add green2, green3. At this point, I can switch between t1 and t2, and there are no surprises.

However, I now drag and drop the t2 "greenN" scenes to reverse the order. Switching back to t1 (correct) to t2 (correct) and to t1 again now shows red1, red2, red3, green1, green2. going to t2 reveals green3, green2, green1, green1, green2. Further switching between t1 and t2 appends more copies of green1 and green2 to both collections.

Log file attached, although it seems not very enlightening.

(Yesterday, in the context of a more complex pairs of of scene collections, I had a test set mix up with my "real" set, and even the sources within scenes had shuffled themselves around between scenes. )

Any thoughts please? Can anyone repeat this? Thanks.

 

[WizardCM]

OBS 25.0 is over a year old, so it's worth updating if you can.

There is currently a known issue that a scene collection doesn't fully unload before loading the next collection. The recommendation is to load a "blank" scene collection in between to essentially clear the memory & avoid the data getting mixed together.

When switching scene collections, the new scene collection often loads before the old one has fully unloaded, causing a variety of issues. · Issue #2715 · obsproject/obs-studio (github.com)

 

[Mike666]

OBS 25.0 is over a year old, so it's worth updating if you can.

There is currently a known issue that a scene collection doesn't fully unload before loading the next collection. The recommendation is to load a "blank" scene collection in between to essentially clear the memory & avoid the data getting mixed together.

When switching scene collections, the new scene collection often loads before the old one has fully unloaded, causing a variety of issues. · Issue #2715 · obsproject/obs-studio (github.com)

Ok; I should have checked versions. Mea culpa. In mitigation, 25 seems to be the most recent in the Mint repo.

But I've tried "hammering" v27, even without any recommended empty collection; it seems solid.

Many thanks.

(I have some queries on the python API; but will start a fresh thread when I've time to word them clearly. I assume here will be a good place?)