It seems that since updating to the 1.2 firmware I’ve lost the ability to program a modulation destination by depressing and holding the MOD2 DEST button then selecting a destination by turning a control (Filter Cutoff for example).
I was able to do this with firmware version 1.1 but have not tried it until recently (since the firmware 1.2 and Editor 1.0 release) so I don’t know at what point it stopped working.
I can still select MOD Destinations through the menu system but holding the button down and selecting a control was much slicker and quicker.
Checked out both threads, then downgraded to 1.1.0, checked the behavior, upgraded again to 1.2.0 and checked the behavior once again.
For me it works similarly in both versions:
Push a MOD DEST button (either 1 or 2), and while holding it rotate a destination knob. If it is any of the parameters for which there’s a dedicated state LED for MOD DEST on the panel (Noise Level, LFO Rate, OSC Wave etc.), the state will change to that position and the corresponding LED will light up. If it’s not (for example OSC1 Level), the EG TIME/PGM LED will light up, and PGM DEST for the specific MOD BUS will be set to that destination.
If you repeat this scenario while the CONTROLLERS button is ON, and on the main LCD you switch to page 2 of the MOD BUS menu, you can see the PGM DEST field changes according to the selected/rotated knob.
What is the change in behavior you are experiencing between 1.1.0 and 1.2.0 ?
Thanks for the info Gil. I tested it again and it worked as you described.
With the 1.1 version of the firmware if You held the MOD button down when EG TIME/PGM was selected the LED stayed on until you selected a knob for the destination. Then the LED would go out until you released the button at which point it would light again and your destination would be set.
Now it seems that you just hold it down, turn a destination knob and when you release it EG TIME/PGM illuminates. Either way the result is the same but the change confused me until I just tried holding the button down despite the different LED display.
I tried downgrading to 1.1 and the process failed and semi-bricked my Sub 37. It came on, the screen was blank, all the LEDs were on but nothing worked. I tried the 1.1 install a couple of times and while it said it was installing and that the install was complete the same thing happened (no screen, all LEDS on, etc…)
I ran the 1.2 update and it seemed to un-brick the Sub 37. I noticed, however, that while my presets in bank 1 were still there, they didn’t sound right. Fortunately I backed them up with Sysex before starting this whole process. I have some stuff to do tonight so I can’t work on it now but I intend to try the reversion to 1.1 again tomorrow.
As ObtuseMoose points out, when you map the Filter Cutoff with this method it doesn’t work, and it might be related to the fact that this destination has its own dedicated knob. However, some of the other destinations like the Noise Level do work in this fashion. I find this rather confusing.
Additionally, if you assign a destination which is not shown on the panel, the only way to know which one is it is by ear, or is there a menu in the display I am missing which shows this?
In v1.1.0 there was an bug, and destination was wrongly set to Ratchet if you pushed the PGM button and rotated Cutoff. Cutoff is not really a valid destination (there’s a dedicated parameter for FILTER AMT in Mod 1/2), therefore this combination has been removed in v1.2.0
Turn a CONTROLLERS button ON, and on the main LCD switch to page 2 of the MOD BUS menu. You should be able to see the PGM DEST field changes according to the rotated/selected destination parameter.