I do have a solution to this planned, and it will basically allow you to use it the same way as Bidule and the like.Hmm... that is a curious way to go about it.
I would much prefer that the plugins would instantiate directly in the graph as modules in the manner of Element or Bidule.
You can set in the properties for a mixer object whether it will take MIDI input from the main track input, or from the preceeding node. I know I need to make this clearer as it isn't obvious from a glance where the MIDI is coming from, but I do have plans in the regard.Sending MIDI to a track seems to have an issue: it sends a thru message through the entire signal path.
MIDI Learn stays on until until you turn it off again, which I believe is generally the standard way this is done in apps; otherwise, it's a bit of a hassle if you're mapping lots of things at once to have to continually enable it. I tend to use the shortcut CMD+M or CTRL+M (depending on your platform) to turn MIDI learn on and off.MIDI learn seems to get stuck if I try it. It highlights everything in purple, then won't let me edit/use anything in the program after that.
There are several sequencers rows that control note length, such as speed, multiply, and divide. The dropdown box initially showing "Velocity" has these other rows behind it. I think adding shortcuts - as you say, such as CTRL, ALT, or SHIFT - to access the length directly would be a handle addition.How do I edit note lengths in the sequencer? I tried clicking everywhere on the note, then every combination of control-click, alt-click, shift-click etc.
