exeldro
Added new feature for having different transition table sets
- When using the new version for the first time, the previous transition table will be saved as "Initial Set". Later on this name can be changed.
- The current set can be chosen by changing the drop down list in the transition table window or by pushing the defined hotkey.
- A default set can be saved that is taken when OBS is opened. When this is not wanted, ignore default can be used to open the last used set instead.
- Currently only the German and English locals are changed, thus the others have to be updated.
We have a conference room where different formats of events (lectures, exercises, presentations ...) take place. Depending on the personal experience of the operator or the host and the type of event a different set of transitions yields the best user experience. The proposed implementation allows for an easy switch between those sets without the need for any changes in the OBS / transition table configuration. For sure it is possible to import the currently desired set prior to the event but selecting it with a hotkey or via a StreamDeck is much more convinient. Furthermore does this feature enable the use of a different transition between two scenes during one event. For example a stinger transition is used to for a certain scence change, but a specific event requieres this scene change very frequently and hence the stinger is not appropiate every time. In this case the first transition can be animated with the stinger, when the transition set is changed to a different set with a transition more appropiate for frequent use.
Is using different scene collections for different formats of events not an option? The stream deck has option to switch scene collections with a button. When different transitions are needed at different times I would not set a transition in the transition table, but set the transition in the transition dock of OBS, which can also be done with a button or multi action button on the stream deck.
Can you fix the unused parameter errors from the mac build?
I will fix all unused parameter errors.
From my point of view it is unnecessarily complex to maintain several scene collections with nearly identical scenes. Using the dock instead of the table works fine only in case that there is only transition to replace. If there is more than one and the replacement differs then reconfiguring the dock between transitions becomes a requieremt, adding complexity and possible errors.
I have corrected the build errors for macOS and Linux. Are the tests running automatically or how can I start them?
Is there anything else I can do now? To me it looks like that all checks have passed now.
I would like to incorporate the web socket functionality into my feature branch. However, it looks like the CMakeLists.txt has not been updated to the new OBS build system. Can @exeldro do that?