XOR Userforum

Full Version: [FIXED] DualChord Patch BASE NOTE / KILL NOTE bug
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
NerdSEQ: Firmware V2.02A
DualChord: Firmware V1.2
3 NSA Expanders: NSA1 More Triggers, NSA2 CV16, NSA3 Dual Chord
1 2HP Midi Expander

Steps to reproduce:
1. Open new project and assign the DualChord expander to a track w/TRACK ASSIGN
2. Create new pattern on DualChord track
3. Create new patch 00 on row 00 and set various mix values for sine, triangle, pulse, and saw waves 1, 2, 3, 4
4. Add some notes to row 00 so you can hear the DualChord and hit Play.
5. Create a new patch 01 on row 08 and set various mix values again for sine, triangle, pulse, and saw waves 1, 2, 3, 4
6. At some point, you may hear the DualChord stop playback.  If not, repeat step 5 with a new patch until you hear the sound start/stop.
7. When you're hearing the start/stop, scroll down to the last page of the patch where the stop is happening and you'll see values added to BASE NOTE and KILL NOTE that you didn't add.  If you manually delete those values, the sound comes back as expected.

The bug is those BASE NOTE + KILL NOTE values intermittently being added to existing DualChord patches as new patches are created and modified.

In my tests, sometimes the BASE NOTE + KILL NOTE gets added right as I start editing patch 01, but other times I'm able to repeat the process through patch 03 or 04 before it happens.

Here's a video of it happening.  If needed, I can make another video showing the same end result.  https://youtu.be/5pFS8g5AXvY
I just tested this in NerdSEQ Firmware V3.0.0 and this bug isn't happening for me anymore.
Yes I know :-)

Quote:- reduced amount of patches and increased amount of patch rows (fixes dualchord patch bug)
For sure! I was just closing out the thread for future readers. Thanks for everything you do!