mapping push pad to a specific value of a parameter
mapping push pad to a specific value of a parameter
greetings!
have anyone achieved a launchpadish behaviour of Push in user mode? i'm interested in those 'virtual faders' which represent a vertical row with specific values for same parameter.
unfortunately, i'm not quite m4l patcher.
appreciated,
cheers
have anyone achieved a launchpadish behaviour of Push in user mode? i'm interested in those 'virtual faders' which represent a vertical row with specific values for same parameter.
unfortunately, i'm not quite m4l patcher.
appreciated,
cheers
-
SittingPanther
- Posts: 11
- Joined: Wed Sep 18, 2013 3:33 pm
Re: mapping push pad to a specific value of a parameter
You could have a horizontal row mapped to a parameter quite easily. This would only give control & not visual feedback though. Plus its a different orientation.
However, to do this:
Enter user mode on push
Enter midi map mode in ableton
select parameter
Hit the lowest and highest pads in the range you want to use. Push's pads ascend left to right, bottom row to top.
Exit midi map mode
Enjoy.
However, to do this:
Enter user mode on push
Enter midi map mode in ableton
select parameter
Hit the lowest and highest pads in the range you want to use. Push's pads ascend left to right, bottom row to top.
Exit midi map mode
Enjoy.
Re: mapping push pad to a specific value of a parameter
god, this is awfully simple and genius. thanks a lot!
-
TomViolenz
- Posts: 6854
- Joined: Mon Dec 13, 2010 6:19 pm
Re: mapping push pad to a specific value of a parameter
It's also totaly useless (sorry)
There are two ways to make Pushs User mode, well usefull.
1: The simple (and only really practical) one: buy a third party script or use a M4L device someone made.
2: The very involved one: Learn to script or build a M4L device.
(Workarounds using Bomes MT etc. would also work, but are just as difficult to implement.)
Ableton does not want you to use your 500€ Midi controller as a, well, Midi controller. If that wouldn't be so, they would have done the decent thing and made a ControllerEditor like their competition has done.
There are two ways to make Pushs User mode, well usefull.
1: The simple (and only really practical) one: buy a third party script or use a M4L device someone made.
2: The very involved one: Learn to script or build a M4L device.
(Workarounds using Bomes MT etc. would also work, but are just as difficult to implement.)
Ableton does not want you to use your 500€ Midi controller as a, well, Midi controller. If that wouldn't be so, they would have done the decent thing and made a ControllerEditor like their competition has done.
Re: mapping push pad to a specific value of a parameter
the idea of mapping this way (a range of button simultaneously pressed) impressed me, as well as the fact i didn't know about it till now))TomViolenz wrote:It's also totaly useless (sorry)
There are two ways to make Pushs User mode, well usefull.
1: The simple (and only really practical) one: buy a third party script or use a M4L device someone made.
2: The very involved one: Learn to script or build a M4L device.
(Workarounds using Bomes MT etc. would also work, but are just as difficult to implement.)
Ableton does not want you to use your 500€ Midi controller as a, well, Midi controller. If that wouldn't be so, they would have done the decent thing and made a ControllerEditor like their competition has done.
meanwhile i've started digging into gridlock device (http://www.sigabort.co/gridlock.html) which i assume resolves for me much more that just this topic's request
Re: mapping push pad to a specific value of a parameter
Gridlock is amazing, but then i would say that 
Cheers
D
Cheers
D
Re: mapping push pad to a specific value of a parameter
btw i'm surprised that gridlock is that scantily discussed over the forum and related ones. there's no dedicated topic to it with let's say gridlock-friendly devices, tips-n-tricks etc.. or maybe i'm missing something
Re: mapping push pad to a specific value of a parameter
I'm sure there'll be lots more soon, Lee's working hard at the next set of updates and they're stellar!
Cheers
D
Cheers
D
-
SittingPanther
- Posts: 11
- Joined: Wed Sep 18, 2013 3:33 pm
Re: mapping push pad to a specific value of a parameter
Very Welcome!ivarin wrote:god, this is awfully simple and genius. thanks a lot!
TomViolenz wrote:It's also totaly useless (sorry)
There are two ways to make Pushs User mode, well usefull.
1: The simple (and only really practical) one: buy a third party script or use a M4L device someone made.
2: The very involved one: Learn to script or build a M4L device.
(Workarounds using Bomes MT etc. would also work, but are just as difficult to implement.)
Ableton does not want you to use your 500€ Midi controller as a, well, Midi controller. If that wouldn't be so, they would have done the decent thing and made a ControllerEditor like their competition has done.
This solution deals with midi mapping in general. As it applies to midi itself, and basically every midi controller, it is illogical to write it off as useless. It is the most simple, native, and stable way to achieve said goal.
I have used 3rd party scripts, paid and free, with a range of midi controllers (launchpad, mpk mini, apc40, push, etc.). They can be amazingly useful and extend functionality to the moon and back. However, stability issues commonly do exist.
Same goes for max4live. Great. amazing. I almost always use m4l devices, but stability, and resource usage is at the mercy of the coders ability.
One should consider the use of extra scripts and devices dependent on how they are using Ableton. (e.g. studio production or live performance)
-
SittingPanther
- Posts: 11
- Joined: Wed Sep 18, 2013 3:33 pm
Re: mapping push pad to a specific value of a parameter
Gridlock does look pretty win. Has anyone given it much use?