Touch OSC + Raspi & OLA + ArtNet

[FLauer]

Hey, I have some issues with the OSC plugin.

I installed the Binary Package Image on my Raspi and Run this:

sudo apt-get update
sudo apt-get upgrade

Now I made an New universe and add OCS and Artnet.

Now my Problem is that i run TouchOSC on my iphone connect to the IP from the Raspi and Port 7770 but how could I configure which Button/Slider changes which channel?

Sorry for my bad english ... but i hope somebody helps me...

[Simon Newton]

The problem is TouchOSC is sending single-item float data. OLA expects
blob data (an array of bytes) so the two aren't compatible right now.

https://code.google.com/p/open-lighting/issues/detail?id=241 has some
patches which make OLA work with TouchOSC. I need to look over them
again.

Simon

On Sat, Aug 3, 2013 at 5:16 PM, FLauer <free...@gmail.com> wrote:
> Hey, I have some issues with the OSC plugin.
>
> I installed the Binary Package Image on my Raspi and Run this:
>
> sudo apt-get update
> sudo apt-get upgrade
>
>
> Now I made an New universe and add OCS and Artnet.
>
>
>
>
>
>
>
>
>
>
>
>
>

> Now my Problem is that i run TouchOSC on my iphone connect to the IP from
> the Raspi and Port 7770 but how could I configure which Button/Slider
> changes which channel?
>
>
> Sorry for my bad english ... but i hope somebody helps me...
>

> --
> The Open Lighting Group: open-l...@googlegroups.com, #openlighting
> (irc.freenode.org)
> To unsubscribe from this group, send email to
> open-lightin...@googlegroups.com
> For more options, visit https://groups.google.com/groups/opt_out?hl=en
>
>

[FLauer]

Okay
Thank you very much!

But how can I install the patch to my Raspberry?

[FLauer]

  I can't find the plugin folder on the Raspberry

[Simon Newton]

There are new changes in the repo that should work with TouchOSC.
You'll need to follow the instructions for using the Raspberry Pi git
image.

Simon

[FLauer]

OK I have updated my Raspi.

What should I edit in the ola-osc.conf and how can i connect for example an slider to channal 1?
I have the TouchOSC editor where i can name the sliders and bottons but how i have to name them to work with channel one or 2 ... ?
Sorry for my many questions and the bad english...

[Peter Newman]

Hi FLauer,

Here's a snippet from my ola-osc.conf, I used it with a demo TouchOSC layout, which had a multifader with address /4/multifader1, so it sent floats as /4/multifader1/1 f 0.50 etc. When you move the fader, OLA displays it on the web DMX monitor of the universe the input port is patched to, and when you move the web DMX console fader of the output port, the TouchOSC fader moves. If you want to use individual faders, naming them in an equivalent way should work too.

enabled = true
input_ports = 1
output_ports = 1
port_0_address = /4/multifader1
port_0_output_format = individual_float
port_0_targets = 192.168.0.1:7770/4/multifader1
udp_listen_port = 7770

Obviously set the target IP and port to match the address and port TouchOSC is listening on, and tell TouchOSC to send to the machine running OLA, on the udp_listen_port.

PN

[Da Duke]

Hi FLauer,
as Simon said, you have to convert and route messages from touchOSC to OLA.
you have 2 solutions:
1. you can patch OLA to deal with touch OSC input
2. you can use a routing software in the middle that takes touchOSC input and route it to OLA

Let's look at the 2 solutions: solution 1 is straight forward but do not work if you do not have a 1 to 1 mapping between your control widgets and OLA input, so it can be quite limiting.
I had this problem because I wanted to control a RGB LED strip with 3 sliders: one as a colorwheel, one to control brightness and the last one for "gamma".
Here any of those sliders is impacting 3 DMX channels on ola, no 1 to 1 mapping and those are not even linear... Therefore solution 1 is dead from start, and I could not deal with 1 slider per color (now I can because of what is following...).

So I decided to use solution 2, to implement it, I use puredata which takes OSC from kontrol (I do not remember why I chose kontrol as a phone/tablet graphical interface but it is the same for touchOSC) as input and send OSC to OLA.

There are 3 independent steps in my pure data scheme:
a) transform input message into integers, depending on the graphical client format and send those 3 integer values to...
b) the mathematical transformations that create my 3 RGB values on 8 bits, then send those 3 RGB values to...
c) the transformation for output to OLA as a well formed OLA OSC message

You can run puredata on the raspberrypi or another computer.

It is very flexible because you can easily add a new client with a different format and use the same mathematical functions and output, you can also change the DMX communication format to anything...

This gives a lot more flexibility, additionally, you can skip DMX value that are known to be problematic for your hardware: let say that you have some high power leds that are noisy for some DMX channel values, you can skip those values...

Cheers,
    Daduke

[Simon Newton]

On Thu, Aug 22, 2013 at 1:16 AM, Da Duke <julien...@gmail.com> wrote:

Hi FLauer,
as Simon said, you have to convert and route messages from touchOSC to OLA.
you have 2 solutions:
1. you can patch OLA to deal with touch OSC input

The changes are in the mainline git repo - you shouldn't need to apply any patches at this point.

 

--