Bug: Under OBS 30.0.0 CreateScene reverses the order of sequentially added scenes about obs-websocket

[tt2468]

This is behavior working as intended. Scenes are now inserted at the current row instead of the top. See commit obsproject/obs-studio@5e198db for more info. Will not close this issue yet in case anyone cares to argue whether we should try to artificially preserve the old behavior.

[david672orford]

I understand that this change was made deliberately to improve usability in the GUI. It is a good change. What I am suggesting is that this change should have been made only in the GUI and that its (presumably unintended) effect on the behavior of the CreateScene calls is a regression.

It now means when we run a script to add a series of scenes (videos and slides) during a live program they get splatted into the middle of the scene list totally disorienting the operator. And they are in reverse order! To the untrained eye it seems like everything has been scrambled.

I think the change in the behavior or CreateScene really is a regression and a serious one. I hope it can be fixed in the next point release.

[david672orford]

I have been trying to figure out how to fix this problem in the hope of submitting a merge request. However, I have been unable to fully trace the path from CreateScene to OBSBasic::AddScene(). This is what I have so far:

• OBS-Websocket's CreateScene calls
• obs_scene_create() which calls
• create_id("scene", name) which calls
• obs_source_create() which calls
• obs_source_create_internal() which calls
• source_create() where I lose the track