Hi again and thanks for reading me.
tijnisfijn wrote: ↑Wed Feb 21, 2024 22:24
Hi, this is unfortunately not possible without a extra piece of software that can function as a bridge. Wire an arena can talk to each other through OSC, but a wire patch can't communicate to arena because they use the same OSC in and output (from Arena).
Actually, Wire can act as an OSC bridge, since I changed its OSC Input and Output ports.
I set Wire OSC Input on 7001 and Output on 7000, and kept Resolume OSC Input on 7000 and Output on 7001. (Is it good practice ? I don't know, but it works fine.)
producation wrote: ↑Thu Feb 22, 2024 02:35
I would suggest using Chataigne for those special OSC mappings / translations.
I looked into Chataigne before turning to Wire (as I read several other posts mentioning it), but it's too much of a hassle for me right now to get into it properly, since I really just need this OSC bridge thing.
What I'm looking for is not which software to use (if Wire isn't good practice, I'd turn to Isadora that I already know quite well), but how to get the "column selected" ID to be passed on to whichever software I'm using.
Here's an example taken from my Wire patch :
OSC IN > READ OSC /composition/columns/X/connect > WRITE OSC /composition/layers/Y/transition/duration (param float 0.5) > OSC OUT
As I said,
this works fine if I click with the mouse on the column header to select it.
I'd like it to work just as fine when hitting the "select next column" button, which I believe I can achieve by polling the selected column :
OSC IN > READ OSC /composition/connectnextcolumn > WRITE OSC /composition/columns/*/selected "?" > OSC OUT
as Zoltàn stated on some other topic in the forum, "This will return an int 1 for the column which is selected and int 0 for all the others." So I was thinking of adding some IF LOGIC like
OSC IN > IF READ OSC /composition/columns/X/connect = TRUE > WRITE OSC /composition/layers/Y/transition/duration (param float 0.5)
... ?