Latest News: u-he releases Sugar and Spice for Hive 2
Satin doesn't save group settings on recall (Logic 10.8.1, Sonoma AS)
-
- KVRist
- 111 posts since 10 Mar, 2009 from Australia
Do you want to post your exact steps for this? If so I’ll give it a try.
Not enough time or talent. https://soundcloud.com/user-346125978?r ... rd&p=i&c=0 or https://soundcloud.com/richard-crane-64 ... rd&p=i&c=1
-
- KVRAF
- Topic Starter
- 6525 posts since 17 Dec, 2009
basically i have couple of summing stacks as stems, and Satin on each of them. I assign them all to a common group and name it, and when i close/reopen the project all instances are set to "no group"
-
- KVRist
- 111 posts since 10 Mar, 2009 from Australia
I’m not sophisticated enough to understand that in terms of trying to reproduce I am afraid. How many summing stacks do I need? What plugins, or are they audios, should I put on them? I don’t even know what common groups are or how to assign them.
Not enough time or talent. https://soundcloud.com/user-346125978?r ... rd&p=i&c=0 or https://soundcloud.com/richard-crane-64 ... rd&p=i&c=1
-
- KVRAF
- Topic Starter
- 6525 posts since 17 Dec, 2009
frankly i can't recreate it now either.
group settings are respected in some projects, but in other projects they're not, i don't really understand it.
these are group settings:
You do not have the required permissions to view the files attached to this post.
-
- KVRist
- 111 posts since 10 Mar, 2009 from Australia
@Ploki Corrupt template?
Not enough time or talent. https://soundcloud.com/user-346125978?r ... rd&p=i&c=0 or https://soundcloud.com/richard-crane-64 ... rd&p=i&c=1
-
- KVRAF
- Topic Starter
- 6525 posts since 17 Dec, 2009
-
- KVRer
- 1 posts since 2 Mar, 2024
I have the same problem!
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- 1751 posts since 22 Mar, 2005 from a planet called u-he
Tried closing and reopening a Logic 10.8.1 project containing multiple grouped Satin instances in macOS Sonoma on a Silicon Mac, and it always loaded the group settings and labels correctly.
If you got a project that repeatedly exhibits that issue, please send it to support, so we can check it.
If you got a project that repeatedly exhibits that issue, please send it to support, so we can check it.
That QA guy from planet u-he.
-
- KVRAF
- Topic Starter
- 6525 posts since 17 Dec, 2009
I have 2 or 3 but they're huge - if i try to do the same on an empty project from scratch it just doesn't happen. so weird.tasmaniandevil wrote: ↑Mon Mar 04, 2024 6:22 am Tried closing and reopening a Logic 10.8.1 project containing multiple grouped Satin instances in macOS Sonoma on a Silicon Mac, and it always loaded the group settings and labels correctly.
If you got a project that repeatedly exhibits that issue, please send it to support, so we can check it.
I'll try fiddling with it a bit more to get a consistent way to trigger it
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- 1751 posts since 22 Mar, 2005 from a planet called u-he
Ah, very large projects. That might explain it.
The group parameters are not part of the preset structure.
Their settings are stored together with the project file only.
We call such parameters "instance parameters" because they are saved on a per plugin instance basis within the project file.
Hosts don't seem to have a real concept how to deal with such instance parameters. Thus we had to come up with a way to still reliably load those parameters when a project is being loaded.
We do this with a timer to differentiate between settings that are loaded by the host when a project is being loaded and settings that are loaded when a user selects a preset.
If, during project load, the delay between the loading of the plugin itself and the time at which the host sends the parameter settings to the plugin becomes too large, the timer runs out, and thus the plugin assumes that it must be the user who is loading a preset, and thus ignores the instance parameters.
This used to work fine for many years. But nowadays, projects are getting larger and larger with more and more plugins to load. Hosts might also have changed some details of their plugin loading procedures during project load. Those are factors that might contribute to those instance settings sometimes not being recalled when you load a project.
So far we don't have a cure for this issue.
The group parameters are not part of the preset structure.
Their settings are stored together with the project file only.
We call such parameters "instance parameters" because they are saved on a per plugin instance basis within the project file.
Hosts don't seem to have a real concept how to deal with such instance parameters. Thus we had to come up with a way to still reliably load those parameters when a project is being loaded.
We do this with a timer to differentiate between settings that are loaded by the host when a project is being loaded and settings that are loaded when a user selects a preset.
If, during project load, the delay between the loading of the plugin itself and the time at which the host sends the parameter settings to the plugin becomes too large, the timer runs out, and thus the plugin assumes that it must be the user who is loading a preset, and thus ignores the instance parameters.
This used to work fine for many years. But nowadays, projects are getting larger and larger with more and more plugins to load. Hosts might also have changed some details of their plugin loading procedures during project load. Those are factors that might contribute to those instance settings sometimes not being recalled when you load a project.
So far we don't have a cure for this issue.
That QA guy from planet u-he.
