set quantization via midi buttons?!?

[docprosper]

OK, this should be simple but I'm stuck. I want to be able to change the global quantization with some buttons on my Launchpad; I'm not currently using the "User 1" section so I have buttons to spare. I want to program a set of buttons for 16th, 1/4, 1 bar, etc. settings. Hit a button, get a new quantization setting. Midi learn allows me to assign a button to the global quantization but I can't fat-finger a value into the midi settings page. Any ideas?

My backup plan is to code up a M4L device with buttons that I can then midi-learn to, but I'd rather go native. Thanks in advance.
-Hamish

[S4racen]

Hi Hamish,

There's no direct way with midi mapping to be able to do this but if you look at the quantisation menu you'll see a number of the options have keystrokes... A simple utility like midistroke should be able to convert the incoming midi to keystrokes and achieve your aim...

If you build in max4live you'll need relatively little, an observer for each button you want to use with an equivalent live.object to enable the lighting... Then you can set any value of quantisation based on the live object model...

Remember though that M4L is designed to be used with User 2...

Cheers
D

[yur2die4]

I forget if this allows you to do it: http://beatwise.proboards.com/index.cgi ... thread=716

..I'm trying to remember if it requires midi feedback. If that is the case, then you could just as easily map MIDI Clips CC# in varying amounts that is assigned to the Quant.

This probably sounds pointless, but Automap is a pretty easy way too (ctrl + #'s , or varying CC amounts). If Automap is installed, accessing it on the LP is as easy as holding User2 then hitting Down Arrow. I think the MIDI Feedback would be the better route though, less pages to mess with .

[docprosper]

thanks for the tips guys... If there's no native solution I'll probably go the M4L route as I'm already fluent & don't want to introduce any new utilities right before my upcoming set. I'm still shocked that this can't just be mapped, I don't normally bitch about Ableton but this seems pretty trivial, doesn't it?

...and Darren, I'm hoping to use user1 because I'm using Octop4d with user2 . I've got a global M4L mixer device already in my set so my thought was that I could add some buttons to that device that send quantization commands to Live via the API. Then I can midi-map my Launchpad user1 buttons to the buttons in my device. Should work, right?

I suppose I could work this into your Util1ty screen as there's some open space but I'm not ready to crack the hood on your device just yet!

-Hamish

[S4racen]

It's already in Utility isn't it?? the round side buttons??

Sorry didn't realise you had it!

Cheers
D

[docprosper]

I'll re-read the manual, I must have missed that one. You rock!

[docprosper]

too funny, I had just looked at the Octop4d manual before starting this post. My eyes seem to gravitate towards the grid buttons and ignore the side buttons for some strange reason.

I'm still surprised that this basic functionality doesn't exist. I seem to have more buttons than knobs and sometimes would prefer a quick button or key press to set a parameter. I may work up a simple M4L device sometime (if it hasn't already been made...) that allows the user to select a parameter path and a setting to load upon a button trigger. Then a hw button or key could be midi-mapped to that. All in good time...

Thanks again!

[littles pliffa]

If you have a launchpad a very easy solution would be Automap Pro. For 30 dollars you can map whatever shortcut you want to your midi buttons. I have shift+tab and cmd+opt+P for plug in control. Along with some others

[essegibi]

clyphx will be able to snapshot different settings(so will kapture obviously) but with clyphx script you´ll also be able to create clips which you use to change the global quant, these clips can then again be mapped to whatever you want..