Ableton Forum

I see that with Push 3 it is possible to change the pitch of a note when editing a MIDI clip, something that I couldn't believe was missing when I bought my Push 2. Is there any hope this functionality ever getting backported to Push 2? That alone would get me to upgrade to 12, if that's what it took.

Assuming you have Scale after Arpeggiator, I'm wondering what happens if you put Scale before Arpeggiator?

> I see, from the videos, that you can choose certain notes in a clip to transpose

You can choose them with the push, and transpose them with the push? Where do you see that?

You're describing what's called "round robin" sample playback, here's how Ableton suggests you implement it https://help.ableton.com/hc/en-us/articles/115000267664-How-to-create-Round-Robin-sample-playback Here's a screen recording that should give you an idea https://drive.google.com/file...

In the context of this software is there any DAW software word/moniker/category that translates to what I'm trying to do so I can search for that instead? Microtuning. It isn't a first class feature of Live (or most other DAWs, I don't think). To an extent, it can be accomplished with built-in Live...

(from my question in the Push discussion ) I think it would be a first class improvement if, when step sequencing on the push in a mode other than 16 velocities mode, notes could be added at the velocity the pad was tapped , instead of at velocity=100 every time. From using sequencers that support t...

I've read the manual, I know about 16 velocities mode, and I think I know the answer but I can't really believe it:

Is there any step sequencer mode, drum or melodic, that lets you add a note by tapping its place on the timeline, and will add that note to the timeline at the tapped velocity?

I have the same problem. Here is a project that will inevitably get stuck on one clip.

Ah figured it out on my end - I had been running 11 on a separate monitor and subsequently turned that monitor off. When I turned that monitor back on after restarting Live 11 for the nth time, there it was. Seems like a bug, if I run 10 on a separate monitor, quit, turn the monitor off, and restart...

Having the same problem all of a sudden on Mojave 10.14.6

I did have 10 and 11 both open by mistake before this started happening.

Does that preserve the timing of your midi events, seeing how JS runs in the low-priority thread?

Damn this is annoying.