I’m still at the gates with touchOSC, I’m having much more luck with OSCemote and SC3 at the moment.
I can’t seem to get much more than start and stop at the moment. I had touchOSC do something with LPB but, all it did was send the LPB to 1 and nothing else.
Must have the syntax wrong as I can’t figure out why “/renoise/trigger/note_on(-1,-1,77,77)” isn’t working for me. I’m pretty sure this is a bundle, telling renoise current instrument, current track, note 77, vel 77.
This looks OK. Do you at least get some “Rejected” messages in the renoise OSC preferences?
If you get an REJECTED, the you know that at least something was received, but either the pattern did not match or the parameters did not match.
Yes, its not even Luas OSC handling, it Renoises OSC handling. It won’t really help you with SC3.
But you don’t have to send a bundle. A single message will work as well.
something like this:
“/renoise/transport/bpm(67)” will get the rejected message, I’ve tried many variations like:
Lot’s of variations of those, for bpm and lpb.
I stopped short of trying much “/renoise/trigger/midi” yet, as I’m not certain what format the bundle messages need to be. Maybe something like “Ch1|CC1”?
I just downloaded the scripting pack, it seems to me touchOSC would be much more suited with Duplex. Thinking I need to start reading the Duplex threads.
I just found out pure data sends the message bundles properly.
send /renoise/transport/lpb 8
is accepted in Renoise.
TouchOSC is a puzzle, OSCemote is also a puzzle. Both of these look to be needing a scripting interface similar to Duplex, I could imagine the other OSC apps for iphone will also need a scripting interface. haven’t tried mrmr or remokon yet.
iOSC is capable of sending bpm & lpb, but crashes with strings like start and stop. triggers is not worth trying on this.
Just looked into remokon, it will definitely need a Duplex like interface.
Hey, Moonriders. Yes, from what I understand there are dozens of little controller apps for the iThings. Each app comes with several different options and layouts, so it’s really a mountain of information.
But if you simply need some TouchOSC/OSCemote/etc fader or button to control a certain parameter in Renoise, then Duplex is overkill. This is a one-to-one mapping, which is much more easily done by modifying GlobalOscActions.lua. Use Duplex only if you really need it. If you want to ‘write something once, and run it everywhere’, then Duplex is your friend. But check out GlobalOsc/MIDIActions.lua first.
I don’t know what TouchOSC does. I never looked at it.
I imagine it’s similar to Open Sound Control (OSC) Client Library for PHP (attached)
Basically, it’s some “program” that sends “stuff” to Renoise. The “program” has it’s own way of writing code, and its up to you to research how it works.
Example OSC PHP code:
$c = new OSCClient();
$m = new OSCMessage("/renoise/evaluate", array(
'renoise.song().transport.bpm = 500'
$m = new OSCMessage("/renoise/transport/start");
$m = new OSCMessage("/renoise/transport/stop");
In the above I:
Set the song bpm to 500
Wait 5 seconds
Stop the song.
This is the PHP Osc format of sending messages. I know this because I opened the PHP OSC file and read the documentation in the file.
Notice the BPM part of the code above. I’m sending Lua here. The OSC Prefs that danoise mentions is just an easier way to do things. Instead of setting the bpm in the PHP Code (remember this is just “my program”, it’s the conceptual equivalent to TouchOSC) you do it on the side of Renoise, and make it easier on yourself by calling, say /renoise/my_bpm where my_bpm() is some lua coce you made up yourself that does what you want on the Renoise side.
You have to read more about TouchOSC, it must document how it sends messages?
Thanks Suva! I was thinking “_observable” meant something else entirely, like certain properties couldn’t be used yet or something about polling the property, which polling the property I guess is essentially what “_observable” is doing.
I’ve been trying to figure out what is wrong with my code here.
This one just seems to need a boolean in those last parentheses but I don’t know what to give it.
What I’m trying to do here is put an awesome amount of entries into the OSC prefs pane, and these seemed simple enough to get my head around. Starting with the renoise.Transport Properties in Renoise.Song.api.txt.
But, running into trouble with variable declarations and that boolean. I figured if I can start closer to home where things still make sense to me. I can start beginning to understand this stuff.