Hm, I don’t know if re-installing the tool helped you, but from my perspectivethere might still be some problem, somewhere.
So, I would be interested to hear if you experience this problem again…
Absolutely, and I want to add a few extra conditions that should be especially useful with sysex
- WHEN on_new_document
- WHEN on_tool_initialize
- WHEN on_song_initialize [+ song name]
So you could set up the tool in a particular way whenever the tool initializes, or if you load a particular song.
And of course, sysex would not support the full spectrum of conditions & actions. Only “equal to/not equal to”, and “set” would be available.
As for MMC, strictly speaking they are also a special kind of sysex message, and I consider implementing them in a way similar to Duplex.
Basically, check if MMC before forwarding to Renoise. If true, simulate the effect by taking control of the transport.
This needs to be done because “raw” MMC messages are not picked up when sending them via the internal MIDI.
Just like any other property “when note-on and note is between C-4 and C-5” ?
Reinstalled without success, with the exception of the first time I opened after installation.
Also sometimes when “channel” “between” setup doesn’t split the third column into 2 values.
It also autostarts on my PC with autostart deselected.
I thought maybe it was MIDI Yoke running amok, but I deleted that and the value selection problem still occurs.
MMC functionality like duplex would be
Sysex would be