#61

this is what the info of the module is saying

This module can send the signal values of up to 40 inputs as parameters of an OSC message. A message is sent at the moment, when an event arrives at the first (top) input. The address pattern of the message is the label of this module and the number of parameters is equal to the number of inputs. On the connection page of the Properties you can select by OSC Target one or more computers to which this module sends its messages.

and the attached ensemble was working with monomeserial. So, I don’t think its an Reaktor problem. I am still not 100% if my settings are correct.

#62

port 12002 is the serialosc server port. you need the device port, which i describe in my post above.

#63

08%20AM 17%20AM

Thanks Tehn. Changed it. But it is still not working. Attached how i build the message.

#64

@malte check to ensure your grid’s prefix is set to /grid as i described above. you can also edit the preferences text file that has the port information and manually set the prefix to /grid (you’ll need to do a grid hotplug after this)

more generally:

i’m sorry to say that i don’t have reaktor, and seemingly neither do many others here. does NI have a reaktor forum that might have some existing/working patches?

the best i can suggest is that we can explain how the OSC protocol works, but then you’ll need to take that information and translate it into reaktor.

#65

I have Reaktor and will spend some time on this tonight. Nothing worked last time I tried, but it was prior to Reaktor 6.

1 Like
#66

@tehn thanks for your support. Adding the box prefix to the message worked. Is still not getting row, col, frame messages to work. If you have some examples how the message format changed from monome serial to serial osc it would be helpful.

#67

The message format did not change. I’m sorry I didn’t end up cracking open Reaktor last night. Just exhausted after work.

#68

ok, I will investigate.

#69

rol, col, and frame are deprecated, and have new formats.

i highly suggest you to look at this link:

https://monome.org/docs/osc

and i dug this out from many years ago for you:

https://web.archive.org/web/20110511200700/http://docs.monome.org:80/doku.php?id=app:serialosc:migrate

1 Like
#70

nice, thank you so much. that will help.

#71

Jumping on this thread. :popcorn:

#72

One thing I’m noticing is that patch always sends floats. I believe we want integers. Please forgive my Reaktor noobishness but how do I get an integer constant rather than a float constant?

Even if I make an integer constant with a core cell, I still end up with a float at OSC Send.

The good news is that Reaktor is quite happily sending and receiving multiple arguments, so that bit of conventional wisdom (that it only takes a single argument) seems to no longer be true (@kisielk).

1 Like
#73

Yes, I think I was thinking from the perspective of OSC mapping, where you can map a control to OSC like you can with MIDI, without having to go into core and edit the ensemble. Maybe not as useful for combining monome though.

1 Like
#74

Ah, I see what you mean, yes I think you are correct about how OSC Learn works. Yeah, we’re pursuing a considerably more involved path that does provide more flexibility.

But I can’t seem to figure out how to get an integer…

#75

@rbxbx was kind enough to google this for me:

um, okey dokey then.

1 Like
#76

did you get /box/grid/led/row to work?

#77

No.

I’m still getting floats, in spite of the above.

ens%202018-11-16%2021-01-58

OSC_Data_Monitor%202018-11-16%2021-02-43
OSC_Data_Monitor 2018-11-16 21-02-43.png912×764 52.9 KB

#78

@tehn is could this be a problem for serialosc?

#79

sorry the internet lied to us :frowning:

5 Likes
#80

It has a habit of doing that.

5 Likes