EQ Display bug - Draggable Filter Panel....

[Lindon]

There are (I think) a couple of bugs recently(last 3 months) introduced into the draggable filter panel - I'll start with this one . I'm reporting it here just to see if I can get someone to test the same behaviour as I have...

So: A project with a Draggable Filter Panel connected to a parametric EQ.....

Set to save in your preset like this:

Engine.addModuleStateToUserPreset("VoiceEQ1");

Reset the filter panel so the DFP has no nodes in it - so a flat blank line - , save this as Preset called "empty"....

Create another Preset - this time with the DFP active and some nodes in some nice shape of your choosing....save this as a preset called "Full"

OK now load "empty" again..... and the DFP has the same shape as "full" except none of the nodes are displayed.... so its just the bezier curve - the parametric EQ is "flat" like we saved it - but its partner DFP is showing this shape. Click on the DFP and it resets to flat ....

[Lindon]

@Lindon looking at the XML in the prese`t you get this for "Full"

<Processor Type="CurveEq" ID="VoiceEQ1" Bypassed="0" NumFilters="3" Band0="-24.0"
               Band1="393.93310546875" Band2="0.300000011920929" Band3="1.0"
               Band4="1.0" Band5="-24.0" Band6="13723.931640625" Band7="1.0"
               Band8="1.0" Band9="0.0" Band10="-15.42857360839844" Band11="2251.29248046875"
               Band12="1.0" Band13="1.0" Band14="4.0" FFTEnabled="1">
      <ChildProcessors/>

and this in "empty":

<Processor Type="CurveEq" ID="VoiceEQ1" Bypassed="1" NumFilters="0" FFTEnabled="1">
      <ChildProcessors/>

[Lindon]

Anybody tried this? Have the same problem? Anyone?

[orange]

@Lindon I'll try and report back.

[orange]

Confirmed, definitely there has been a glitch. Also it affects the laf elements too.

[orange]

But it doesn't happen when the empty preset has at least one node. So if the empty preset has a node, the glitch is gone.

[Lindon]

@orange Thanks mate - I will log this as a bug...

[Oli Ullmann]

@Lindon The error also occurs in the Parametric EQ's own display. If the module is open and I change presets, the same behavior can be seen. I have to close the module and open it again so that the display shows the correct values.

[clevername27]

@orange Nice-looking interface.

[orange]

@clevername27 said in EQ Display bug - Draggable Filter Panel....:

@orange Nice-looking interface.

Thanks, it's one of our freebies, you can get it from here if you'd like: https://noiseash.com/sweetcase-vintage-electric-piano/

[Oli Ullmann]

Has anyone found a workaround for this problem?

[Lindon]

@Christoph-Hart - any chance of getting this fixed?

[Oli Ullmann]

@Christoph-Hart Yes please. :-)

[Lindon]

@Lindon bump bump...

[clevername27]

@Lindon I swear if I had a magic wand, I'd fix that for you.

[d.healey]

@clevername27 said in EQ Display bug - Draggable Filter Panel....:

@Lindon I swear if I had a magic wand, I'd fix that for you.

What a waste of a superpower.

World peace, nope.
Eternal life, nope.
Cure cancer, nope.

Fix Lindon's bug, check!

[Lindon]

@d-healey said in EQ Display bug - Draggable Filter Panel....:

@clevername27 said in EQ Display bug - Draggable Filter Panel....:

@Lindon I swear if I had a magic wand, I'd fix that for you.

What a waste of a superpower.

World peace, nope.
Eternal life, nope.
Cure cancer, nope.

Fix Lindon's bug, check!

sorry if Im being a pain...Im just getting rained on by a client for this fix...

[clevername27]

@d-healey said in EQ Display bug - Draggable Filter Panel....:

@clevername27 said in EQ Display bug - Draggable Filter Panel....:

@Lindon I swear if I had a magic wand, I'd fix that for you.

What a waste of a superpower.

World peace, nope.
Eternal life, nope.
Cure cancer, nope.

Fix Lindon's bug, check!

Although I did work on a cure for cancer.

EDIT: I failed.

[Oli Ullmann]

Yes, a fix would be really great! :-)

[Goodflow]

Changing HISE/hi_core/hi_modules/effects/fx/CurveEq.h, line 318:

sendOtherChangeMessage(dispatch::library::ProcessorChangeEvent::Preset);

to

sendOtherChangeMessage(dispatch::library::ProcessorChangeEvent::Custom);

Seems to resolve the issue. Not sure if it's a typo or if there's a missing definition for the Preset event, but I haven't found any new problems since making the change.