You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If scene names overlap between different scene collections, the scene names will be changed automatically.
This issue does not occur in safe mode, so after verifying it, it does not occur if "NDI Output settings" is turned off.
Steps to reproduce the problem
Create scene “test” in scene collection “01”
Create scene “test” in scene collection “02”
When you return to scene collection “01”, scene “test” has been changed to “test 2”.
If "NDI Output settings" is turned off, this problem will not occur.
Expected behavior
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
This is because the COLLECTION_CLEANUP event is not acted on in preview_output.cpp:
Add this case in the on_preview_scene_changed callback:
case OBS_FRONTEND_EVENT_SCENE_COLLECTION_CLEANUP:
obs_source_release(ctx->current_source);
ctx->current_source = nullptr;
break;
Because we don't release the source, the previous collection isn't cleaned up. When a new collection is selected with a duplicate scene name, it thinks there is already a scene with that name.
Operating System Version
Windows11
CPU
No response
GPU
No response
NDI Devices
No response
OBS Version
29.1.3~30.0.2
OBS Installation Method
exe
OBS-NDI Version
4.12.0~4.13.0
OBS-NDI Installation Method
exe
[Extra] Installation Steps
No response
OBS Log [URL]
No response
NDI Version
5.6.0.0
Describe the bug
If scene names overlap between different scene collections, the scene names will be changed automatically.
This issue does not occur in safe mode, so after verifying it, it does not occur if "NDI Output settings" is turned off.
Steps to reproduce the problem
If "NDI Output settings" is turned off, this problem will not occur.
Expected behavior
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: