M4L idea - the big missing one - coders needed

[tone61]

If you will do new versions after 0.9.1. please do NOT use version number in the file name.
When you've used older version in some live set and replace it with new, Live cannot find the old device when opening a live set.
So even though you can show Live that it should use the new device instead, you have to re-do all the parameter value definitions inside the device and midi mappings.

[Because789]

If you will do new versions after 0.9.1. please do NOT use version number in the file name.
When you've used older version in some live set and replace it with new, Live cannot find the old device when opening a live set.
So even though you can show Live that it should use the new device instead, you have to re-do all the parameter value definitions inside the device and midi mappings.

Including the version number in the file name is recommended by the m4l production guidelines. The file name was not the reason you had to redo the settings, it had to do with the changes in the "Long Name" attribute of the live.x objects. There's a chance that a further improvement will again make a renaming necessary (that's why it's still a beta device). If you are happy with how the device works right now just don't replace it with a future version.

But there is also a great chance that it will not be further improved due to the limitations of the live.x objects, we'll see...

[filter_7]

But there is also a great chance that it will not be further improved due to the limitations of the live.x objects, we'll see...

and what about your idea to do a Push version?

[Because789]

and what about your idea to do a Push version?

I'm working on that Push device. It's still in a very early stage and it will take some time. If you wanna beta test it, send me a pm with your email adress and I'll send you the device as soon as the basic functionality should work.

[filter_7]

@Because789: Looking at the 'momentary 8' device i found the use of keyboard note assignment very handy and super reliable for automations.
Recording a single note for automation the device call that parameter only for the duration of the note.

This made me think about an upgraded version of our FixedValueMapper device with that concept:



You see 4 multimap with 8 different fixed values, and also an assignable keynote for each value, as on momentary 8 device.

I am wondering if this concept could be adapted to our device, and make it rock solid.

[Because789]

I am wondering if this concept could be adapted to our device, and make it rock solid.

Since the Push device will work with MIDI notes as well, it should be fairly easy to adapt the Momentary 8 approach once the device is ready. The main task for now is to put down a notes handling which makes sense and is usable in a live context. I have serveral ideas for that but it needs time to implement it (controlling one parameter with one button makes a huge difference to controlling one parameter with multiple buttons).

Just for the record, Paraminator is worth a look too viewtopic.php?p=1516607#p1516607 (the matrix routing is very clever, but automation recording is also problematic).

[tone61]

Would it be possible to make this Fixed_value device work so that once you have mapped some parameter, you could read parameter's cuurent value to one of the values that the device remembers? So this would be an alternative to manually typing values.

So you could go to a value, choose Read Value. Then turn the parameter's UI knob in Live until it sounds good, move to next value and again Read Value.

[filter_7]

Your idea is interesting especially when the device should map parameters on different tracks.

If you have complex values to follow the best choice at the moment is to have the device on the same track of your mappings.

I dream to get rid of dummy clips, that are in fact a fixed values approach to automation.

[Because789]

Just released a complete rework of the device posted above:

http://www.maxforlive.com/library/device/1657

For feedback please head over to the new thread:

viewtopic.php?f=55&t=195188