I3ordo
Member
i wish: there was another bracket, like Scenes\Sets\Sources "Sets" are like groups that can contain groups but they don't fill up the scenes section like they do here:
but instead like this:
Scene collections are good for having multiple versions but audio settings / adjustments dont auto update on each other which is quite normal. as the scenes always get improved the more they are used; keeping track of changes on another scene collection is not possible for me anyway.
I always ended up using one Master collection that has multiple logos, BGs , themes so , placements and a single "click" gets change whole scene collection so i went with this as it was i guess meant to be used like this:
But it results in a cluttered "scenes" tab which is filled with scenes which are not actually scenes.
so a "Sets" bracket although not actually any different than a "scene" (code wise) would do a quick solution about it, i assume(edited)
I would just drag not actual "scenes" from the "Scenes" bracket to the "Sets" bracket , so no major overhaul to the OBS's sturcture is needed imo
Scene collections are good for having multiple versions but audio settings / adjustments dont auto update on each other which is quite normal. as the scenes always get improved the more they are used; keeping track of changes on another scene collection is not possible for me anyway.
I always ended up using one Master collection that has multiple logos, BGs , themes so , placements and a single "click" gets change whole scene collection so i went with this as it was i guess meant to be used like this:
But it results in a cluttered "scenes" tab which is filled with scenes which are not actually scenes.
so a "Sets" bracket although not actually any different than a "scene" (code wise) would do a quick solution about it, i assume(edited)
I would just drag not actual "scenes" from the "Scenes" bracket to the "Sets" bracket , so no major overhaul to the OBS's sturcture is needed imo