10-02-2025, 11:35 AM
(This post was last modified: 10-02-2025, 11:43 AM by beep.et.cetera.
Edit Reason: Adding info.
)
Hi
I've mapped out envelope sustain and volume on my Assimil8or using the MIDI IN to send CC via the mapping screen.
I've found a sporadically replicable issue, where hitting min or max value on specific CC channels, will set a CC value to another CC channel. Practically, this means that maxing out a fader, will open up the volume of a different channel, causing ruckus in a otherwise quiet part of the set.
There's a pattern to the issue, in which a specific channel will affect another specific channel. It adds a specific value to different channels (ie. CC33 will be set to a value between 0830 and 0930).
So far, affected channels are CC24 CC32 CC33 and CC36. I'm still trying to figure out which are affecting which. So far CC29 has a ~30% chance of affecting CC24 if maxed out, judging by observation. CC24 is mapped to the CV16 EV4R, which will open the envelope in crucial performance situations
I have tested my controller (Faderfox MX12) using MIDI-OX, which shows no sign of cross-affecting values. I initially met the problem in 2.02A, but it still persists in 3.00.
Also: I found it hard to place this between "less important glitches/bugs" and "really bad bugs", since there's not crash. But since this is a crucial part of my live setup, it's more than a QoL issue, as it makes the NerdSeq problematic to use in a professional setting. Would you consider this less important? Just checking, because I want to put it in the right subforum, and it's good to know for future reference.
I will make a dump from the MIDI OUT when I get to work in 40 mins. I attached the project and mappings.
Let me know if you need anything else.
Cheers, and congratulations on the new update!
/beep
PS: I suspected some NRPN tomfoolery, but I don't have the knowledge to single anything out.
I've mapped out envelope sustain and volume on my Assimil8or using the MIDI IN to send CC via the mapping screen.
I've found a sporadically replicable issue, where hitting min or max value on specific CC channels, will set a CC value to another CC channel. Practically, this means that maxing out a fader, will open up the volume of a different channel, causing ruckus in a otherwise quiet part of the set.
There's a pattern to the issue, in which a specific channel will affect another specific channel. It adds a specific value to different channels (ie. CC33 will be set to a value between 0830 and 0930).
So far, affected channels are CC24 CC32 CC33 and CC36. I'm still trying to figure out which are affecting which. So far CC29 has a ~30% chance of affecting CC24 if maxed out, judging by observation. CC24 is mapped to the CV16 EV4R, which will open the envelope in crucial performance situations
I have tested my controller (Faderfox MX12) using MIDI-OX, which shows no sign of cross-affecting values. I initially met the problem in 2.02A, but it still persists in 3.00.
Also: I found it hard to place this between "less important glitches/bugs" and "really bad bugs", since there's not crash. But since this is a crucial part of my live setup, it's more than a QoL issue, as it makes the NerdSeq problematic to use in a professional setting. Would you consider this less important? Just checking, because I want to put it in the right subforum, and it's good to know for future reference.
I will make a dump from the MIDI OUT when I get to work in 40 mins. I attached the project and mappings.
Let me know if you need anything else.
Cheers, and congratulations on the new update!
/beep
PS: I suspected some NRPN tomfoolery, but I don't have the knowledge to single anything out.