OK, just finished v0.61
IMPORTANT: If you have created rules of your own, take a backup of the /rulesets folder. The new install will overwrite the existing ones!
(you can find the folder from Tools > Tool Browser > rightclick and ‘reveal’ )
This is only the second release, so I’ve fixed a number of the reported issues. Probably introduced some new ones too
But really, the big news is that now it can both send and receive OSC and MIDI.
Before, it was limited to receiving MIDI and passing that into Renoise - now, you can do quite a bit more. This also means that the user interface has been re-organized a little bit to more room for new stuff.
If you want to work with OSC data, the pattern syntax is quite simple:
-- interpret incoming pattern with two integer values /some/pattern %i %i -- of course, you can also specify a literal value -- (these two are interpreted as integer and float, respectively) /some/pattern 42 3.145 -- you can assign names like this (will show up in the UI) /some/pattern %i:foo %i:bar -- all supported value types: -- %i int32 -- %f float32 -- %n "number" (can be both integer or float) -- %s string -- define an output pattern like this /another/pattern $1 $2 -- the "tokens" determine the order of incoming values -- so, in order to flip the "foo" and "bar" around you would do this /another/pattern $2 $1 -- note also that if no output pattern is defined, the output is -- based on the input pattern
Btw: I just realized that I have not yet implemented OSC prefixes on a device level. So if you need to use prefixes, simply apply them to the patterns themselves.
When I write rules for the button grid. I can get it to produce sound. But I’m not able to MIDI map the buttons to effects.
This should be now be possible. To pass messages to Renoise without the extra routing information, select “internal_raw” as the target.