Thank you! Even a video demonstration it
Imagine that such a ‘tiny’ feature can mean the world to some.
I need to resist the urge to post your video in the MPC thread and ask if the Live 3 can do that ![]()
Thank you! Even a video demonstration it
Imagine that such a ‘tiny’ feature can mean the world to some.
I need to resist the urge to post your video in the MPC thread and ask if the Live 3 can do that ![]()
Agreed - its surprising that you can’t do that on the MPC!
Must be so annoying.
MIDI Mappings and Control Surface Scripts : Now you can create and modify MIDI Controller mappings from Push, and customize which control scripts your connected MIDI device uses. Control scripts can also be deactivated entirely, so that you can use custom mappings without conflicts. MIDI Mapping is also partly accessible via Live on Push 2 and the tethered version of Push 3.
Mapping Max for Live Devices : A new “Visible” option allows Max for Live devices to add more parameters directly to the device view on Push 2 and 3. This expands the range of parameters that can be controlled on Push to features like modulation mapping in LFO or calibration in CV Instrument.
Excellent Update! Great news for MAX instruments (looking at you Fors ;-))
PS- Live 12.4 beta out, lots of cools stuff!
Full list of updates
It truly is. So annoying in fact that some MPC users are leaving Akai for Ableton ![]()
Of course there are more annoyances, but that is a huge one for actually performing live.
You can now use midi control surfaces! You cannot just drag your remote scripts folder to the Push’s User Folder though. I tried to add a Roto Control script and it doesn’t work. Yet.
Omg that is AMAZING.
So basically we’ll be able to:
Map midi controllers on the fly (ctrl + m style)
Enable control scripts (i.e. the Roto control’s Ableton live script will now work with push)
Enjoy better implemented M4L devices
If that’s correct, that is a phenomenal update
Should have read this first - sucks that the Roto didn’t work. Which new control scripts do work?
I say “new” because some control scripts (novation controllers, kontrol s49 Mk3) worked already
This news has almost killed my gas for the TR-1000 tbh. Just another example of how making beats on the push 3 will be more convenient for me
I’ve successfully hacked the new feature to enable Roto-Control to work. But you need to be confident with existing methods of gaining access to Push 3 via ssh, so the instructions are far from suitable for everyone.
General pointer for people who do have the required confidence and skills to achieve this:
Push 3 linux location of built in Control Scripts: /opt/push3/products/live/Live/AppLive/Python/remote-scripts/
I made a new subdirectory there and copied two .pyc files from the computer version of Roto-Control Ableton script in User Library, to the new folder I created at above location, rebooted, saw ROTO listed in the new Control Scripts menu, selected its MIDI ports and boom, it all seems to be working.
May I ask weich specific new feature you are referring to?
That sounds promising - what’s the “standard” way of bringing over control scripts? I.e. what’s the point of this update - is it just that the roto control script in particular isn’t working?
MIDI mapping
Until the new beta control scripts had no user interface for Push 3 standalone. So a bunch of ones that Ableton already included did work previously, but there was no ability to fiddle with their settings (ie selecting MIDI input and output ports), the whole thing was invisible to users.
Now we have visibility in terms of being able to see a list of Control Scripts and to manually set their MIDI ins and outs, or set them to none.
What is not clear is whether Ableton intend to provide a location within the User Library where users can easily add other scripts using the existing Live methods for copying files to the Push 3. I had a very brief try at creating my own folder for this, but it didnt work, which is why I went ahead and hacked the push 3 using ssh so that I could copy the Roto-Control scripts to the same place that all the built in scripts live on the Push 3.
Ah yes there are a bunch of stock scripts with Ableton aren’t there.
Thanks for the detailed explanation!
Still no fix for the browser bugs. ![]()
Indeed. I seem to recall that previously they only had a subset of these setup to work on Push 3 Standalone, and just added a few new ones occasionally. Now that they are a lot further along with enabling this feature more comprehensively, the list of included ones that work on Push 3 standalone is probably much longer and more like what people were used to on desktop.
Pardon my ignorance, but what is ssh? I’ve seen you mention it twice.
Its a secure shell thing, in this case its a way that power users can connect to the computer with linux that lives inside the Push 3 standalone, look at and manipulate all the files on the drive, etc. But its text-based command prompt/terminal nerdy stuff, so not within the comfort zone of everyone.