Satin in Ableton: Loading additional instance clears Group Names

[mholloway]

Hi Guys.

I'm using Satin (current version) in Ableton Live 9.6.2, and I have a minor problem.

1.) Load one instance Satin, create a Group, name the group, apply various settings.

2.) Load an additional instance of Satin; Group name disappears from both first instance and new instance; notably, the -settings- for the group remain the same, but the name gets cleared.

I know this isn't the intended behavior, so I thought I'd mention it here and see if anyone else is having this problem as well.

thanks!

-Michael H.

[tasmaniandevil]

Just a shot in the dark, but in Reaper there is an option to save a plugin with a self-created default preset, so that when loading a new instance of the plugin, it will already have these settings. But when using this feature with Satin, Reaper saves not only the settings that are normally saved inside a Satin preset, but also the names of the groups. And the next time you load a new instance, it will shout out to the other Satin instances: 'Hey look, here are new group names for you.' And it will force all other plugins to synchronize to the same group names as the newly loaded instance (and if those group names were empty, all other instances will take over the empty names).

I don't know very much about Ableton Live. Is there maybe a similar option in Live, i.e. a way to save a plugin with some sort of default preset? And are you by any chance using such a feature?
That's the only way I know that can lead to this kind of behavior.