- Brisbane, AU
- Last Active
- Beta Tester
- Brisbane, AU
Rohan - thanks for the clarification! - But I agree it would be nice in 2.0 if this kind of continuous controllers could be linked
I guess I like the idea of what I do to one track also happens on the other if it's a clone. Maybe a differentiation between a clone and a copy of a track and if I "copy" then it make a separate copy of the synth, and if I clone it IS the same synth.
This is something I'd like to see where several tracks are attached to the one synth/drum engine. It's like the MIDI tracks where 2A, 2B etc all go to the one external synth
*disclaimer I am working on MIDI 2.0 specification within the MMA
One of the new features being worked on by the MIDI Association is a thing called Property Exchange which provides manufacturers with a set of standard SysEx messages for managing and auto configuration of their devices. Part of what is available is the ability to transfer files (8 bit over 7bit protocol)
I would recommend that the Deluge was to go down this path instead of writing custom SysEx.
I am happy to help in anyway I can to get this done.
Chair of the Property Exchange working group
This is very exciting news
It's worth noting that the MIDI Association have reformed the MPE working group to improve MPE support amongst devices as many devices have incomplete support.
Will the Deluge be supporting Pitchbend Sensitivity as required by the specification? Is the Deluge going to act as a MPE MIDI Controller as well?
I look forward to being able to do some compliance testing the Deluge when the Beta is released