Ableton Forum

I was wondering if the only way to install Ubermap on the Live 9 beta is via a manual install. The terminal script just installs only to my regular suite version.

fistikuffs wrote:I've installed Ubermap on 9.2.1b w7x64 and it seems to be fine so far. Created a few new configs and loads my old ones. Community mappings seem fine.

Good news! Thanks for testing. Maybe I can reactivate auto update on my live installation

rhythmhead wrote:I was wondering if the only way to install Ubermap on the Live 9 beta is via a manual install. The terminal script just installs only to my regular suite version.

Ah yeah, the script looks at the Suite rather than Beta version. You can either do it manually, change the script yourself, or try this version - note that I just changed it on Github and haven't tried running the script! https://github.com/tomduncalf/ubermap/archive/beta.zip

Has anyone got it working in 9.1.9?

Other any other success stories in 9.2 beta?

Just found out about this and I'm keen to give it a whirl. I've got a new computer coming this weekend and I'm going to be doing a fresh install so I'm trying to decide which version to start with.

This is totally the killer feature that Push has been missing, so excited to play with it!

hello,

this is brillant !
congrats to you guys
i really like the parameter remapping feature

unfortunately i'm a windows user
i've posted some info's regarding the windows installation and issues of blank parameters on push with certain devices:
https://github.com/tomduncalf/ubermap/issues/1

i've made an experiment with the parameters remapping + renaming
and i'm almost done ...but let me explain my case :

the goal is to dynamically change the parameters names both on Push and on the Max for live device itself
i've a 8 copies of a generic M4L Midi device with 8 parameters on 8 different tracks..
i set the parameters names of the devices (with the shortname attribute) through OSC
i Read / Write the "Max MIDI Effect_HASH.cfg" of the 8 devices to dynamically change the parameters name on push
it works but there's a workaround to refresh push screen : you need to change the focus to a another device and go back (i use a next/previous device selection patch for that)

the two major problems i see right now (probably windows only issues?) are

1/ when i compare the generated Hash for GenericDevice01.amxd inside the ubermap/Devices folder with a standalone MD5 program it doesn't match!!!
so i'm wondering if the Hash Analysis is done on the file itself or on the string (the device path)!
does anyone know a way to identify the String Path generated by the script on windows ?

i try to modify the script (without success)to add the device name to the created cfg file eg :"Max MIDI Effect_ GenericDevice01_HASH.cfg"
could be really nice to have something like that in a future version!

2/ i'm wondering if at some point it's possible to store all the devices Hashes.cfg in the LiveSet project Folder
using some Relative Path?? it will allow to store kind of Mapping/Naming templates for each project

EDIT: yes but it's painful!
a/ edit the "UBERMAP_ROOT = MAPPING_DIRECTORY = ..." to the absolute the live project path in UbermapLibs.py
b/ erase UbermapLibs.pyc
c/ create the Ubermap folder structure inside the Live Project folder
d/ create devices.cfg, browser.cfg and global.cfg
e/ reload the live project

to automate all this i use the Log.txt from Ableton/Live9.xxx/Preferences folder
extract the path of the current loaded live set :
"Default App: Command-line arguments: Document locations: file:///E:/==Live==/Folder/"
and then launch a batch... i'm sure there's an easiest way!
what do you think?

3/ i'm really a noob when it comes to python

1/ when i compare the generated Hash for GenericDevice01.amxd inside the ubermap/Devices folder with a standalone MD5 program it doesn't match!!!
so i'm wondering if the Hash Analysis is done on the file itself or on the string (the device path)!
does anyone know a way to identify the String Path generated by the script on windows ?

okay the MD5 takes the 'params' names
so the hash is done on a string not on the file name nor the file path
unfortunately it won't work with my setup since the parameters of the generic devices (on first start) have the same names
and the system only create one hash.cfg for all the generic devices

in my case the hash should be on the filepath + filename
does anyone can help me to modify this part of the UbermapDevices.py on line 45:
name += '_' + hashlib.md5(params).hexdigest()
to replace the 'params' with the path and the name of the device
thanks
C.

in my case the hash should be on the filepath + filename
does anyone can help me to modify this part of the UbermapDevices.py on line 45:
name += '_' + hashlib.md5(params).hexdigest()
to replace the 'params' with the path and the name of the device

okay if you need the device name in the cfg file just use device.name in
UbermapDevices.py

