Page 2 of 2
Posted: Mon Oct 03, 2011 12:01 am
by michelkeijzers
I will do some tests tomorrow on my M50 and hopefully give some help, at least share my experiences.
Posted: Mon Oct 03, 2011 1:09 am
by danatkorg
McHale wrote:I think it has to do with the fact that I have a pedal switch set to Portamento in the Global Settings. ANY value I change it to other than PRG will revert to OFF regardless what it was when you saved it. EVERY combi I've tested it on does it. I can't see this not being a bug.
You mention that your footswitch is momentary.
If the polarity (in Global Controllers) is set to match the switch, that means that it's off in the normal state, and on when you step on it.
In other words, CC#65 is always Off unless you step on the switch.
Step on the switch, and it's On.
When I hook things up this way, and look at the Portamento values in the Combi, they show Off until I step on the switch, and then show the saved values (e.g. 048 as above) when I step on the switch.
If you wanted it to work the opposite way (Portamento On unless you step on the switch), you could swap the polarity for the switch (in Global Controllers).
As far as I can tell, it's working exactly as I'd expect.
- Dan
Posted: Mon Oct 03, 2011 1:54 am
by McHale
danatkorg wrote:You mention that your footswitch is momentary.
If the polarity (in Global Controllers) is set to match the switch, that means that it's off in the normal state, and on when you step on it.
In other words, CC#65 is always Off unless you step on the switch.
Step on the switch, and it's On.
When I hook things up this way, and look at the Portamento values in the Combi, they show Off until I step on the switch, and then show the saved values (e.g. 048 as above) when I step on the switch.
If you wanted it to work the opposite way (Portamento On unless you step on the switch), you could swap the polarity for the switch (in Global Controllers).
As far as I can tell, it's working exactly as I'd expect.
- Dan
It's momentary and normally off. I want portamento off until I step on the pedal. That's a pretty basic function that works as expected in prog mode.
But, you're now starting to see where the problem lies. Because you have the pedal switch set to portamento, it makes the combis set your custom settings to off until you step on it. Now, save your patch with portamento set to 048. Reboot, and now it's set to off even when you step on the pedal. That is not how it's supposed to behave. If it was, you might as well have the settings be PRG or OFF with no over ride.
Again, it works exactly like I want it to after saving the patch... UNTIL I reboot. If it were behaving properly, it would behave the same before and after the reboot.
-Mc
Posted: Mon Oct 03, 2011 10:23 pm
by McHale
Forgot to mention, my Triton, M50, or M3 do NOT behave this way.
-Mc
Posted: Tue Oct 04, 2011 3:46 am
by danatkorg
I've done some testing and filed a bug report. Note that I am using pre-release software, so it's possible that the behavior is different from 1.x. Here's what I've found, assuming that I've put things together properly:
If Assignable Foot Switch is set to Portamento SW
and
Combi (n) uses Timbre overrides for Portamento Time (a numeric value as opposed to PRG)
and
Combi (n) is the Combi initially selected when entering Combi mode (can happen in various ways: when changing from a Program to a Combi in Set List, for instance, or if Memorize is used for startup)
then
Timbre overrides for Portamento Time stay off, and do not respond to the Foot Switch.
If you enter Combi mode, and then select another Combi, the second Combi's Timbre overrides for Portamento will work properly.
If you use the PRG setting instead of a Timbre override, it will work properly.
And, if the Foot Switch is not assigned to Portamento, then the problem doesn't appear.
We'll fix this when possible. In the meantime, if you want to control Portamento from the Foot Switch, I would recommend the workaround of using the PRG settings (with accompanying edits to the Programs, if necessary) instead of the Timbre overrides.
I'm sorry for the inconvenience.
- Dan
Posted: Tue Oct 04, 2011 6:07 am
by McHale
danatkorg wrote:I'm sorry for the inconvenience.
Not a problem! I'm just glad I'm not crazy and you were able to replicate it. I do hope it gets fixed eventually (not necessarily in the next update yet to be released). I reported a bug on the M50 almost as soon as the M50-73 got released and there hasn't been an OS release since and it remains a living bug.
Thanks again Dan for all your testing on this.
-Mike