OSC apps for osx

[Ron Peer]

Hi all,

did any of you ever bumped into a software for osx that do exactly what TouchOSC does, and as mentioned, works on mac osx?

Ron.

[Lucas Krech]

I'm confused. Touch OSC is for controlling programs in OSX. What are you trying to achieve?

The whole point of a MIDI/OSC controller to me is that it is external to the main computer. There are a million ways to control MIDI and OSC on a computer. Touch OSC creates the ability to control those programs from a user definable UI external controller. 

-L

*insert witty mobile device advertising here*

--
--
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.

[Drew Schmidt]

TouchOSC is for mobile devices (iOS and Android). It's corresponding *editor* is on OSX, but not TouchOSC itself.

I often use QLab as a QLab remote. This is especially helpful in rehearsal with rehearsal cues. We'll put the show on the show computer, and craft a shortened show comprised of the 10 OSC cues needed on the stagemanager's laptop. I'll also place a panic cue and a few other function cues here.

If I want more control than that? I'll use the screen sharing that is built right into the system. 

What is your specific need?

[Lucas Krech]

> On Oct 29, 2014, at 2:08 PM, Drew Schmidt <drew.s...@nwciowa.edu> wrote:
>
> TouchOSC is for mobile devices (iOS and Android). It's corresponding *editor* is on OSX, but not TouchOSC itself.

Right. But it is for controlling OSX programs not iOS. My point was that touch OSC may achieve the system design goals.

[Ron Peer]

First of all, thank you all for your input.
As David said, TouchOsc is an iOS app wich runs on an iPad usually. Means, wireless connection, small screen and not very pro look and feel to operate for long demanding shows.
I'm looking for a way to control qlab from a OS X machine just the way TouchOsc does from an iPad.
I've tried qbee but UI is *still* quite poor comparing to TouchOsc capabilities. A bigger screen and LAN connection is much more important than touch screen in that case.
best, Ron.

[Ron Peer]

And by saying David, I of course mean Drew :-).

[Lucas Krech]

Well if you do not like the look of TouchOSC and that is important to you it won't work. I find it very clean and intuitive and sure looks nicer than my Korg. ;)

If you have a dedicated wifi it is quite reliable and I know many people who trust it for pro level shows. Mostly musicians controlling Live. Obviously YMMV.

If you want this on a computer why not just use QLab directly? I'm missing the reason a simple screen sharing solution wouldn't work.

-L

*insert witty mobile device advertising here*

[Ron Peer]

I think you misunderstood. I like the TouchOsc ui so much. I just need 10 to 12 really big buttons to trigger cues. It's not a 'cue to cue' show and trying to pick up the correct cue with your mouse usually ends up with one big operator headache and wrong cues on air. As said before, I would like to work on OS X machine and not a iPad.

[Lucas Krech]

Why not just use 1-0 as hot keys to trigger cues?

-L

*insert witty mobile device advertising here*

> On Nov 2, 2014, at 1:57 AM, Ron Peer <ro...@hakolsound.co.il> wrote:
>
> I think you misunderstood. I like the TouchOsc ui so much. I just need 10 to 12 really big buttons to trigger cues. It's not a 'cue to cue' show and trying to pick up the correct cue with your mouse usually ends up with one big operator headache and wrong cues on air. As said before, I would like to work on OS X machine and not a iPad.
>

[Lucas Krech]

Also Touch OSC allows pages so if size really is such a concern you can put five big buttons (or rotary dials or sliders) per page and have the operator page through them.

-L

*insert witty mobile device advertising here*

> On Nov 2, 2014, at 1:57 AM, Ron Peer <ro...@hakolsound.co.il> wrote:
>
> I think you misunderstood. I like the TouchOsc ui so much. I just need 10 to 12 really big buttons to trigger cues. It's not a 'cue to cue' show and trying to pick up the correct cue with your mouse usually ends up with one big operator headache and wrong cues on air. As said before, I would like to work on OS X machine and not a iPad.
>

[Drew Schmidt]

If you just need sound effects, you could look at QCart.
Perhaps the good folks at Figure53 could add an OSC cue to the app. I would use it for rehearsals and improve shows

[mackerr]

And routable outputs like QLab!

Mac

[Sam Kusnetz]

Hello folks

I’ve been mulling over this since the topic started, but haven’t had time to build anything. Until today!

http://notquite.net/qbutton

That’s a link to download my new and very lightweight app called QButton. It’s basically what the OP requested: ten largish buttons which send OSC triggers to QLab running on the same Mac.

Each button sends “/cue/Bx/start” where “x” is 1 through 10, one for each button. So button #1 sends /cue/B1/start and so forth.

You can set the name, text color, and background color of each button by sending OSC messages from QLab to localhost port 12121. Examples:

/qbutton/1 text “some text”

…sets the name of button 1 to “some text”. You need to type in the quotes in order to use multiple words.

/qbutton/3 bgcolor .5 .5 .5 1

…sets the background color of button 3 to 50% grey. The last digit is opacity, so 1 is opaque and 0 is transparent.

/qbutton/9 textcolor 0 1 0 1

…sets the text folor of button 9 to primary green.

There’s also an example workspace attached with three group cues full of resets to set the parameters back to defaults.

Right now the app won’t store its state, so you need to put setup cues in your workspace to run every time you need it. I kind of like it that way, personally, since that means all the smarts live inside the workspace and the app stays “dumb”, but I could be persuaded to include state saving if someone made a really good argument.

Any thoughts are welcome.

I should say, too: this is not an official product of Figure 53, this is a fun little thing I made in response to this conversation. If it’s useful to anyone, then that’s terrific, and i’m happy to answer questions and talk about it, but it’s probably not a good idea to go assuming that it’s going to be all officially supported or anything like that.

Cheerio

Sam

--
Sam Kusnetz
Figure 53 Field Operative
s...@figure53.com

[Sam Kusnetz]

Update already!

I re-read the OP and saw that the request was for ten to twelve buttons, so I made it twelve.

[Ron Peer]

Oh My God!

thats exactly what i was looking for!

how can i donate the developer?????

בתאריך יום שני, 3 בנובמבר 2014 08:15:44 UTC+2, מאת sam kusnetz:

[Drew Schmidt]

Mad skillz!

[Sam Kusnetz]

> On Nov 3, 2014, at 1:45 AM, Ron Peer <ro...@hakolsound.co.il> wrote:
>
> Oh My God!
> thats exactly what i was looking for!
> how can i donate the developer?????

I’m so glad it’s working for you!

No donation is necessary. I would enjoy a photograph of the software in action, though, if you have a minute to take one and send it.

[Sam Kusnetz]

Hello folks

Upon further reflection, in order to make it clearer that this is not an official Figure 53 product, I’ve renamed it OSCpanel (since it’s a panel of buttons that uses OSC) and kept away from the “Q” language.

An updated app (also with one small bug fix) and example workspace can be downloaded here:

http://notquite.net/oscpanel