Paraphonic: strange behaviour changing OSC1
bibenu last edited by bibenu
I found this problem while exploring paraphonic setup. Steps to reproduce.
First, select a new patch, so OSC1 defaults to Sine. Then remove mapping 1 and follow these steps for paraphonic setup.
Then, go to OSC1 and change the type, turning the encoder all the way anti-clockwise to NONE, and then clockwise back to sine.
Result: Paraphony configuration is now broken because
- OSC1 pitch is now set to CTRLR and not CHORD1
- on the mapping for Chord1 to OSC1, the TO.PARAM used to be EXPR, but is now '?'
I found this very confusing, took a while to figure out what had happened. Easy to repair once you know, but it can make exploring different sounds in paraphonic mode a bit tedious.
EDIT: It seems that scrolling through the oscillator types without a pitch (Bow, Wind, Strike, White noise) is what causes the OSC1 pitch to reset.
EDIT 2: It seems that turning the OSC1 type to 'none' is what causes the mapping to reset.
join last edited by
This is exactly the expected behavior. But it's not ideal nonetheless. I'll try to revise the rules so that the pitch and mapping destinations don't reset.
bibenu last edited by
@join re "expected behaviour" yes, I can totally understand how it came about, but as you say, it's not ideal ... particularly with the change in the mapping which is away on another 'screen' you're not looking at. It's a completely unexpected change in the scenario I outlined. I thought that first note in the chord was not being detected and I started messing with keyboard connections, before I discovered the real cause.