We know you’re not blaming GP though please understand that if it was a GP issue we would be looking to fix it quickly. You should reach out to the developer of the plugin
I don’t know if this is exactly the same thing…
When I was working on the GP5 set with GPscript to get snapshots (SSs) working/syncing with a MIDI foot controller I had some issues.
As I recall, Helix Native’s factory presets always load SS1 — i.e. they’re all saved with SS1 when created by Line 6. That is a convention but not a necessity. You can save presets with any SS number and it will load correctly as saved. But the SS data is not updated correctly to SS-linked widgets in GP5 when you change presets unless the SS state at the time of change is the same in the new preset as it was when you left the last preset.
I get the impression that Native is dead, unlikely to see any future updates after the arrival of the Stadium hardware, and so I never bothered to follow up with Line 6 on the issue.
My workaround was to manually send CC#69 value 0 with every PC to force the SS to SS1 regardless of the actual saved state. Not ideal but it works.
Helix Native is a great plugin for all its effects and amp options with a no-nonsense GUI but it does have some quirks.
That’s a great workaround. I have decided to forgo native presets and work in the GP layer. So I’m using a combination of GP Presets and GP Variations to do effectively the same thing. Reasoning here is when I recall a GP Preset the plugin knobs snap to the correct position. I don’t change presets often to be honest. Its more when I’m changing whole sounds (Like I have a bass patch with a pitch shifter so my guitar becomes a bass, or I have a mock organ patch). I’ve begged, borrowed, and stole from several others on the forum to come up with something I think is workable.
I also think native is dead development wise. I’m not bothered by it. I would like stadium native if/when they ever release it.