Hi folks,
I am finally able to take my single Mandal pad for a rip.
I noticed whatever I trigger in Logic Pro, the pad surface is responsive but the pad portion is quiet no matter how hard I hit.
I opened up the utility setup @ https://synesthesiacorp.com/mandalav3/utility/#
and noticed that any portion of the pad, no matter how hard I strike it, cant get above 27. The rim pads operate as expected and get up to 127.
Any tips here? Am I missing something?
Thanks!
update= I scrolled through the preset maps and when I returned to Trigger Map Default, it now works as it should.
Velocity Mandala 3.0
Re: Velocity Mandala 3.0
You can adjust the velocity response of the V3 surface using the 'Surface Damping' parameter in the V3 Utility app. Setting Surface Damping to somewhere in the range of 45-75 would do it based on your preference. You can option-click (or alt-click) where it says Surface Zones in the Utility and check the Surface Damping parameter there.
If your Surface Damping parameter ever changes to a different value without you intentionally changing it please let us know if you are Windows or Mac and if you use the online version of the V3 Utility or the offline version. Most importantly, if you notice that it happens and you can reproduce the steps to make it happen please let us know what those steps are (even if the steps include things you are doing in other software).
What could be happening is if anything in your setup is accidentally sending MIDI messages into your V3 or into the Utility app there is a possibility of V3 internal parameters being changed when you don't want them to. The V3 is only meant to be an Input Device to your computer and shouldn't be set as an output device.
If your Surface Damping parameter ever changes to a different value without you intentionally changing it please let us know if you are Windows or Mac and if you use the online version of the V3 Utility or the offline version. Most importantly, if you notice that it happens and you can reproduce the steps to make it happen please let us know what those steps are (even if the steps include things you are doing in other software).
What could be happening is if anything in your setup is accidentally sending MIDI messages into your V3 or into the Utility app there is a possibility of V3 internal parameters being changed when you don't want them to. The V3 is only meant to be an Input Device to your computer and shouldn't be set as an output device.
Re: Velocity Mandala 3.0
I have a similar problem, but it's predictable and the solution can just be part of your workflow.
Anytime I switch between Mac and Windows, the pads will have the problem as explained above. Although the Utility will have my previous settings for sensitivity, the monitor won't read anything above 25ish for velocity. I just click into the sensitivity setting, and make a small adjustment, then go back (if the surface is 39, I just click it to 40 then back to 39). Then the monitor will read the full 0-127 range for velocity. I do this for all my pads.
(To answer the question above: I use the web utility for Mac, and the offline for Windows. I've never got the web to work on windows, in any browser or security setting, just fyi.)
Anytime I switch between Mac and Windows, the pads will have the problem as explained above. Although the Utility will have my previous settings for sensitivity, the monitor won't read anything above 25ish for velocity. I just click into the sensitivity setting, and make a small adjustment, then go back (if the surface is 39, I just click it to 40 then back to 39). Then the monitor will read the full 0-127 range for velocity. I do this for all my pads.
(To answer the question above: I use the web utility for Mac, and the offline for Windows. I've never got the web to work on windows, in any browser or security setting, just fyi.)
Re: Velocity Mandala 3.0
Thank you for that info. We would like to look deeper into this by being able to reproduce it in here in the lab.
Could you please let us know more info about the steps involved when switching between Mac and Windows? It will also help to know what browsers you are using for the V3 Utility on each system and if the issue happens no matter what programs you are or aren't running on the machines when it happens.
When you see the Utility showing your previous settings for Surface Damping but the pad isn't reading anything above 25ish for velocity please reselect that Mandala in the device dropdown and see if the Surface Damping parameter updates from what appears to be its previous setting to its actual (corrupted) value instead.
Regarding the online Windows version of the Utility we just tested https://utility.mandalaV3.com in Chrome and Edge on Windows 11 and Windows 10 with no issues so please let us know what machine and OS you are running and what happens (or does not happen) when you go to the Utility at that address and connect a Mandala. As a note, please do a hard refresh of the Utility site in your browser since an updated version was recently uploaded.
A hard refresh in Chrome on a Mac can be done by holding down the Shift key and clicking the Reload button.
A hard refresh in Chrome or Edge on Windows can be done by holding down the Ctrl key and clicking the Reload button.
If the issue turns out to somehow be caused by the offline Windows version of the Utility then perhaps getting you going with the online Windows version of the Utility is something that could help while we work on the offline version.
Again, thank you very much for your help with the details.
Could you please let us know more info about the steps involved when switching between Mac and Windows? It will also help to know what browsers you are using for the V3 Utility on each system and if the issue happens no matter what programs you are or aren't running on the machines when it happens.
When you see the Utility showing your previous settings for Surface Damping but the pad isn't reading anything above 25ish for velocity please reselect that Mandala in the device dropdown and see if the Surface Damping parameter updates from what appears to be its previous setting to its actual (corrupted) value instead.
Regarding the online Windows version of the Utility we just tested https://utility.mandalaV3.com in Chrome and Edge on Windows 11 and Windows 10 with no issues so please let us know what machine and OS you are running and what happens (or does not happen) when you go to the Utility at that address and connect a Mandala. As a note, please do a hard refresh of the Utility site in your browser since an updated version was recently uploaded.
A hard refresh in Chrome on a Mac can be done by holding down the Shift key and clicking the Reload button.
A hard refresh in Chrome or Edge on Windows can be done by holding down the Ctrl key and clicking the Reload button.
If the issue turns out to somehow be caused by the offline Windows version of the Utility then perhaps getting you going with the online Windows version of the Utility is something that could help while we work on the offline version.
Again, thank you very much for your help with the details.