Bug? Omnisphere Live Mode Patch Persist not working with variations

General discussion about Gig Performer
1

Hi,

im trying to figure out if I’m doing something wrong or there is a GP or Omni Bug:
I overall followed this guide.

I have two Variations:

  • Variation A with Layers 1, 2 and 3 enabled
  • Variation B with Layers 1 and 2 enabled

When I go from B to A with some persisting notes, all notes are muted, no Patch Persistance.
Even more weird: When I go from B to A, only Layer 3 persists.
This behavior does NOT happen when I manually switch the layers on/off from widgets - just when doing it via variation switch.

Anybody got an idea?

Attached the rackspace; look at variations “Cathedral Strings + Pad” (B) and “Cathedral Strings + Pad + Choir” (A).
Omnisphere Pads.rackspace (281.9 KB)

2

Patch Persistence is designed for switching between rackspaces.
Are you switching between rackspace variations?

3

I should have clarified:
I mean the patch persistance that Omnisphere Live Mode has built-in (switching between layers by mouse or by GP widgets has patch persistance).

My guess is that GP must do something other than just giving out host automation parameters when switching variations…

4

Please connect a MIDI monitor plugin after your MIDI In Plugin which is connected to OMNISPHERE in parallel to OMNISPHERE.
Can you see messages when you switch variations?

When you see message then delete the MIDI In plugin and include it again, connect to OMNISPHERE and the MIDI monitor.

Now this messages should not appear anymore.

1 Like
5

Absolutly right, that solved it :slight_smile:
What was the error? Did I setup something wrong?

6

No clue, I just tried to find a solution :wink:

1 Like
7

Did you build this rackspace with Version 4 of GP or is it migrated from V3 of Gig Performer?

8

Bildschirmfoto 2024-02-28 um 8.00.33 AM
Bildschirmfoto 2024-02-28 um 8.00.33 AM1882×1554 114 KB

I found the root cause

With this mapped widget the transpose of the MIDI In Block is changed.
An each change of the transpose forces reset messages sent from the plugin.

3 Likes
9

I did indeed!

Hmmm, yeah, I just noticed that the fix destroyed the octave change and the problem returned when I fixed it.

Maybe it would be an enhancement to gig performer to have this behavior only when the transpose is actually changed between variations?

1 Like
10

Excellent idea – just implemented this (a one line change) so it will be in the next release!

3 Likes