Dune 2 - Filter resets

[Teksonik]

after assigning the cutoff to my Drehbank I tweaked, then double clicked stop and.......wa la.......magically reset the cutoff.

So it does appear to be related to Midi CC assignment..... What CC # was your Drehbank sending ? Did you use D2's Midi Learn or Orion's Link to Next Midi Controller ?

As you can see in the screenshot I posted earlier if your controller is sending CC # 120 or 123, double clicking Orion's stop button will set anything assigned to receive that CC # to Zero.

[ufo]

Sorry, here is the spec:
Pentium Q6600 running Windows XP SP3
Orion 8.5
Last releaser of Dune
Dune 2 2.07 (I think, cant really tell from account)

And no, cc assignment is irrelevant. New instance of everything, panic and cutoff resets to zero.

Trippy.

[Marcin]

Does it help if you click "Midi Forget" in DUNE 2 on the filter's control?

[Teksonik]

And no, cc assignment is irrelevant. New instance of everything, panic and cutoff resets to zero.
Trippy.

As Marcin has suggested D2 remembers it's Midi Learn assignments....even with a new instance of everything so no it's not irrelevant. Once again here is the clue:

after assigning the cutoff to my Drehbank I tweaked, then double clicked stop and.......wa la.......magically reset the cutoff.

[Marcin]

Once again here is the clue:

after assigning the cutoff to my Drehbank I tweaked, then double clicked stop and.......wa la.......magically reset the cutoff.

That's why I asked for "Midi Forget". After "Midi Learn" DUNE 2 is waiting for Midi data, and DUNE 2 has got "double click on stop", instead of midi data (DUNE 2 in Orion must be set to the CC Mode to handle CC assignments properly, and not the VST Parameter mode).

[Kriminal]

confirmed bug here

new project
insert dune
switch to midi cc
switch to song mode
press play
double click stop
cut off goes to zero

no controllers connected at all

orioin/dune 64bit

[Marcin]

confirmed bug here

Please right-click and use "MIDI Forget". Does it remove the problem?

[Kriminal]

confirmed bug here

Please right-click and use "MIDI Forget". Does it remove the problem?

yes it does, but as i have never used a controller to do anything except play keys in D2, its not 'remembering' an old assignment. That is to say, i have never used 'midi learn' or 'link to next controller' in D2 (as you know, i did virtually zero testing and i dont even use it these days)

[Steven_Blair]

So MIDI forget fixes the problem?

[Kriminal]

So MIDI forget fixes the problem?

Yes, but you shouldnt need to do it in the first place, so its def a bug.

[Steven_Blair]

Agreed, but its been really annoying me for a while so this helps a lot.

[Steven_Blair]

Great news, it worked for me!

[Teksonik]

confirmed bug here

new project
insert dune
switch to midi cc
switch to song mode
press play
double click stop
cut off goes to zero

no controllers connected at all

orioin/dune 64bit

Not confirmed here. Even on my laptop which has never had a controller connected to it.......(Win 8.1 64 Bit)

Try this....Load Orion, Load D2. Right Click the ADSR Release knob and select Midi Learn. Double Click the Stop Button. Close Orion then reopen it and reload D2. Double Click the Stop button and the Release Knob will set to Zero. Right Click the Release Knob and select Midi Forget, Click and then Double Click the Stop Button. Release Knob no longer resets to Zero.

What's one of the most common parameters people choose to control with a Midi Controller ? Filter Cutoff.........

[Kriminal]

I dont understand what you are getting at....?

I didnt midi learn anything to start with....

its a bug that needs looking at for sure.

[Teksonik]

What I'm getting at is it's possible that people who are experiencing this issue might have unintentionally clicked midi learn on the cutoff at some point but didn't actually assign a CC#. Then when they double clicked Stop it automatically assigned CC# 120 or 123 to the cutoff. The fact that selecting Midi Forget fixes the issue is a big clue.

I'm also willing to entertain the possibility that somehow the cutoff knob for some reason went in to midi learn mode without anyone actually selecting learn which would be a bug. But then why only the Cutoff knob ?

Anyway I can't reproduce the cutoff issue on any of my three systems but I am able to assign CC# 120 to a parameter by taking the steps above and I can reproduce that every time.

So while it may well be a bug I am unable to confirm or reproduce it here........if I could I would certainly report those results as well.