OSC wildcards

[Clearscreen]

The OSC standard apparently allows for wildcards, might be handy for getting/sending data?

[senso]

you're right. I'll see how I can implement it.

[Clearscreen]

very cool! thanks Senso

[Clearscreen]

Any word on this? Been playing with touchOSC again and wondering if it's possible to use wildcards to easily translate from a multitoggle object to a Usine matrix module & vice versa?

Thinking of building something similar to a flame "six-in-a-row" on an iphone/touchpad...

[senso]

Actually not easy to implement.
I'll try to add several osc manipulation functions in the script engine.

[23fx23]

some scripting OSC could be very handy indeed.
modules are cool but if wanna ask several parameters one after the other
we need to make process that count, and each message can be sent only per bloc. also maybe that would allow to make
message of n length? in liveOsc, the same tag is often used , but with different length for differents ops, actually that mean
in usine to use a module for each message, create the in/out in script, count procedures..quite long.
at typical mess in python script look like:

def clipinfoCB(self, msg):
if len (msg) = 4
track:= msg 2
clip:= msg 3
playing:= getClip(track,clip).status
name:= str (getClip(track,clip).name
self.oscServer.sendOSC("/live/clip/info", (track, clip, playing, str(clipname) )

that' seem very simple/handy for the user to deal with.
so it's possible to set on the fly the adress, the number of infos to send, wich can by the way be independently integers, float,blocks or strings, list ect.

(don't get me wrong im supper happy of the V5 osc work that have be done, it's quite huge, but just
would be awesome to be able to acces kind of same simplicity in usine script. kind of sendinternal msg
with args, but where args type could be somehow set/recognised as numbers or strings, with adjustable length.
(all of that i an ideal world )

I imagine it's quite a huge job to implement such a thing, but going in that direction in futur would be very cool.

[Clearscreen]

I have a feeling I'm just repeating what 23fx23 is saying, but It'd be nice to do things like assign repetitive addresses easily - for example, having a matrix in touchOSC talk to the matrix in Usine. The addresses are something like '/1/multitoggle1/1/1... /1/multitoggle1/1/2... etc', which means I have to set up 64 sends/receivers to do the address's 64 times for an 8x8 grid. If Usine could send/receive that address range polyphonically it'd make life easier - be even nicer if Usine could optionally resolve that address range to 64 data outlets in one OSC module and send/receive it to an array? Then I can imagine extracting and manipulatingsub arrays for different purposes etc.

This is where I've always felt OSC had an issue in that all addresses had to be manually entered - we need OSClearn like MIDIlearn I reckon. As far as I know OSCulator is the only program that currently does this, shame it's only on OSX...

[senso]

interesting.

the Osc learn is already in my TODO list.
let me time for that++++

[Clearscreen]

cheers Senso - look forward to seeing how you implement this stuff

[Clearscreen]

interesting.

the Osc learn is already in my TODO list.
let me time for that++++

Any word on OSClearn? It'd make my iPad much happier with Usine...