MIDI Kinetics Forum

no ideas?

I whish to assign controls to Lemur on the fly while I am working on Ableton. That way I'd make a picture of what params I am controlling via midi.

This can only be achieved IF the DAW in question sends that data in the first place (and then we can start wondering of how to decode it).

In case of Ableton Live that is not possible by default - it might be achieved if you have MaxForLive, and you design your own M4L device which will look up in specific stuff of Live's API - and even then Im not sure if its possible. Thinking about it, I really think even then, its not possible, the reason being I dont recall anything in Live's API referencing which parapeters are midi mapped and which are not in order to retrieve that data and send it to Lemur.

Frankly, you dont need a Lemur scripting God - you need a feature in DAWs which doesnt exist (at least in those I know of and have worked with).
For Reason I really don't have a clue although I suspect it wont be possible for the same reasons.

In situations like these, and given the "nature" and freedom that Lemur provides why dont ya just make a Lemur project that controls ALL the parameters you wish to control and show-hide elements if the surface gets "massively clogged" and full of controls?

My current Ableton Live - Lemur controller features around 10 midi channels x 127 CC numbers = 1270 parameters. No need to re-map anything on the fly, anything I want is already there and of course named after the mapped parameter.
Cumbersome? Yes it is. It has taken me months to design this "template" project in Ableton and Lemur just came to "unify" what i was already controlling with 3 different controllers, but yes its "doable".

Thanks for the reply.

The reason I wish to do this is because I usually assign five or six (different) params via midi per project to do things on the fly. If I actually could see those controls, it'd make me work faster.

Ex: Open up this project from some days ago and voilà, my three filters and two envelopes from different synths and fx.

Then, when I put all together to my live performance, I might have for example one lemur page per track with its particular params, all named correctly.

I actually own Max 4 Live so maybe I have to think in other way of doing this.

Hear ya!

Since we are talking about live-gigs stuff and not production (which is also how I use Live) my approach is to have a saved project with the same synths and the same effect chains, the same tracks and sends, and just fiddle with the parameters and have some preset synth sounds ready and organised into folders. So it made sense to me to have pre-mapped all the parameters I thought would make sense to have under my fingertips while performing (hence the huge amount of parapeters mapped which I described in previous post). Then, since all the "objects" in Lemur are mapped statically (I do not re-map them to other stuff) they are just named after those mappings.

Actually coming from using traditional controllers where I had to resort to sticking litle pieces of paper with parameters' names handwritten on them - having the tactile feedback and object naming of Lemur seemed Godsent - I never thought of "what if i want to re-map that knob over there?" because I never did it with my physical controllers too (it would then be too hard to remember what is where)

Isn't there some kind of Live to OSC translator that was written in python?

I seem to remember dealing with it when using the Live Control template for touch osc

it was sharp enough to send the clip colors and clip names over as well as a bunch of other stuff

Yeah
Thats the other option and what LiveControl uses - Remote Scripts with access to the underlying API
There are many ways to skin a lemur . .
MM