Hello! I'm working on implementing this feature, and would like to use this space to engage with the community.
I've been periodically updating the issue in GitHub as we refine the initial scope and desired functionality. Current progress is I've validated tuning twelve notes in an octave, and I've started focusing on building an interface to import Scala files.
Eventually we want to end up with more than twelve divisions per octave, but it is growing increasingly clear that this will be considerably more effort to implement owing to pitch, sample speed, and FM ratios all being somewhat interconnected. My goal for this feature is to get it working well enough that it can be accepted into the community branch, ideally in a way that is of high enough quality to merge into the official branch.
There are some open questions mentioned in the issue that I'll cross-post here.
How to handle Scala files with greater than 128 divisions.
* Ignore and apply partial scale?
* Reject the file and popup a warning?
* Wait until MIDI 2.0 is implemented?
QWERTY or basic menu for selecting Scala files?
* Optimize for searching through many tunings?
* Optimize for being able to play each tuning in keyboard mode while scrolling through tuning presets?
I will also be reading through the linked discussions below to get a sense of what folks want.
naming MIDI tracks would be useful, and it might be easy enough to add this feature once the source code is published
Just wanted to chime in and bump this thread since I'm having a related issue.
I'm running firmware 2.0. I can describe in detail what is happening. I have a bunch of gear connected via USB; Deluge, JUNO-DS, Moog Little Phatty, Novation Circuit; and Ableton on my Mac direct to the Deluge via MIDI 5-pin DIN.
Let's start with what happens when it's just the Deluge and the Circuit connected with either DIN or USB:
The Circuit responds on Channels 1,2,10. I want to get a groove going on the circuit and later record the data to a MIDI track on the Deluge. I make a new MIDI track for channel 1 and learn the output from the Circuit on channel 1 to that track. What then happens is a sort of horrible feedback loop where Circuit sends data on channel 1, which prompts the Deluge to send the same data back out on channel 1, which triggers the same note again on the Circuit. The Deluge would ideally handle this case a bit more intelligently and not parrot back the data when the channel out matches the learned input channel. This happens with any of the instruments mentioned above.
With Ableton I have a problem that might be better conveyed in a separate thread. To be brief, I've had the Deluge freeze randomly four times today with a stuck buzzing sound requiring me to power cycle the Deluge. It's a real bummer when that happens because any edits I made are lost.
I'm happy to go into greater detail... I'm a software engineer who did a bit of work for Moog several years back.