Thanks for the reply. I must be doing something wrong. I will try again in the morning.
1 Like
Are you talking about an external keyboard or the push’s own “keyboard”?
Me trying to do exactly what you described with external midi keyboard and not being able to is why I posted here in first place lol
Are you sure this is possible I can’t get it to work?
I am pretty sure you can change which chain is in focus to reveal that chain’s instrument parameters.
Using the example you gave of Drift on one chain and Wavetable on a second chain. If you press and hold down the button for the whole instrument rack - the lower portion of the screen will display the names of it’s chains, in this case Drift and then Wavetable. Switch the chain focus of the rack by selecting one of the lower buttons, say Wavetable. Then when you release the instrument rack button Wavetable will be a device option. Hit that and it’s parameters should be accessible.
I’m not at the Push right now but pretty sure I have done this many times
Unfortunate tho’ that the focus doesn’t seem to change automatically via a macro knob assigned to chain select. 
I just tried as well. Does not work from a midi keyboard. I don’t think it is possible, currently. Is there a feature request area that ableton developers look at? This would be a great feature to add.
1 Like
Same, I’m about as certain as I can be without double checking this is correct.
Not sure do the new performance devices work in standalone - I’ve been doing Jamuary as a kind of hunger games between pretty much everything in my studio except the Push 3 to see what I can get rid of, so I haven’t really used it in a few weeks.
But previously I was using this device to switch chains which has the added bonus of automatically switching off all devices in unused chains, worked pretty well most of the time for me, although sometimes required going in manually at the start to make sure the right chain was switched on.
There’s a new stable release but no new beta release for Standalone, right? Assuming it’s probably mainly stuff from the most recent beta finally making it to the stable release…
I don’t see an option to update the beta to the official release on the standalone. Should there be? My Ableton DAW has the latest official update.
Using my external controller, I want to map to various sound parameters. The only way I can see to do this is on the computer, then transfer to the Push 3, which is my first question.
On my computer’s Live, I click the MIDI button, click filter cutoff (or whatever), and play my controller, but nothing gets mapped. Nothing registers in the MIDI Mappings window. My controller plays the sound just fine, but I can’t get any MIDI to map. Key mapping works as expected, just not MIDI.
I’ve read through the Live manual (chapter 29) and I’ve done Live’s tutorial. I’ve tried a couple of different controllers. I figure I’m missing something beginnerish. Can someone advise.?
Awesome! Thank for this, really! I can really live with it not being automatic - would be great if it could, though :). This just opens chains for me. But I can understand that if you make a lot of chains it can be confusing and clumsy to navigate through say, 40 chains.
For now I am thinking of having a chain with my most used instruments with a set of the most tweakable parameters - cutoff , amp attack, amp release, etc - mapped to macros. Finally I can assign those macros to my midi controller of choice and have that instrument racks saved on my default template. All of this would be unnecessary if we had the possibilty to assign parameters to midi controllers, when in standalone 
. On the other hand I think that this can help to keep your push template organized and focused. A bit like the limitations imposed by syntakts machines, but now with the possibility of pressing a button (or two) and having full access to the full instrument. Again, Thanx for this 
I think you might need to select “remote” on your midi in settings for that controller
2 Likes
I just tried that, but I get the same behavior.
Is “track” selected also?
1 Like
Yes, track was selected. Following your pattern, I just tried “Sync,” and it worked! That doesn’t exactly make sense to me, so then I un-selected “Sync,” and it still worked. Then I un-selected “Remote,” and it stopped working. Toggling “Remote” back on made it work again. Judging from your first suggestion, I suppose “Remote” is the normal toggling behavior in this context? The mystery is why toggling “Sync” made “Remote” start taking effect. I’ll put that in my note in any case.
Am I correct that there’s no way to do this directly on Push 3?
I think if you want to switch streams, then you have to download the one your want to switch to and then making sure your computer and push are on the same network, you can then go to http://push.local/update.
You must download the latest official *.swu file(v.10.3.20) at Centercode and install it to your Push with http://push.local/update like already @cuberoo mentioned
No, that’s not possible from a external midi keyboard
2 Likes
Has anyone tried OktoPUSH by ISOTONIK STUDIOS?
https://twitter.com/IsotonikStudios/status/1745506279961903436
Having a bit of a strange issue with Push 3 Stand Alone.
I am using an instrument rack to host a bunch of drum racks.
I am using the chain selector to choose the drum rack I want and turn on/off drum racks so that only the selected drum rack is playing.
I select the the drum rack I want by holding the button for the main container so that I get access to the macros for the correct drum rack.
I play on the pads and the correct sounds are being played back.
The problem: Everything is working as expected except for when I hold the mute button and press a pad to mute a sound.
If I do it with the first drum rack in the chain it works as expected. eg. pressing mute and kick drum pad stops the sound of the kick.
However, with all other racks in the chain the sound just keeps playing after I mute the pad. Even though I have selected the correct rack to be in focus and it is showing the correct parameters etc.
I could have swore that this was working as I would expect it to in the past. I was on the latest Beta when I discovered the issue and have now switched to latest stable release. Both have same issue.
I am wondering if someone can please check if they have the same behavior or if there is something I could be doing wrong:)
Thanks. From what i can see it says the lateest release is 1.2 and that came out last month. Is that correct?
Read my post from 9 hours ago…1.4 is the latest release for the Push 3. Came out last week.
2 Likes