Видео

EDIT: Thank you, but I realized that my code is actually correct! info~ sends out the number of channels the sound file has, so it will send out 1 if the file is mono and 2 if the file is stereo. It is easy to overlook using [+ 1] when using gate, selector, etc. in other cases, though

That's a great way to avoid all the glitchiness from moving the loop points while groove~ is active! Thanks for sharing that

I just updated the device because I forgot to use plugin~ and plugout~ so audio can pass through it! It should now work anywhere in your Live set. I actually based this concept on the native behavior of the Push and some other MIDI controllers that automatically arm tracks for recording in Live! Your Push should automatically arm the selected track for recording (www.ableton.com/en/live-manual/12/using-push-2/#navigating-in-note-mode).

Good question - I would add a flush before a note out and send a bang to it every time you change the scale or root. I believe this mimics how Ableton works when you change the scale or root note. Let me know if that makes sense/works for you.

@@sam_ssaem I track all the incoming notes and make a 128 element coll that keeps pairs of incoming/outgoing note numbers. So for every incoming note-off I check how it was remapped to shut off the correct note. The flush method is far less useful as it would cut notes in a not natural way and I believe it's not how it works in Ableton.

@@chapelierfouTV Oops, I wasn’t thinking properly! I was thinking about changing the scale during held notes, not note-ons. For held notes, Ableton does the opposite and ignores the scale change until you play the next note. This is probably the behavior we want. However, you are correct, for note-ons it does transpose the note (I automated scale changes in the Scale MIDI Effect to test this). I originally wrote and expanded the code in this video to generate and transpose notes and send them to instruments in Ableton, and it transposes note-ons correctly when automated. But if you are using it to transpose incoming notes, your approach sounds great!

@@chapelierfouTV Update! I rigged something up with borax and coll that seems to be working - it is similar to your approach. I will try to explain: I send the pitch to the quantization code only if it is a note-on (velocity > 0). I then save that quantized pitch in coll using the voice number from borax as the address. When there is a note-off, I send the voice number to coll to retrieve the pitch for the note off message. I append 0 to the pitch to make it into a note-off message, then remove that voice from coll using the second outlet, which outputs the address. I hope that makes sense. The code seems to work, but I need to test it more. Thanks for asking about this!

@@sam_ssaem Awesome, thanks for taking the time to experiment ! I'll think about your solution, but that sounds very similar albeit maybe more efficient.