I am, for the moment, hard to get. That’s rare in this economy, and I feel very fortunate that I’m still able to turn down work.
I do try to make time to help friends, however. If you fall in that category, you know how to reach me.
For everyone else… I’ll hear you out, but I promise nothing.
Evening my friend,
I watched Josh Spoons 30 days of Ableton Live a while back and have since been trying to get a version of your PushCCs. I am willing to pay a fee if you can get it to work in Ableton Live. I have a cracked version. Not sure if this matters, but it is a later version. Please just let me know. Like I said, I am willing to pay you.
Peace
I believe it works right now on Push, but not at all on Push 2. But there were some problems with it playing nice alongside other apps, I think, and my general feeling at this point is that the app is more trouble than it’s worth.
Hi! My name is Andrew, i am passionate for electronic music for several years now. I am a musician since I am 12 years old, tho, so it’s been 10 years now living with music in my heart. I was a guitarist but I got into electronic music — now I want to really use Push to a full potential to improvise on it as I did previously on guitar. What I wanted to do is to create a midi device which basically quantizes notes in real time but with one addition — so I be able to add my own “grooves” for it to quantize it to. I am writing to you to ask you whether I can use your patch “Real-Time Midi Quantize 2.2” as a starting point of my work. And also if you can provide some tips on how you’d do it It would be superappreciated! Anyway, cheers, and all the best, m8
Sorry for replying nearly eight months late. This site isn’t great about sending me comment notifications.
Anyway, I did make a version which takes its timing from MIDI clips (as dragged in from Ableton’s groove pool) but you have to jump through some weird hoops to actually play through it, and the learning curve wasn’t going to be fun for users. Also, this version felt like the timing was a little off, and I was never satisfied with the mechanisms I built to offset that. So, for a variety of reasons, I never published it.
How I would do it (how I actually did it) is a bit crazy. I basically had to turn monitoring ON for that track (so MIDI comes in from your keyboard instead of the midi clips), then start a clip playing. The device would then detect which clip was active, and copy its contents and parameters into a custom player inside of max, which the quantizer would then use for timing.
(I am planning revisit the idea when Ableton removes some of those filters, but probably not until then. When we can react to multi-channel MIDI, or route MIDI between tracks without losing sight of where it came from, this will be fairly simple to build, and less arduous to use and teach.)
That said, if you have a better approach, go for it.
That patch was mostly written by John Brian Kirby (aka Nonagon), so make sure to credit him.