def get_device_name(self, device):
name = device.name
if self.cfg.get('use_md5'):
params = ''
for i in device.parameters[1:]:
params += i.original_name
name += '_' + hashlib.md5(name).hexdigest()
return name

okay lest one...sorry for the spam,

everything works like a charm
autonaming/remapping devices paramaters on the fly on both push LCD and the device itself
auto ubermap config (cfg's) pointing to the current project folder

BUT... the devices cfg's are only created on selection
is there a way to scan the whole Live Set and create all the cfg's at startup??

thanks

Many thanks tom and the others for compiling this.

Seems that it doesn't work here. When I open Live and click a device, Ubermap creates files - all good. But when I change these files for my needs and restart everything, there is no difference. I still get Bank 1, Bank 2, ... Any idea what could be wrong?

Other thing I want to do is to control drum rack sends of each cell with Push. Currently my solution for this is to have a M4L device Multimapper on each cell in the drum rack, mapped to corresponding sends. Then I have a device which "forwards" the signal from each of these sends to main return tracks of the project. Works ok but can quickly become too CPU heavy. Is there a way to map each of these drum rack cell sends via Ubermap to show on Push?

Just a quick question: I see there has been a few updates to the community mappings. Can we update these independently of Ubermap or do we need an Ubermap update for this?

So looks like Live 9.5 doesn't add anything new in terms of VST mapping, but does totally change the MIDI Remote Script code for Push... so it isn't going to be trivial to get Ubermap working with 9.5 I am taking a look at it but can't make any promises. Really surprised 9.5 hasn't added some kind of VST control reconfiguration for Push!

tom_d wrote:So looks like Live 9.5 doesn't add anything new in terms of VST mapping, but does totally change the MIDI Remote Script code for Push... so it isn't going to be trivial to get Ubermap working with 9.5 I am taking a look at it but can't make any promises. Really surprised 9.5 hasn't added some kind of VST control reconfiguration for Push!

From the changelog

A parameter configuration can now be saved as a default per AU or VST plug-in. This is done via a new context menu entry available in Live's plug-in device. The default configurations are stored in a "Plug-In Configurations" folder under "User Library/Defaults".

login wrote:

tom_d wrote:So looks like Live 9.5 doesn't add anything new in terms of VST mapping, but does totally change the MIDI Remote Script code for Push... so it isn't going to be trivial to get Ubermap working with 9.5 I am taking a look at it but can't make any promises. Really surprised 9.5 hasn't added some kind of VST control reconfiguration for Push!

From the changelog

A parameter configuration can now be saved as a default per AU or VST plug-in. This is done via a new context menu entry available in Live's plug-in device. The default configurations are stored in a "Plug-In Configurations" folder under "User Library/Defaults".

Ah I see - still no way to rename or group into sensibly named banks, but that's something. EDIT: looks like there might be a native way to do this, see below - can't see anything exposing this in the UI but I've not looked properly.

Having a quick look at the code it seems that the parameter names displayed on Push 2 are much more dynamic than Push 1, they have things like "use('OSC1 Octave').if_parameter('OSC1 On/Off').has_value('1').else_use('OSC2 Octave').if_parameter('OSC2 On/Off').has_value('1')" so the controls show and hide depending on the instrument state.

Sadly this hasn't been backported to Push 1 as far as I can see (separate code base with some shared elements) and in all honesty, working in software myself, I would be amazed if they did ever backport these changes as it's a lot of effort for an "old" device. Shame - can't help feeling like us Push 1 users were used as beta testers a little... If I find time I may see if it's possible to backport this to Push 1 myself, although I find so little time to use Ableton anyway these days that I'm not sure if/when that will happen... maybe we should all just buy Push 2 and hope they don't abandon it like Push 1

login wrote:

A parameter configuration can now be saved as a default per AU or VST plug-in. This is done via a new context menu entry available in Live's plug-in device. The default configurations are stored in a "Plug-In Configurations" folder under "User Library/Defaults".

Actually this is kind of interesting, the saved Plug-in Configuration file is a JSON file which suggests that remapping the controls might be possible, it has groups and names defined. I'm at work so can't verify if this actually works with Push but looks promising! Anyone fancy trying changing some stuff in the .appc file which is created in their user library and see what happens?

OK, we've not been totally abandoned

It is now possible to preview sounds from the browser with Push 1 as well. Auto preview can be toggled on/off.
It is now possible to load Samples from Push. These will be instantiated in Simpler.

- finally!