OSC Noob

[Arvol]

I finally got a spare day or two that I can dig into the OSC aspect of the app.
So far I've got the droid app and editor from hexler.net (TouchOSC). Is this the same app that everyone else is using?

The programming seems pretty straight forward.
Just add a button or fader, Select the option you want to control in Resolume and copy and paste it into the editor app, then hit sync.

I created a simple Piano button to control a Strobe fx as well as a fader for the strobe speed, and a LED to show the BPM speed.

1 (maybe 2 part) question:
The LED only shows values via intensity and I was hoping for more a a blinking value (similar to the BPM clock in Resolume), Has anyone been able to make a blinking button in the editor?
Is there more options, or advanced options in some sort of coding for OSC or is the buttons,faders,etc. I add in the app, all I can do with OSC? it seems like everything I need is there, just curious to see how deep this rabbit hole really goes? (custom button colors or blinking colors, coding to convert values to a bpm flash, etc. etc.)

If anyone has a video guide they could point me to, that would be extremely helpful as well, But if this is the same app everyone else is using, and the options in front of me is all I can use, then it looks like i'm set.

Thanks guys!

[pfelberg]

Hi there, Dinga.
I am using the very same one along with my Samsung Android Tablet.
I did several tests and already ran my layouts during a couple of real GiGs. Never used the "led" before so I can´t give you any feedback on this. But...
I don´t know about the iPad, but I get some glitches, most visual, on the Androind side. I don´t know if this are related to the OSC app itelf or the O.S.
There are a couple of threads on this on the forums. You should take a look at them.

I ended up creating a local network and used a RJ45 adapter to connect my tablet using an ethernet connection, which is much better and faster than a wi-fi connection.

[Arvol]

Thanks pfelberg.
I'm currently using an Adhoc from my laptop to my phone for testing. No clue how reliable that will be when 60,000-80,000 people are around me at a festival killing the 2.4Ghz bandwidth. Hardwired sounds like the sure bet.

In regards to the app, is that the same one most people are using?
Is there any advanced editing on the programming side of it, or is the options you see, the options you get?

Thanks for the help

[Joris]

TouchOSC is pretty straightforward. What you see is what you get.

If you like to add some logic, you can take a look at the Lemur app.

After that, if you want to get really nerdy, you could make your own interface in Processing. Using OSC in Processing and deploying to mobile can seem like a bit of a step, but it's surprisingly easy and well documented.

[Oaktown]

No clue how reliable that will be when 60,000-80,000 people are around me at a festival killing the 2.4Ghz bandwidth. Hardwired sounds like the sure bet.

Simple show equation, wireless BAD, wired GOOD

I've done my share of wireless networks for show control and there is almost always something that goes wrong. It usually all works perfectly while you're in tech but as soon as you get the audience in, it usually all becomes problematic.

I would run thousands of feet of copper CAT6 cable with Ethercon connector/coupler to avoid using wireless. If you must use wireless, I would recommend using either a mesh network with lots of repeaters or a high power access point such as the ones from Amped Wireless

I only use iPad Pro these days and Redpark makes a [urlhttp://redpark.com/lightning-ethernet-plus-power-adapter-cable-l4-netp/]Lightning Ethernet+Power Adapter[/url] which works great if the app you're using can access that network stack. I use that with Luminair to control Arena and it's been super reliable. If TouchOSC or Lemur can't access the network stack you might be able to create your own using their RedSocket SDK.

As far as OSC, I used to built controllers in both TouchOSC and Lemur but lately, I've mostly been using Qlab, Vezer and most recently OSC Linear Controller(Ravensc's controller) but these might not work for your workflow. As a note, Qlab 4 just added the ability to control OSC fades with single & double parameters and cue carts which are grids of cue triggers.

[Arvol]

Thank you guys for the replies.
I'm going to dig a bit deeper into all of this today.
I'm primarily going to have an iPad setup behind FOH for audience control. We have themed stages, so having certain small elements of the stage controlled by the audience give a bit more feedback and interaction with the setup. Running cable to unlabeled MIDI controllers didn't workout so well, so having a labeled OSC controller makes sense.

We do this with our lasers from time to time as well. Really fun elements we can safely allow people to play with (in which we can disable at anytime if they get too annoying lol)