Omnisphere Cutoff parameter resets to previous value on Rackspace activation (despite Reset to 0)

General discussion about Gig Performer
1

Hi everyone,

I am facing an issue with Omnisphere and Gig Performer regarding widget initialization upon rackspace activation.

My Setup:

  • Hardware Controller: Faderfox UC4, with Encoder 1, or more configured in Relative mode (Offset).

  • Plugin: Omnisphere (using Host Automation enabled on the Filter Cutoff parameter).

  • GP Widget: A knob mapped to Omnisphere’s Cutoff.

    • Widget Properties: “Reset on Rackspace Activation” is enabled and set to 0. “Ignore Variations” is also checked. “Sync” is disabled.

The Problem: Every time I activate this specific Rackspace, the Cutoff widget is supposed to reset to 0. However, most of the time, the Cutoff value jumps back to where it was when I previously left the rackspace (e.g., around 50% or 60%), instead of staying at 0.

Has anyone experienced this specific issue with Omnisphere, and is there a way to force Gig Performer’s widget reset to take priority upon activation? What should I do ?

Thanks in advance for your help!

2

Is the widget MIDI mapped to your controller?

3

Can you export the rackspace and upload it?

4

Yes it is !

5

Did you enable “Follow Hardware” in the widget properties?

6

Hi everyone,

I think I managed to fix the issue and wanted to share the solution in case it helps someone else.

The problem wasn’t coming from Gig Performer or Omnisphere directly, but from a “ghost value” (44) stuck inside the memory of my Faderfox UC4 on Encoder 1, which was overriding the widget initialization. Since the encoder was in relative mode, there was no obvious way to reset this internal value from the hardware itself.

How I fixed it:

  1. In Gig Performer’s MIDI widget properties, I temporarily checked the “Sync” option.

  2. I turned the physical encoder on my Faderfox UC4 all the way down until the widget hit 0. (This forced Gig Performer to send a “0” message back to the Faderfox, overwriting its internal ghost memory).

  3. I then unchecked the “Sync” option to go back to my normal relative behavior.

Now, every time I switch rackspaces, the widget correctly stays at 0 without needing any workaround or “Follow Hardware” options. The encoder memory has been successfully cleaned, I hope !

Thanks for your time!

PS : Here’s the rackspace in case you want to see or help me more !

cutoff reset issue resolved?.rackspace (330.2 KB)