Feature Request - Disable Network Output Patches

[Brenden Friedel]

Hello!

I'd like to submit a feature that in my brief looking I didn't find. I think an option in the Network Output patch window, that looks like a checkbox to enable or disable certain OSC outputs would be great. 

The reasons for this is that if I use the OSC Overrides to disable all OSC outputs, I lose access to things like the QLab App or Streaming OSC to something like Vor. My intention is to disable  Network outputs to something like a Q338 and DS100 while leaving other OSC functional. I have gotten around this currently with a script that disables all network cues whose patch matches the ID inputed, but I feel like this should be a more native feature baked into QLab. +1 if the enables are targetable via OSC input, MIDI, or Apple Script.

B

[David Crone]

We do this by using a separate network patch for each device being controlled. Then to disable a device, edit the patch to change the port number to something invalid. For example, if it is usually port 3333, change it to 3334. 

[Sam Kusnetz]

Not to deny the feature request, but here are two ways to address it:

Option 1: use patterns for your cue numbers, then disarm cues according to patterns. For example, you could use a suffix for the cue numbers on the cues that target your Q338 and DS100 such as “x”, then use this OSC message: “/cue/*x/arm 0” which will disarm all cues whose numbers end in “x”.

Option 2: write a script which disarms all Network cues that use a specific patch. Network cues have properties called “network patch name”, “network patch number”, and “network patch ID”, so you can say something like “set the armed of each cue whose network patch name is “console” to false” (NB, that isn’t proper AppleScript, it’s just an example.)

Best

Sam

—

Sam Kusnetz (he/him) | Figure 53

s...@figure53.com

--
Contact support anytime: sup...@figure53.com
User Group Code of Conduct: https://qlab.app/code-of-conduct/
 
Instagram: https://www.instagram.com/Figure53
Bluesky: https://bsky.app/profile/qlab.app
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/qlab/67da773b-04dd-4aa4-a4b9-636988689486n%40googlegroups.com.

[Rich Walsh]

In case it’s useful, my favourite third way – dating from before all of this – is to stick all the cues relating to each piece of outboard in its own cuelist (one for each device) and use Start Cues when you want to call one. Then you can simply disarm a cuelist if you don’t want to send those cues out.

I also like doing this as you can batch generate useful cues in one place and also see them all together if you need to update something. You don’t have to remember the structure of the cues, just the numbering convention you’ve chosen to make creating the Start Cue easy (eg: 901 = recall scene 1 on a console, 723 = send command to go video cue 23, etc).

Rich