It is by design (EARevolve works the same way).
The "interface size" is a parameter (default value = 100%) which is saved with DAW projects.
Therefore, it is a per instance parameter.
When inserting a new instance, the GUI size is always 100%, but when reloading a project (or closing/reopening the GUI), each instance remembers its size.
eaReckon - EAReverb 2
-
- KVRAF
- 6039 posts since 8 Jul, 2009
I am not fond of this appraoch. I must prefer the more ubiquitous "set a UI size and all subsqeuent instantiations adopt that size". It's extra work to always have to set the UI size when opening a plugin. The use-case is fairly obvious: a user will typically want to use a UI at the same size across projects. Why would they always want to start at 100% if they dont typically use 100%.PFozz wrote: ↑Sun Aug 21, 2022 11:21 am It is by design (EARevolve works the same way).
The "interface size" is a parameter (default value = 100%) which is saved with DAW projects.
Therefore, it is a per instance parameter.
When inserting a new instance, the GUI size is always 100%, but when reloading a project (or closing/reopening the GUI), each instance remembers its size.
#NONFR Check out my music at Bandcamp 
Free Streaming!
Free music with your support on Patreon | Youtube: Music of Plexus Videos (music videos) | Youtube: Plexus Productions (audio related) Stop whining. Make music.
Free Streaming! Free music with your support on Patreon | Youtube: Music of Plexus Videos (music videos) | Youtube: Plexus Productions (audio related) Stop whining. Make music.
-
- KVRist
- 341 posts since 30 Apr, 2004 from France
I like to quickly check what happens in different plugins (movement in EARevolve, analyzers, ...) and like to display several of them on my secondary screen.
In this case, I want small enough "blocks".
When I need to spend some time tuning an instance, having it temporarily larger may be convenient until I set it back to a smaller size.
I don't want to get this layout changing when reloading a project or reopening a closed GUI.
For example, in my situation (QHD Main screen : DAW / FHD Secondary screen : Plugins and other things), it would be a pain to get all my instances at x2 when opening a project just because I wanted one of them larger at the end of the previous session.
I understand it does not make sense when a DAW shows only one plugin at a time or if you want all the instances at x2 whatever the situation, for example, but it is important for me (as a user of my own things) to get it working that way.
This is why I wanted it to be a per instance parameter (saved with DAW projects) and not a global setting.
We could think about a global setting that stores the last selected size to be applied to next inserted instances only.
I thought about it... but some formats may not pass validation tools (now or later) :
- if the default value of a parameter is not applied when the plugin is opened ; or
- if this parameter is changing, later, during the validation process, without any GUI manipulation.
+ depending on the context, if the validation tool randomly tests parameters, it could "accidentally" set the GUI size to x0.5 (even if the GUI is not opened).
- etc...
... and I still want to retrieve my plugins displayed as I want when reopening a project (with different sizes if this is what I want).
+ I like to get new instances at x1 (but this is just my preference - applying the two clicks, if needed, is easier for me at x1 than at x2 if the window is partially out of boundaries or at x0.5 which is very small).
Again, I understand your point (especially if your DAW displays only one plugin at a time), but changing this would be risky (parameter + saving the last selected size) or it would not suit my needs as a user (global setting), which would be ironic :--)
This is why I don't plan to modify this.
In this case, I want small enough "blocks".
When I need to spend some time tuning an instance, having it temporarily larger may be convenient until I set it back to a smaller size.
I don't want to get this layout changing when reloading a project or reopening a closed GUI.
For example, in my situation (QHD Main screen : DAW / FHD Secondary screen : Plugins and other things), it would be a pain to get all my instances at x2 when opening a project just because I wanted one of them larger at the end of the previous session.
I understand it does not make sense when a DAW shows only one plugin at a time or if you want all the instances at x2 whatever the situation, for example, but it is important for me (as a user of my own things) to get it working that way.
This is why I wanted it to be a per instance parameter (saved with DAW projects) and not a global setting.
We could think about a global setting that stores the last selected size to be applied to next inserted instances only.
I thought about it... but some formats may not pass validation tools (now or later) :
- if the default value of a parameter is not applied when the plugin is opened ; or
- if this parameter is changing, later, during the validation process, without any GUI manipulation.
+ depending on the context, if the validation tool randomly tests parameters, it could "accidentally" set the GUI size to x0.5 (even if the GUI is not opened).
- etc...
... and I still want to retrieve my plugins displayed as I want when reopening a project (with different sizes if this is what I want).
+ I like to get new instances at x1 (but this is just my preference - applying the two clicks, if needed, is easier for me at x1 than at x2 if the window is partially out of boundaries or at x0.5 which is very small).
Again, I understand your point (especially if your DAW displays only one plugin at a time), but changing this would be risky (parameter + saving the last selected size) or it would not suit my needs as a user (global setting), which would be ironic :--)
This is why I don't plan to modify this.
-
- KVRist
- 341 posts since 30 Apr, 2004 from France
As an illustration, when I want this on my secondary screen...
... I don't want to get the following when reopening the project (after x2 has been selected in another project) :
... I don't want to get the following when reopening the project (after x2 has been selected in another project) :
-
- KVRAF
- 6039 posts since 8 Jul, 2009
Sure. Be annoying. I know I will be every time I open your plugins and they size differently than my others.... alas. paid users be damned, as long as it works for the dev's workflow...
Last edited by plexuss on Tue Aug 23, 2022 9:14 am, edited 1 time in total.
#NONFR Check out my music at Bandcamp Free Streaming!
Free music with your support on Patreon | Youtube: Music of Plexus Videos (music videos) | Youtube: Plexus Productions (audio related) Stop whining. Make music.
Free Streaming! Free music with your support on Patreon | Youtube: Music of Plexus Videos (music videos) | Youtube: Plexus Productions (audio related) Stop whining. Make music.
-
- KVRAF
- 5526 posts since 15 Dec, 2011 from Bucharest, Romania
I think that adding an option to have a default global size as other developers did would make a lot of sense. You can continue to use your plugins the way you do and we, the rest, will have a bigger size that doesn't reset.
Examples:
Examples:
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- 6854 posts since 28 Apr, 2004 from france
+1
(and thank you a lot for the update !
)-
- KVRist
- 341 posts since 30 Apr, 2004 from France
Thanks for your kind words, sinkmusic
e@rs, an option would be nice, indeed.
Those who like how it currently works (I'm not alone in this situation) will not be disturbed and I understand why having a "global" mode would be interesting in various contexts.
I will have to think twice about it as I don't want to break user projects nor to get a potential validation issue.
I cannot promise anything but I have an idea that may work. All of this will probably take time, though.
-
- KVRist
- 341 posts since 30 Apr, 2004 from France
It is a tiny brighter spot on the 2x version of the (textured) background picture.
I darkened it a bit and a new picture is ready to replace the current one in the next update (which will be released when more significant things are added).
-
- KVRist
- 341 posts since 30 Apr, 2004 from France
-
- KVRAF
- 5526 posts since 15 Dec, 2011 from Bucharest, Romania
Version 2.2.1 changelog:
Improvements:
AAX : Native Apple Silicon support.
Improved “GUI Size” control: “Global’ and “Per instance” modes.
In “Global” mode, all instances have the same size (system-wide). The “global” size can be set at any time, from any instance and from any DAW, regardless of the format (AAX, AU, VST2, VST3).
Compatibility:
macOS 10.9 (minimum) up to macOS 14 are supported. 64-bit only.
Version 2.1.0 (32/64-bit) of the plugin is the last version to support macOS 10.6, 10.7 and 10.8 (up to 10.14).
Windows 10 and Windows 11.
Improvements:
AAX : Native Apple Silicon support.
Improved “GUI Size” control: “Global’ and “Per instance” modes.
In “Global” mode, all instances have the same size (system-wide). The “global” size can be set at any time, from any instance and from any DAW, regardless of the format (AAX, AU, VST2, VST3).
Compatibility:
macOS 10.9 (minimum) up to macOS 14 are supported. 64-bit only.
Version 2.1.0 (32/64-bit) of the plugin is the last version to support macOS 10.6, 10.7 and 10.8 (up to 10.14).
Windows 10 and Windows 11.
-
- KVRAF
- 6854 posts since 28 Apr, 2004 from france
Agreed
