OSC command for Panic all

[jpver...@gmail.com]

Hello,

Im running a Qlab 3 show with a couple of movies. Triggered randomly with an Ipad with touchOSC.

I would like to make a panic button on the Ipad which when I press the button it will behave like the ESCAPE button on the keyboard. 

I tried everything to make it work but till so far no succes.

Is this possible?

Thanks!

[Dave "luckydave" Memory]

On Saturday, May 24, 2014 at 11:04 AM, jpver...@gmail.com wrote:

Im running a Qlab 3 show with a couple of movies. Triggered randomly with an Ipad with touchOSC.

I would like to make a panic button on the Ipad which when I press the button it will behave like the ESCAPE button on the keyboard. 

I believe you're looking for:

/panic

-- 

luck...@figure53.com 

[Chris Ashworth]

Hi there,

Welcome to the list.  The OSC command:  

/panic 

will cause the front-most workspace to panic.  You can also panic a specific cue, if you know the cue number.

One thing to note is that I believe I remember that Touch OSC might require you to send an argument with an OSC message. I may be remembering that incorrectly, but if not, that’s a limitation of Touch OSC and would prevent you from triggering a simple address-only action in QLab.

-C

[jpver...@gmail.com]

Yes, I tried that one.

It behaves right when you hit it for the first time. But after the second time it panics in 0 seconds instead of the default panic time in the preferences. The ESCAPE button still uses the 2 seconds default time but the OSC command /panic doesnt.

I also tried: /cue/*/panic and /cue/{whatever}/panic but with no succes.

[Chris Ashworth]

Note that sending a “panic” message twice in a row causes a hard stop.

i.e. a cue that is already panicking will hard-stop if it is told to panic again.

-C

[jpver...@gmail.com]

I believe this would be right. Or do I need to set a value range as well?

[Dave "luckydave" Memory]

On Saturday, May 24, 2014 at 11:21 AM, jpver...@gmail.com wrote:

I believe this would be right. Or do I need to set a value range as well?

Looks right to me. As long as you don't send /panic while the workspace is already panicking, you shouldn't have an issue. Sending the second /panic within the panic duration will cause it to stop immediately. You'll get the same results with the Esc key.

-- 

luck...@figure53.com 

[jpver...@gmail.com]

I think its a bug then. When I change the panic time to 4 seconds. hit done and start the cue again and hit /panic on the Ipad it panics in 4 secons. The second time I start the cue and hit /panic on the Ipad it panics in 0 seconds while the default panic time still says 4 seconds. Everytime I change the default panic time it works once.

[Chris Ashworth]

I think its a bug then. When I change the panic time to 4 seconds. hit done and start the cue again and hit /panic on the Ipad it panics in 4 secons. The second time I start the cue and hit /panic on the Ipad it panics in 0 seconds while the default panic time still says 4 seconds. Everytime I change the default panic time it works once.

Hi,

On this particular area I can say with confidence that the QLab side is working correctly.  What I think we need to do is track down exactly what TouchOSC is sending, and when. I predict it will not be what you think it is sending. 

One way to check this is to set the log level to “2” by going to “QLab” —> “Preferences…”

Then open up the Console.app utility from Apple.  You will see log entries such as this:

5/24/14 2:44:11.422 PM QLab[4133]: [UDP socket 127.0.0.1:53001] sent OSC message:   /panic

If you get more than one message when you press a button, it’s wrong.  Also if you get anything other than “/panic"

-C

[jpver...@gmail.com]

This is what I receive: Its the value range that comes behind the /panic:

25-05-14 00:41:53,270 QLab[32571]: [UDP socket 192.168.50.5:53001] sent OSC message:   /panic 0

[sam kusnetz]

Hi folks

I'm fairly sure that TouchOSC sends two messages, one on press and one on release. This is why it causes problems with /panic.

Cheerio

Sam 

--

Sam Kusnetz

QLab Support Operative

(mobile)

--
--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab
 
Follow Figure 53 on Twitter: http://twitter.com/Figure53

---
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.
For more options, visit https://groups.google.com/d/optout.

[jpver...@gmail.com]

Yep, your right. I checked it. When I hold the OSC button down it panics in the right time.

How can I fix this? Is it possible? Is there also a way around?

[jpver...@gmail.com]

Got it:

Make a toggle button with local feedback off.

[Drew Schmidt]

A toggle of course means you button is toggling on/off. If you want a normal button or want to use other elements (such as volume sliders) you'll need to use python, pure data, or osculator. Osculator being the easiest. These will let you adjust the OSC message to ignore values ( which is what you need), scale, append, and much more.

Maybe I should write a blog post about these ...

[Drew Schmidt]

And Sam is correct. You're sending "/panic 1" when pressing down and "/panic 0" when releasing

[jpver...@gmail.com]

So there isnt any touchOSC button to only send one message? Like a MIDI "not on"?  (I now use a toggle to panic all)

[Dave Wallingford]

I have a related question:

I'm using 2 QLab machines, and on one of them, I've setup a group cue with two OSC cues, one to panic the local machine and one to panic the other machine. Working great so far. Can I use escape as a hotkey for this group cue? I know I can use any other key, but I'm afraid that trying to get myself to use any key other than escape for panic just ain't gonna happen…

My operator is using one of Andy's remotes, so using a MIDI trigger for the group cue works just fine, but I use panic quite a bit when jumping around while programming.

Thanks!

- Dave Wallingford

[Chris Ashworth]

Hi Dave,

I'm using 2 QLab machines, and on one of them, I've setup a group cue with two OSC cues, one to panic the local machine and one to panic the other machine. Working great so far. Can I use escape as a hotkey for this group cue? 

The escape key is reserved exclusively for the built-in panic, so as to remain constant for all systems. So that key is only ever that function.

Best,

Chris

[Tyler]

Feature request: could an option be added to transmit a panic to other stations via OSC on hitting esc? It seems a bit of a strech, but for those working with backup rigs it does come to mind what if I need to panic

[Joshua Langman]

If you're running a redundant system, ideally you would be using an external trigger which could be programmed to fire whatever group cue you use as a custom panic in lieu of QLab's default Panic action. Though actually, come to think of it, using an external trigger would eliminate the problem altogether because you could just send the default Panic action to both machines.