Hi Alexy,
I now have my studio rack back at home and will pick up with the Yamaha 01V implementation again soon. I recently bought an MCU.
After playing with the default MCU template, I found that the VPots don't seem to control switch parameters well - the internal value didn't always get to 1.0 (or above half way in some cases) to turn a switch on, so I set about trying to modify the preset.
I have added VPot Switches "VS1-8" (MIDI Notes 32 - 39) but only added logic for Switches 3-5, for
tr. Interleave, Phase and Input echo
I created Hardware controls called:
_funcVSw3
_funcVSw4
_funcVSw5
All above with Parameter Name and Value monitors
_funcVSwParM
I also swapped the Interleave and Phase display and physical control order, as they were the reverse of Sonar screen.
I am sure that I have not been as tidy as you, but I was trying..
My next goal would be to allow all the VSw to become ACT Buttons also...
In testing, I see that I have broken something in Sends SE. Mode. Pushing any of VSw 3-5, sends the fader to -Inf or +6.0dB on consecutive presses - probably copied in some settings that I should have copied
In trying to read the preset, I struggle with some of your abbreviations
as in these examples:
(PlugNBu)
(OffPlugBuS)
(PlugNTr)
(OffPlugTrS)
(OffPlugBuM)
(PlugNTr)
(OffPlugTrM)
(OffEQBuS)
Even understanding the Camel case and catching some of the words, I fail to understand their meaning in context.
I think I have to go and reconfigure my ACT learnings for the MCU. I have downloaded the latest controller version and setup Multiple Instances (AZ 01V, and AX MCU) to try and avoid stuffing anything up.. the 01V still appears to be working as per our last efforts, but the MCU PC EQ seems to use the first 4 VPots and Faders and then duplicates them onto the last 4 VPots and faders even have read this thread about the multiple contexts.
Linz.