i just tested this and was able to get it working as long as i stayed in session view. if you switch to another track and then open the keyboard view it stops recording for some reason. maybe that helps?
I’m on latest version of Live and Push (not beta). Works on controller or standalone.
I made a short video of this but my phone does not seem to want to upload it.
I set up some return effects within the drum rack chains. Then in P3S I can choose how much of each pad I send to these effects. You currently can’t create these effects chains on standalone so they have to be done in Live.
1 Like
This is exactly how it works for me
Shared a video of how it works for me on the Ableton Discord
Is the 2.1.5 regular release the same as the latest beta 2.1.5b4?
Just as a general take, a lot of the Push 3 standalone experience for me is building in Live then playing in Push. It’s not quite a blank canvas, but there’s a lot of scope to make it what you want it to be within the pretty broad parameters it provides, especially using max devices.
Mainly posting to note how powerful the MPE pads are for drum racks - this wasn’t obvious to me at the start and I kinda slept on it because a lot of what I have been doing over the past year was more so around building custom sequencing setups. But if you look at e.g. the Studio Drums MPE kits it shows one way of using it that takes a 16 pad kit way beyond what other devices can do. Gonna be exploring this a lot further in 2025.
5 Likes
Thanks, I just updated to the release version
When you switch between Macro Variations on Push 3, is there a way to quantise when they change?
(Also, is it possible to time the transition between them?? 1/4 note or 1 Bar for example?))
Has anyone used this M4L Follow Scene + Clip XL device with the Push 3SA?
Am I reading this right that this will add the ability to create songs using the session mode with automatic follow actions and dummy clips to set scene length?
You can do this using clips in Session view (ie clip 1 has macro variation 1, clip 2 has macro variation 2 etc). Switching between macros would then be quantised to whatever your clip launch quantisation grid is set to (1 bar, half, quarter-note, eighth-note etc).
I guess it should also be possible to automate macro variation switching within a clip by pressing the Automate button + Record… haven’t tried this yet. That wouldn’t be quantised though, you’d play in the changes live.
The ideal would be to automate macro variations by ‘p-locking’ a step in the Push step sequencer… but I’m not sure how this would work. I’m away from Live ATM and I can’t remember if macro variations are available as a p-lockable parameter in a rack instrument when you press and hold a step in the step sequencer.
2 Likes
Been asking since P3SA came out…
You can do this with smooth Automator Smooth Automator version 1.0 by KBDevices on maxforlive.com
That exposes the variation as an option you can set in the midi clip.
If you are on Push3SA though, you’d have to do what I did and use the live.banks option in the max device, so that you can then see it on the screen of the push. Which I guess you could then automate.
The instructions for that are here: https://youtu.be/yWA7spj26I8?si=NiJGaagCVJxaiF8B
I’ve not tried that last idea though, I don’t have Push 3SA, so I just use the mouse and add it to the midi clip automation.
1 Like
hey everyone, can any push 3 experts help me out here?
I am experiencing the strangest problem
so I wanted to build a live set around push 3 using it for drum racks as well as looped samples and stuff
the gig is friday and this is a huge bummer
so basically I made a big drum rack with a ton of samples, and made like 10 sequences with the drum rack, all on the unit
everything was fine, but then i imported the session into ableton and named all the sequences and also made controller assignments for a korg nano control i want to use with it
once i put it back on the push i encountered a bug where the pads on the drum rack become unresponsive
video here:
https://www.youtube.com/shorts/yioll4TUVK0
this is driving me up the wall because I don’t see what could have happened, i re opened the session and no tracks are frozen or flattened in any way,
and if i manually scroll to the actual drum channels on the unit and select them i can edit them, it’s only with the pads
this also occurs with the nano control unplugged
this is a major problem for me because a lot of my live set is making drum sequences on the fly and adding and removing triggers to do stuff like fills
has anyone experienced this before and if so can you lend me some guidance?
thanks!
There has been lots of bugs like this related to using different Max4live devices. Don’t know if you are using any? I also experienced a strange bug a while back where one of the drum cells was causing this issue. When I deleted the cell and loaded a new device there everything was fine.
Are you on the latest firmware. This has solved all my issues with inactive pads for me so far
i do have pitchloop89 loaded as a send effect and a few instances of drum bus and beat repeat
i am on the latest firmware
edit: i just tried deleting all send effects and pads one by one and no dice on anything, still unresponsive
I would try to delete any non native plugin to see what happens.
If you have Push in controller mode does it have the same issue? If so, is the issue solved by restarting Push while keeping the program open (and then selecting it as an audio device again). Also check what happens if you delete all the cells in the drum rack and then load a new sample into the rack.
I had this exact issue a while ago and I even started the project from scratch several times which fixed it temporarily. However it always came back until I figured out it was one of the instances loaded into the drum rack that was causing it (just a normal instance of simpler)
Edit. Just saw your edit now. What if you create a new track with a drum rack in the project? Are the pads responsive then?
if i make a new track the new track is responsive, i tested loading analog and drum rack on separate tracks and both worked
It sounds very similar to what I experienced (could be something different of course).
Does the issue also happen on the computer if you send the project back to the computer from push? It did for me. If I then would load the saved drum rack into a new track it would work fine first but after playing around a little while selecting other tracks etc I would get lots of strange behaviour including unresponsive pads.
when i open the project again on the computer everything works perfectly