Another aspect of UDP/OSC, which I've not seen in the other discriptions, is the easy ability for broadcasting messages. Instead of sending the OSC command to a specific IP address, one can often use the networks broadcast address.
As for the Broadcast term, it describes the process of broadcasting packets to an entire subnet. (e.g: 192.168.1.001 to 192.168.1.254). As you see, the Address 192.168.1.255 here is spared out. This is the broadcast address of the used subnet. If you put this IP as the OSC recievers address, the messages will be fired to all IP Adresses e.g. devices in the network. This makes it easy to trigger multiple devices, with only one OSC message and therefore in Izzy, only one OSC send actor.
if I really understand what you want (I am not sure), your problem is coming from the toggle actor. The init entry is set to off so that by every scene enter it will be active so set the output to off. But as you use the output only as a trigger you get by scene entry a trigger. It is normal. You have to set the init input of the toggle actor to none to have no trigger on changing scene.
But further why do you use so much actors in your fist user actor to get only a trigger. You can use only the keyboard watcher to get the same result. Here an example how I would make your patch:
The stepper motor is very precise. Adding additional Counter actor and Gate actor you will be able to make very accurate rotation to a specific angle/rotation point. By counting the number of triggers delivered to the motor via the ‘Pulse Generator” actor. This particular stepper motor and half-step sequence takes 4096 triggers to complete a full rotation. With the Pulse Generator set to 300hz a full rotation takes approx 13 seconds. However, precision with the motor speed appears to be less predictable within 0.5 sec tolerance this is because the Pulse Generator is effected by the cycle rate available to the patch at any given time.
If you want to describe what you would like to do I may be able to provide assistance with modifying the patch.
@juriaan thank you for your detailed response! It's great to follow your workflow and suggestions. The theatre that I work in has an ETC EOS GIO @5 and a ETC Gadget II so I will take a look at connecting this up with Isadora in the first instance.
...for your different solutions, all of which are expanding my understanding of how to program switches and triggers in Isadora. Using the Trigger Value actor as a binary 'on/off' switch is powerful. Monty talks about this too. In the end I went for a mouse watcher with no modifier triggering a zero/off, so that i can toggle between on and off using the modifier i set for the first Mouse Watcher (img). This is good, but following the tutorial advice, I am now playing with the Stage Mouse Watcher to get something closer to the kind of 'touch = 'on' / release = off' experience.