Ableton Forum

kineticUk wrote:What does MEH mean ?

Definition of meh :.

(mé')

1. (n.) A multi-purpose response, primarily used to imply a degree of indifference. Tone of voice and circumstance often implies a meaning. Can be used when you don't want to answer an awkward or embarrassing question, or if you just plain have nothing else to say, and you want the other person to interpret the "meh" however he/she chooses. As in: Q: "What do you think of my new dress?" A: "Meh." or Q: "What do you want to do tonight?" A: "Meh."

hoffman2k wrote:

Spiralgroove wrote:you should only have to hit midi learn the first time you connect your controller

save a profile and be done.

I don't agree. MIDI learn is different from MIDI map.
A MIDI map is for the good of humanity.
MIDI learn is for the spur of the moment.

ill agree with this
you should only have to map it once though

Spiralgroove wrote:

hoffman2k wrote:

Spiralgroove wrote:you should only have to hit midi learn the first time you connect your controller

save a profile and be done.

I don't agree. MIDI learn is different from MIDI map.
A MIDI map is for the good of humanity.
MIDI learn is for the spur of the moment.

ill agree with this
you should only have to map it once though

Yeah. Thats the whole point of this post.
They need to improve the specs of the custom map. So that we can edit our own and share it with other people who have the same controller.

Saving midi controller assigments would be nice...
The template that you can edit manually is a small step in the right direction...

Hell yeah!!!

I don't know what native support is but it seems to be important so yeah!!!!


F*CK! YEAH!!!!!!

hoffman2k wrote:Yeah. Thats the whole point of this post.
They need to improve the specs of the custom map. So that we can edit our own and share it with other people who have the same controller.

Couldn't agree more...and thanks for the MEH definition.
Please ableton just give us the tools, leave us to deal with making our devices work like they should. Its not a problem seriously...sort us out though.

Adonis wrote:F*CK! YEAH!!!!!!

Fuc*in' right...

definitely, they should DRASTICALLY expand the automap scripts so people can do their own. I'd much rather they do that and let people write scripts for their controllers.

this way, they'd hopefully be able to use their resources to make live better in other ways!

(like, I don't want support for every single control surface out there, just for mine )

davec1 wrote:(I don't want support for every single control surface out there, just for mine )

Yeah me too, whats that your controller isn't supported...thats a shame. Hold on a second, I'll just get my violin. Run along now Only kiddin' you know.
Plus automap great idea...but not so great, if its not setting up the controllers to where we would normally like them to be. Instead its automapping maps that we don't particularly like very much. Know what I mean ? Much better they leave all that in our capable hands.
Give us the tools fools...

kineticUk wrote:

Dammit! I have that exact same vest! DOH!

but yeah... midi. Sure thing

What I would love for the future to bring is a much tighter integration with hardware, preferably not via midi. Midi sucks - said the guy with about 8 midi controllers...

Is that OSC? Or are there other possibilites out there?

Well osc is good, no doubt. But apparently there are alternatives on the way which are better. For instance osc needs an ip address and so on, whereas a simpler solution would be more appropriate. Imagine something like OSC that was simple plug-and-play. Wouldn't that be sweet?

Plug in a control surface, and all the hip-and-happening controls simply move to the surface? Etc. Etc.

Ideally there is so much that could be done with a proper music networking setup, that OSC seems kind of .... well... lame.

brand of controller shouldnt even be an issue
you should pull up the interface and it says
"ok i detect X controllers is that correct Y or N"
"does your controller have X feature? press it now"
or something to that effect...
"ok done your keyboard is now automapped, save profile as______"

then you could just load profiles for devices you have created, share them, etc..

yeah, that sure sounds easy enough.. But when you start thinking it through the difficulties become apparent quite quickly....

Spiralgroove wrote:brand of controller shouldnt even be an issue
you should pull up the interface and it says
"ok i detect X controllers is that correct Y or N"
"does your controller have X feature? press it now"
or something to that effect...
"ok done your keyboard is now automapped, save profile as______"

followed by

"click here to render your hit trance track to disc" at which point you won't need a controller, just Live, a mouse and a writable CD.



The problem as I heard it described by the Abes while pinching a loaf in their bathroom (very clean btw) was that windows detects USB devices when an application starts up, so Live can't predict what devices would be connected at any given time. That's why you have to reset the devices in the midi preferences. What the Mac excuse is, I have no idea, I ripped a fart and Henke had to leave the bathroom to get a sampling mic, Gerhard just washed his hands and left.

I kind of like it that way, if I wasn't resetting my midi device settings all the time I'd be making music, and if I'm making music I might hurt my neck from bobbing to my tracks.

Live 7 will address this but not have an edit button
Live 8 will have an edit button but this will break
Live 9 will be bought out by Native Instruments and only be supported Win 95.

live can already midi learn any controller regardless of brand, whats the big deal?
as long as you dont change the cc assignments internally everything should line up...right?