-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scenes JSON clogged by the scene switcher #539
Comments
Thanks for reporting the issue! |
Ok so i did a few more testing and i noticed a few aspects of this bug:
An example: Switch to Collection B: |
I see .. thank you very much for the hint! :) https://github.com/WarmUpTill/SceneSwitcher/actions/runs/3093591727 The problem was that when settings were loaded the old splitter sizes were not discarded. |
Great! Is the fix also going to sanitize existing JSONs after updating? What may be happening is that people are experiencing terrible performances and have no idea where that's coming from. EDIT: just tested the new version and yeah the bug is gone, but what data is already present in the lists does not get cleared. I think this should be addressed. |
It should get cleared as soon you open, but more importantly close the advanced scene switcher window at least once, as this triggers the values to be written again for the active scene collection. |
Yeah i was almost editing my message adding that i found that out. That should be enough for everyone hopefully. |
Describe the bug
I had an issue where somehow the
macroActionConditionSplitterPosition
andmacroListMacroEditSplitterPosition
lists in the scenes collections JSON would get filled with a huge amount ofpos
variables (making the files several megabytes in size). This would in turn make scene collection switches extremely slow. Emptying those lists restored the usual performance.To Reproduce
Steps to reproduce the behavior:
N/A (don't know how this happened)
Expected behavior
Those lists don't get filled with infinitely repeated variables
Version information
Additional context
I use the
--multi
switch and launch multiple instances of OBS at the same time, maybe that's what caused it?The text was updated successfully, but these errors were encountered: