I’m not sure what you are aiming at…
works fine if there is a device 3.
You can’t disable the vol/pan device (device 1) but any other device can be bypassed.
Then open Renoise, go to “Tools” menu and click Scripting terminal & Editor.
Click “~Create new tool”
Edit basic properties and titles
Start goofing around with the example code that is inserted in your new created tool.
Then start to copy parts from the snippets into your own test tool.
It may look steep, but if you know where to find the information, it is not that hard.
For the GUI, you can select the Example tool GUI snippets in the tools menu to learn how the GUI objects are build. You can easily copy/paste snippets from that source into yours.
The basic learning steps for scripting is simply starting here:
Yeah, the GUI is a long way off. To be honest, I don`t really have the time or motivation needed to make this myself. I want to use renoise to make music!! I have seen you midi management console, can you help in any way with the midi side??
I would like 8 cc messages to trigger the effects to be on (value 0) and off (value 127).
I would gladly help you if i had the time, i would probably already have given you a workable snippet.
Unfortunately i’m with my head in another programming project currently and i need the concentration for a longer while.
I’m just taking breaks here and there, but not to put my mind on other programming stuff, i hope you can understand .
The X and Y axis on the joystick send midi cc messages to Renoise. Each time a button is held a different cc value is sent, making up to 16 cc changes at any one time. All the data can be recorded into track automation.
The arrow buttons on the top of the stick toggle playback, recording and looping, so you can form a track in the moment and record everything just using the joystick.
Each CC is hooked up to a hydra; which then goes to an XY pad to monitor all the data. There is also a configuration mode which sends only one cc value at a time.