Audiority plugin values not saved

General discussion about Gig Performer
1

Yes I’m cribbing this from the UA plugin thread earlier in the year as it seems very similar.

-I create a simple Rackspace using a VST3 Audiority plugin (Deleight and Chief Chorus for example) and a Valhalla Supermassive plugin.

-I change some settings on each plugin

-I save and exit

-Upon restart only the Valhalla settings are retained. The Audiority plugins always revert to the 00 Factory Init settings even if I save my plugin settings to a preset within the plugin.

I have also tried Soundtoys and IK’s Tonex plugin: these work fine.

Any ideas?

2

And when you try the VST version or AU version (if you are on a Mac)?

3

Ah, forum rookie mistake on my part. I’m on PC.

4

If you map the settings you are wanting to change to widgets, save and then reload, does the plugin load with the correct settings then? There are a few other plugins mentioned in the forum that have issues similar to this, and mapping the controls to widgets worked.

5

Are you using widgets?

6

This is nothing to do with widgets - it’s a question of how the plugin state is being handled by the plugin

7

I’m not using widgets. I shall try the Audiority plugins with widgets tomorrow and report back.

8

I am getting this issue on the VST3 version of Chief Chorus and another Audiority plugin that I own. But the VST3 recalls its setting correctly in Reaper and Blue Cat PatchWork. So it’s only GP that I am getting this issue.

The VST and AU plugin versions work fine in GP. @HeartfeltDawn I assume you are using VST3? Can you try the VST version.

1 Like
9

Following rank13’s post, I installed the VST2 version of Chief Chorus onto my PC.

The VST2 plugin does recall its setting correctly in GP.

The VST3 version does not.

I then installed the VST2 version of Deleight.

The VST2 plugin does recall its setting correctly in GP.

The VST3 version does not.

I dropped in a couple of widgets controlling bypass on/off for the VST3 versions of Chief and Deleight to see if this would affect the non-recall of settings issue. After restarting GP, I can report that it did not affect it. Settings on the VST3 versions were not recalled.

End result: there’s a problem with VST3 versions of Audiority plugins.

10

I’ve contacted their developer. It’s strange that I couldn’t replicate the issue in another host though.

11

Same here, dropped an email to Audiority yesterday.

12

Actually, we think this may be an issue in GP …. we are looking to see if we can do a hot fix in the near future to address it.

4 Likes
13

Thank you, that would be fantastic as I use a lot of Audiority plugins and I’m moving over to a hybrid pedals + GP guitar setup over the next few months :slight_smile:

14

We will do our best.

4 Likes
15

At least the standard VST version works. A number of users here tend to favor these over VST3, as often they are more stable and have less issues.

3 Likes