Maybe I should spin out the BP questions into a separate thread then?
Multi-band and gating sounds freakin' amazing.
Yep, those are the ones, and that's basically what I'm doing in M4L..
[live.thisdevice] into a thing that gets the track number, then sends that into the
[monomecontrol] subpatch. I'm not 100% sure, but I think the
[send ---whatever] style only applies a device-specific prefix when the object is inside of a M4L device, so it may be completely irrelevant inside of Max alone (though it would be pretty sensible if it behaved like
#0 when inside of Max alone)
I ran into some pretty huge bottlenecks once I got things working inside of Ableton, but I'm not sure if it's something that should be blamed on my computer, or if it's something that could be fixed by optimization. The main symptom was that, when stopping recording of a loop (say, the third or fourth loop), Ableton choked up enough that it automatically disabled record-arm on some of my tracks, which makes using it pretty unreasonable. The whole point from my perspective was to be able to record the inputs as well as each individual loop separately, and to control sends, pan, and volume for each loop, and Ableton's auto-disabling runs pretty contrary to that.
Just today I heard a similar sort of hiccup when stopping recording in Max, which was unfortunate, but not fatal, since Ableton wasn't there to break things by trying to help.
I suspect the issue is a combination of a) my computer (11" MacBook Air.. not exactly the fastest horse in the race), and b) whatever
[descriptiors~] is doing when recording finishes. If the patch is open source, maybe it's possible to adapt it so that it doesn't do all of its processing in a single audio callback? (Though that sounds like a bit of a nightmare of a state machine to try to implement)
I'll have a look at the real-time version now as well..
The other thing that I haven't figured out yet is how to handle the
combine sections and the input mute, since those will all have to be sent from the loop channels to the input handler (which is new). I'm also not personally using the
combine feature really ever, so my motivation to do that is unfortunately low.
Unrelated to all of these things, I'm also now thinking about using multiple channels in
karma~ combined with some overdubbing / resampling to get a sort of "disintegration loops" effect as a loop continues, but in a way that preserves the original audio as well. Combined with divided effects, this could be particularly interesting