Page 15 of 17
Re: Ubermap for Push 2 (VST/AU parameter remapping)
Posted: Mon Nov 22, 2021 3:29 pm
by vokinpirks
Horselover Fat wrote: ↑Fri Nov 19, 2021 7:05 pm
2021-11-19T19:58:17.705834: info: RemoteScriptError: unexpected character after line continuation character
2021-11-19T19:58:17.705859: info: RemoteScriptError:
2021-11-19T19:58:17.705884: info: Exception: Script could not be loaded.
Sorry, I really don't know what to suggest. The error message looks so weird. As if the files got somehow corrupted.
Re: Ubermap for Push 2 (VST/AU parameter remapping)
Posted: Tue Nov 23, 2021 3:09 pm
by Abuwabu
Vokin... is there anyway to change the display range of a mapped parameter from 0 - 1.0 to 0 - 127 (for example)?
Re: Ubermap for Push 2 (VST/AU parameter remapping)
Posted: Tue Nov 23, 2021 5:16 pm
by Abuwabu
Abuwabu wrote: ↑Tue Nov 23, 2021 3:09 pm
Vokin... is there anyway to change the display range of a mapped parameter from 0 - 1.0 to 0 - 127 (for example)?
And perhaps having a centralised pan pot running from -64 to 0 to 64?
Re: Ubermap for Push 2 (VST/AU parameter remapping)
Posted: Tue Nov 23, 2021 8:10 pm
by vokinpirks
Abuwabu wrote: ↑Tue Nov 23, 2021 3:09 pm
Vokin... is there anyway to change the display range of a mapped parameter from 0 - 1.0 to 0 - 127 (for example)?
You can try this out
https://github.com/vokinpirks/ubermap/b ... ush-2-only
Try to define all discrete values:
Code: Select all
[ParameterValues]
Param = 0, 1, 2, 3, .., 127
Judging by what is said in the manual, Ubermap should map 0..127 to 0 - 1.0 correctly.
Sure it would require much handwork, but I think this is the most adequate way to achive what you want for now.
Re: Ubermap for Push 2 (VST/AU parameter remapping)
Posted: Wed Nov 24, 2021 9:37 am
by Abuwabu
Ah yes.... I read all the bumpf on parameter values; but didn't think to manual type in all the number 0-127. Thanks
Re: Ubermap for Push 2 (VST/AU parameter remapping)
Posted: Fri Dec 03, 2021 7:19 am
by Abuwabu
Vokin... what was the thinking behind removing the hash maps for mapping Kontakt/Reaktor/etc... what was the problem with it?
Re: Ubermap for Push 2 (VST/AU parameter remapping)
Posted: Sun Dec 05, 2021 8:43 am
by vokinpirks
Abuwabu wrote: ↑Fri Dec 03, 2021 7:19 am
Vokin... what was the thinking behind removing the hash maps for mapping Kontakt/Reaktor/etc... what was the problem with it?
That's a good question. I did that like a year ago and can't remeber exactly why. Perhaps I was annoyed with the fact Ubermap creates a new device config every time I add new parameters to that device via the Configure button.
By the way, I have an experimental version where this hashing feature can be enabled on per-device basis, meaning you can have it on for Kontakt/Reaktor and off for all other devices. I made some basic testing and it seemed working. I can upload it to Github for you to try it out, if you will.
Re: Ubermap for Push 2 (VST/AU parameter remapping)
Posted: Sun Dec 05, 2021 4:45 pm
by Abuwabu
Yes please do... it would be good to see what's going on
Re: Ubermap for Push 2 (VST/AU parameter remapping)
Posted: Sun Dec 05, 2021 9:30 pm
by vokinpirks
delete this pls
Re: Ubermap for Push 2 (VST/AU parameter remapping)
Posted: Sun Dec 05, 2021 9:31 pm
by vokinpirks
delete this pls
Re: Ubermap for Push 2 (VST/AU parameter remapping)
Posted: Sun Dec 05, 2021 9:33 pm
by vokinpirks
Abuwabu wrote: ↑Sun Dec 05, 2021 4:45 pm
Yes please do... it would be good to see what's going on
Done. The changes are in a separate branch tho. Only the
Devices\UbermapDevices.py file has been updated. You can just download and place it to the MIDI Remote Scripts/Ubermap folder and restart Live. Back the old file up first though.
There are also some changes in the
global config too.
The section [Strict_matching] has been added. You need these lines:
Code: Select all
[Strict_matching]
Kontakt = PARAMETERS
Reaktor = PARAMETERS
They tell Ubermap that Kontakt and Reaktor should be treated as 'multi config devices' and that configurations that belong to those devices must be uniquely identified by hash of actual parameters set (just how things were working before I ruined everything). Update your main config file accordingly.
Ignore the other lines in the new config for now.
Let me know how (and if) it works.
Re: Ubermap for Push 2 (VST/AU parameter remapping)
Posted: Mon Dec 06, 2021 4:08 pm
by Abuwabu
Brilliant. Thanks VP. I'll give it whirl over the next few days...
Re: Ubermap for Push 2 (VST/AU parameter remapping)
Posted: Mon Dec 13, 2021 7:34 am
by vokinpirks
Abuwabu wrote: ↑Mon Dec 06, 2021 4:08 pm
Brilliant. Thanks VP. I'll give it whirl over the next few days...
Hey, so how is it going? Works as expected or...? I want to merge this feature into to the master, but first I need to be sure it works not only for me.
Re: Ubermap for Push 2 (VST/AU parameter remapping)
Posted: Mon Dec 13, 2021 12:33 pm
by Abuwabu
Unfortunately, I'm at home ill. I will report back as soon as I'm back in the studio
Re: Ubermap for Push 2 (VST/AU parameter remapping)
Posted: Thu Dec 23, 2021 3:03 pm
by Abuwabu
vokinpirks wrote: ↑Mon Dec 13, 2021 7:34 am
Abuwabu wrote: ↑Mon Dec 06, 2021 4:08 pm
Brilliant. Thanks VP. I'll give it whirl over the next few days...
Hey, so how is it going? Works as expected or...? I want to merge this feature into to the master, but first I need to be sure it works not only for me.
Back on my feet, and in the studio.
Downloaded the zip of the improvements branch, and installed on a fresh copy of Live 11.1 Beta, but it doesn't work at all. There are no logs generated so it's not crashing, just not functioning.
UPDATE
---------
I ditched the Ubermap folder in Remote Scripts, and reinstalled from your main branch to get back to a working version.
All good, so I copied over just UbermapDevices.py, replacing the original with the one from the improvements branch, and it broke.
UPDATE II
----------
Just copied over the new Config/devices.cfg, and it now reads previously mapped devices; but won't map anything new.