live.tab midi mapping each tab
Hello everybody,
I'm trying to midi map or key map a live.tab object in Live, but it's the same in max. The live.tab object has 3 tabs and I'm expecting that I can assign each tab to a different midi or key command. The only way it works is to have one single midi or key command that cycle between tabs.
Let's say I have the default live.tab that comes with 3 tabs labeled "one" "two" "three". Let's say I would like to assign the numeric keys "1", "2" and "3" to the tabs in order to directly control the switching. I can' find any possible way; I can assign only one command.
I can't figure out how to have 3 different midi or key command to select directly each one of the tabs of live.tab.
Any suggestion?
forget mappings, use direct midi.
If I were in that unfortunate position to have to use Live and to
have to control that tab using keystrokes 1 2 3
this is only thing that I could imagine to work ( only on Mac)
Thanks a lot SOURCE AUDIO,
Using a trasparent ubutton over the live.tab and enabling them for mapping, seems to work pretty fine. This allows me to map midi control or keystroke on the fly, without fixing it while patching.
I think this could be much simplier if live.tab could have a way to direct assign midi or keys to each tab.
did you try to record automation in Live ?
In Max things are easier, in Live you can't map anything
to object if it does not have parameter mode
"automated and stored"
In Live my workaround doesn't work at all... in Live utext objects aren't mappable, even if the parameter visibility is set to "automated and stored".
Any other clues that let me map live.tab on the fly?
The live.tab object has 3 tabs and I'm expecting that I can assign each tab to a different midi or key command.
Your expectation is wrong. [live.tab] is a single object and, therefore, can be mapped only once (as you already noticed).
Why not use multiple [live.text] next to each other? Those are mappable. You can also use them as transparent overlays.
Use the live objects instead of the regular max objects if you want compatibility with Live (mapping, automation, etc). So [live.menu] instead of [umenu], for example.
As first, max needs no mappings.
Assigned Midi gets received no matter what,
and one can route device, midi channel , whatever to control something without restrictions.
Live in comparison is a misery because one can't receive anything unless a track is
input monitored, and mapping as you can see is simply useless when it comes to
buttons and anyway one can't select which device to receive from.
Live developers seem not to realise that keys have press and release ?
What is that good for ?
And then one gets that objects to fiddle into automation,
storage , undo history flood ...
Thanks guys,
this is very helpful. I understand that there's no way in doing something mappable on the fly in max that works fine in Live. Also using live.text as buttons as transparent overlays over live.tab doesn't work, because when you map each button to different keystrokes, you need to press twice to trigger a change.
Implementing the direct mapping (key or midi) in the patch itself seems to be the only workaround I can figure out (obviously with the suggestion of SOURCE ADUIO ;-))
well you can get away with that double key press
just set live.button to trigger on both transitions.
But you can't prevent adding to undo history so simple.
but that works here just because you don't need to set 1 or 0
using mapping.
like to hold and release when you want which would make sense