M4L idea - the big missing one - coders needed

[Because789]

How to KEY/MIDI map:

http://www.youtube.com/watch?v=NAZt-D4eHTE

The mapped buttons work for now as toggle (first press on, second off), have to check how to change that.

[mothergarage]

He probably referred to this error

[Because789]

He probably referred to this error...[/img]

Oh, thanks for the reply! I guess I should have freezed the device then

It's never a good idea to rush with stuff like this, should have known that. Removed the download link and will up it when it's fixed.

[filter_7]

The mapped buttons work for now as toggle (first press on, second off), have to check how to change that.

Do you mean that now when you release it returns to default/0 value?
If yes the button should trigger a value with usual press/release.

If you're thinking about momentary buttons this can be a second version of the device, or if you're a M4L genius you could include the button type choice

I can't wait to see it in action!

[Because789]

If you're thinking about momentary buttons this can be a second version of the device, or if you're a M4L genius you could include the button type choice

That's exactly what I'm thinking of and I want to include the button type choice. Since I'm definitely not a M4L genius I'm happy that this work has been done by others Let's hope that the implementation is as flawless as I think it should be.

I can't wait to see it in action!

I plan to do the work tomorrow...

[Because789]

Up again for testing:

http://www.maxforlive.com/library/devic ... ues-mapper

Now we got 8 slots for parameter mapping and 64 mappable buttons. By default 8 buttons are assigned to each parameter. But you can choose to which parameter you want to assign a button segment (8 buttons). It's done with the tiny box on the left of each button segment.

Any feedback/suggestions for improvements are highly appreciated.

@filter_7: drop me a line if I should refer to you in a different way.

[filter_7]

Hey Because789, nice work!
I was thinking to have 8 parameters and you did it!
The routing possibility it's a good idea too.

I tested it and i noticed some strange things during clip automation recording:
- the automation line in the clip is blinking before the recording
- after the recording the 'return to automation' button is not working
- there are issues in the overdub recording (not correct overdub command automation)

Maybe some kind of conflict between button label names?
I did the test using key mapping on the pc keyboard.
Unfortunately i can't help in the coding, so any suggestion is welcome from other coders.

In live tweaking is very fun! Exactly what i needed!
Let me know when you can improve it, i will do all the crash tests needed

Thanks for including me in the credits, i appeciated it.

[Because789]

Glad to hear you like it so far! I was just messing around with an instrument rack with several synths on it and the chain selector mapped to the device. A lot of fun and I can see a lot of potential!

And thanks for reporting. I recognized some strange behavior, too. I need to work on the MIDI note handling since the workaround I implemented is untrustworthy. And as you suggested naming seems to need a clean up as well. Probably not today...

When you find more problems it would be great if you could provide a way to reproduce it.

[tone61]

Tried this today and it's really useful. Thanks!

[Because789]

Uff, after hours of investigation I at least can see now how much I underestimated the task. It starts with the limitations of live.button and ends with the troubles you probably will run into when you try to record automations.

I uploaded a new version anyway. The stuck button issue which could occur with the last version should be fixed now, in return there is no more color changing feedback on the buttons. In addition to that I set the automapping index to the numberboxes. On a controller like Push all the 64 numberboxes are now immediately available (8 banks containing 8 buttons). The naming of everything is also cleaned up.

I'm very interested to hear how you use/would like to use the device. It would be a great help for further improvements.

[tone61]

There is a similar new device with Youtube video showing how to use it

https://www.youtube.com/watch?feature=p ... VbHS6jhBHM

download:
http://www.maxforlive.com/library/devic ... ual-toggle

[Because789]

This one is very interesting too:

http://www.maxforlive.com/library/devic ... omentary-8

And let's not forget that you can simply map MIDI keys to a parameter range of buttons without a m4l device:

https://www.youtube.com/watch?v=YS-e2r5bef0

[filter_7]

@Because789: Just downloaded the new version, will let you know soon my impressions.

That's how i would use the device:
for audio: i have a guitar track with a FX rack with 4 chains inside. I need to switch through the chains to have different FX during the song.
for midi: i have a synth with an arpeggiator device before. I need to turn on and off the arp with different timing during the song.

These are only my needs at the moment, but i plan to use it as a glitch device and fx automations that are impossible to o with the turning of a knob.

The main concept is to record automation, for an easier and more musical approach during composition.

The momentary 8 device is great; its limitations are that is only momentary and the forced mapping to keys (similar to what you reminded about the simple midi map on a range of adiacent keys)
I would need free mapping and fixed custom values.

[Because789]

Automation recording is exactly what is giving me headache and it's not (yet?) possible with the device . What is so simple with a dial is not at all simple with a button (at least if I didn't miss something obvious). The main reason seems to be that Live only is able to record the values which the buttons send. I would need a way to catch these values and tell Live what value it should record instead. But I don't think this is possible with the Live internal MIDI mapping system (and believe me, I tried a lot of different approaches, I still would love it if someone could prove me wrong!).

Therefore I think for recording there is no other way than taking the Momentary_8 road (mapping the notes in the device itself). I already can see a lot of new problems along this road, but it seems easier to sort them out.

What controller do you use? Since I feel like I'm at a dead end I also thought about transforming the tool into a Push specific device.

[filter_7]

I have Push! So it would be great if you do it.
(Now for quick test i used a key mapping)

I tried the device and i'm pretty happy with it because automation works! At least i believe... All worked right with the exception of just one 'bug':
I have the arpeggiator on/off button mapped. 2 boxes used, first with 0 as off and second with 13 as on. I recorded the automation and at the end of the clip I have the arp on.
When the clip starts again I have the command on even if my clip started with the arp with off position.

Don't know if this is an easy task but i thought the device needs a sort of 'auto reset' every new beginning (the beginning of the clip).
This reset should be linked to our first parameter (of our 8 boxes/buttons) so it will be pushed at the start.

So maybe we need this kind of workaround that will help Live to understand our button commands operation. Let me know what do you think.

Do not give up!