Basically we're using a MOS workflow so I'd like to have a single master scene that comes online with the first take item.
Then subsequent take items pass commands to that master scene to make it change in a predictable fashion. The actual take items would have a visibility of zero because they'd simply provide the method to acquire the data.
To do this I need some sort of global data store that I can read and write to with scripting.
I managed to achieve what I wanted by creating an external .net app but it seemed a bit ridiculous to have to implement such an app to simply pass data from one template to another.
I appreciate you can do a lot of this sort of thing with transition logic but I've found transition logic simply isn't flexible for what I want to achieve (or rather it's too much of a pig to set up every single combination possible in transition logic to guarantee you'd always get the right action)
It's the sort of thing that's quite straightforward to achieve in Viz or Caspar as you have a single scene online all the time and it changes based on incoming commands. As XPression always replaces the scene when a new Take Item is bought online (because MOS workflow) it seems to be very fiddly.
As the deadline for this project is looming I've given up trying to do fancy back to back things and simply remove each strap before replacing with the new one, it's not as pretty but it works consistently which is the most important thing.
#XPression