NS4 OS v1.46 bug - Flanger becomes non-functional on sections

[WannitBBBad]

I submitted the following to Nord Support today and entered it in the Google sheet NS4 Issues/Bugs List. The Flanger effect on Piano B becomes non-functional with program reload (other MOD 2 effects will work but the flanger is dead). The flanger becomes functional again with the next program reload. The flanger became disabled at other times while editing a program but it was difficult to recreate.

TEST 1: Set up a new program, initialize ALL, then set up Piano B only with the flanger effect. Save the test program. Turn off your NS4 and then turn it back on. Press the test program button to toggle back and forth between the flanger being on and being non-functional (other Mod 2 effects work, flanger is dead). Moving to any other program with flanger on Piano B will yield the same result.

TEST 2: Move to any program without the flanger on Piano B. Turn off the NS4 and then turn it back on. Move to the test program. The flanger works fine on Piano B.

[Nordlicht]

I have just checked it a couple of times at my NS4C (v1.44), but was not able to reproduce this bug.
The flanger was always working. I tried both grouped FX (A+B) and individual FX (only B).

Strange...

[WannitBBBad]

I have just checked it a couple of times at my NS4C (v1.44), but was not able to reproduce this bug.
The flanger was always working. I tried both grouped FX (A+B) and individual FX (only B).

Strange...

Thanks, I saved the program and will post it. The effect was individual on B as I was working on "Peg" with a phase shifter on the Rhodes on A. I'll dig a little further.

[Nordlicht]

Now I noticed the bug, too!
I have switched the instrument off for an hour and wanted now to play again.
Checked again the test program, and it behaves exactly as you write.
And it’s really only the flanger.

[WannitBBBad]

Now I noticed the bug, too!
I have switched the instrument off for an hour and wanted now to play again.
Checked again the test program, and it behaves exactly as you write.
And it’s really only the flanger.

You found another piece to the puzzle. I started my NS4 with a different program that didn't use the flanger and then went to "Peg" and my test programs to find that they worked fine. I turned my NS4 off and back on with the test program and the bug was there again. I revised the tests above with the additional information. Thanks!

[taxman]

Bug still present in OS v1.46. Nord Support in the U.S.A. has forwarded it to the folks at Clavia.

[WannitBBBad]

I found this morning that the flanger bug isn't just on the Piano B flanger, and that the bug only appears if the NS4 loads a program with the flanger active. After booting up, pressing the program button will alternate between whether the flanger is on or not, AND the bug appears on any other program brought up after that with a flanger used in the same sections as the program that loaded upon booting. If the program has a flanger used in just the piano section, the synth and organ flangers will turn on and work fine; other programs brought up will only have the problem in the Piano section. If flanger settings are saved in both the piano and synth sections, booting up with that program will affect both sections and any other programs moved to with flanger settings in either section and pressing the program button will alternate between flanger being on or off. I'm checking with Nord Support to see if there's any progress. Cheers!

Update: This fix will be included in the next OS update soon to be released.