mAp++ test
mAp++ test
hello
thread opened to test the device mAp++
the beta can be found there :
https://maxforlive.com/library/device/6 ... -plus-plus
it's a device to discard the mapping and binding of live's parameter.
previous posts are here :
viewtopic.php?f=35&t=241869&p=1786763#p1786763
---------------------------------------------------------------------------------------------------
@jbone
thank you for your feedback !
.the pop-up will be fixed very soon, a little mistake in the configuration of the device.
-about the several versions., the two modes are totally bypassing each other, and for my use I need both...
But maybe the "SelF" mode will won and I will remove the old one.
If you only use the new mode , it's the default one, the old should not disturb it at all...
-about the "del button" and the creation of preset in the UI, it's not really a choice.
Making devices that play with the live mappping is a bit tricky, especially in this device where you have to constantly affect ids and discared them continuously. You cannot, in Max, fill informations between the preset object and the [pattrstorage] object which manage them..and you have to because deleting presets cannot discarded the affectation made in this preset slot.
But I think of a workaround for a next release..
Thank you jbone !
Julien
thread opened to test the device mAp++
the beta can be found there :
https://maxforlive.com/library/device/6 ... -plus-plus
it's a device to discard the mapping and binding of live's parameter.
previous posts are here :
viewtopic.php?f=35&t=241869&p=1786763#p1786763
---------------------------------------------------------------------------------------------------
@jbone
thank you for your feedback !
.the pop-up will be fixed very soon, a little mistake in the configuration of the device.
-about the several versions., the two modes are totally bypassing each other, and for my use I need both...
But maybe the "SelF" mode will won and I will remove the old one.
If you only use the new mode , it's the default one, the old should not disturb it at all...
-about the "del button" and the creation of preset in the UI, it's not really a choice.
Making devices that play with the live mappping is a bit tricky, especially in this device where you have to constantly affect ids and discared them continuously. You cannot, in Max, fill informations between the preset object and the [pattrstorage] object which manage them..and you have to because deleting presets cannot discarded the affectation made in this preset slot.
But I think of a workaround for a next release..
Thank you jbone !
Julien
Re: mAp++ test
My comment about the buttons was just a compliment. I do not think that part needs any changes.
Keep up the good work!
This is an insanely powerful idea, assuming there are no gotchas.
Keep up the good work!
This is an insanely powerful idea, assuming there are no gotchas.
-
- Posts: 6025
- Joined: Mon May 15, 2006 12:15 pm
Re: mAp++ test
Had a quick look inside the patch.
From my experience, any [pattr] object used in a M4L device must have a name to work properly.
Also, to avoid the prompt to save a .json file, you have to enable Parameter Mode for the [pattrstorage].
From my experience, any [pattr] object used in a M4L device must have a name to work properly.
Also, to avoid the prompt to save a .json file, you have to enable Parameter Mode for the [pattrstorage].
MacBook Pro 13" Retina i7 2.8 GHz OS 10.13, L10.0.1, M4L.
MacStudio M1Max 32Go OS 12.3.1
MacStudio M1Max 32Go OS 12.3.1
Re: mAp++ test
Merci bien Chapelier de ton intérêt.
I already tried your 1st suggestion, but in was not enough.
...in fact it was simply an initial value of 1. on the Read and the Write buttons... :_\
I already tried your 1st suggestion, but in was not enough.
...in fact it was simply an initial value of 1. on the Read and the Write buttons... :_\
Re: mAp++ test
------------------UPDATE 0.5
-----4 modes :
the bindings can me recalled by :
- the SELECTED TRACK. It means that you can with one little controller, control all of your tracks when one is selected.
- the SELECTED SCENE, Each selected scene trigger a binding preset.
- the SELF MODE. map your controller or an LFO or whatever to the auTo.chAin slider and change all your binding when you want.
- the CHAIN SELECTOR of a rack, if the device is in a rack.
In this mode you have to put one device per chain.
------Bugs fixes
- the min and max values are well cleared.
- no more window popup when loading.
------>help button in the device.
If some people can test the device and tell me if they find some bugs or have suggestions, that would be great !
Thank you !
Julien
-----4 modes :
the bindings can me recalled by :
- the SELECTED TRACK. It means that you can with one little controller, control all of your tracks when one is selected.
- the SELECTED SCENE, Each selected scene trigger a binding preset.
- the SELF MODE. map your controller or an LFO or whatever to the auTo.chAin slider and change all your binding when you want.
- the CHAIN SELECTOR of a rack, if the device is in a rack.
In this mode you have to put one device per chain.
------Bugs fixes
- the min and max values are well cleared.
- no more window popup when loading.
------>help button in the device.
If some people can test the device and tell me if they find some bugs or have suggestions, that would be great !
Thank you !
Julien
Re: mAp++ test
It is not working for me in 10 or 11.
-The mapping buttons do not update to indicate a parameter was mapped
-I can only seem to map one preset. Trying to map another preset does not work
-Generally not working. Think it needs more testing on your end
Happy to test again when you have an update.
-The mapping buttons do not update to indicate a parameter was mapped
-I can only seem to map one preset. Trying to map another preset does not work
-Generally not working. Think it needs more testing on your end
Happy to test again when you have an update.
Re: mAp++ test
Hello Jbone
It seems that the device was not frozen when I uploaded it.
I re-uploaded it.
Can you tell me if it's working now ?
Thanks !
It seems that the device was not frozen when I uploaded it.
I re-uploaded it.
Can you tell me if it's working now ?
Thanks !
Re: mAp++ test
It's still not really working. Like, when I try to map and assign to presets, the behavior is inconsistent and does not work. I tried in 10 and 11.
I appreciate your efforts, but respectfully, I think this needs more thorough testing on your end before asking us to keep testing it.
Here is what I am doing:
-Add device
-Click new
-Click on the first preset
-Map a parameter
-Click new
-Click on the second preset
-Map a parameter
-Click on the first preset
-Notice the first preset is no longer mapped
-Click on the second preset
-Notice the second preset is no longer mapped
See what I mean? It is simply not working.
I appreciate your efforts, but respectfully, I think this needs more thorough testing on your end before asking us to keep testing it.
Here is what I am doing:
-Add device
-Click new
-Click on the first preset
-Map a parameter
-Click new
-Click on the second preset
-Map a parameter
-Click on the first preset
-Notice the first preset is no longer mapped
-Click on the second preset
-Notice the second preset is no longer mapped
See what I mean? It is simply not working.
Re: mAp++ test
thank you for your report.
..what is strange is that it's working quite perfectly on my computer
live 10.1.30 / max 8.1.8 win10 home.
What is your config ?
..what is strange is that it's working quite perfectly on my computer
live 10.1.30 / max 8.1.8 win10 home.
What is your config ?
Re: mAp++ test
Aahhh..
...I didn't read your post well.
You have to shift+click on the preset to store it !
..a store button will be perhaps in a next release..
...I didn't read your post well.
You have to shift+click on the preset to store it !
..a store button will be perhaps in a next release..
Re: mAp++ test
Ok thanks. The self mode seems to be working, in my very limited test. I tried chain mode in 11, and it was not working. The buttons were not displaying correctly.
I have some work to do for the next days, but I will keep an eye on the progress.
I have some work to do for the next days, but I will keep an eye on the progress.
Re: mAp++ test
Thank you jbone.
I still don't be invited to test L11...
..if it's working good on L10 will be a first victory !
If other people can get un eye on the device while my only beta -tester is at work it would be great !
I still don't be invited to test L11...
..if it's working good on L10 will be a first victory !
If other people can get un eye on the device while my only beta -tester is at work it would be great !
Re: mAp++ test
------------------UPDATE 0.6
- Add a Store button
- the track of the mapped parameter is written in each map box
Very often with this kind of device, only the name of the parameter is written in the Map
Button. But "Track Volume" is not very understandable when you have 24 tracks...
Here, each button shows the track where the controlled parameter is
(Usual Track / Return tracks/ Master Track)
- Add a Store button
- the track of the mapped parameter is written in each map box
Very often with this kind of device, only the name of the parameter is written in the Map
Button. But "Track Volume" is not very understandable when you have 24 tracks...
Here, each button shows the track where the controlled parameter is
(Usual Track / Return tracks/ Master Track)
Re: mAp++ test
------------------UPDATE 0.6.2
bug fixe.
- names of tracks were well saved but not properly displayed.
bug fixe.
- names of tracks were well saved but not properly displayed.