SCALE_GUI_SIZE bug on Studio One 5 | VST Stuff | Forum

Avatar

Please consider registering
guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed Topic RSS sp_TopicIcon
SCALE_GUI_SIZE bug on Studio One 5
Avatar
Member
Members
June 22, 2021 - 10:52 am
Member Since: June 1, 2021
Forum Posts: 37
sp_UserOfflineSmall Offline

Hi Will,

I can't fix this SCALE_GUI_SIZE issue on Studio One 5. Whatever I try so nothing helped me. The issue is that when I load my plugin on Studio One so it's showing up %10 GUI_size but normally it should load it as the default size right? It doesn't happen on any Steinberg DAWs or AU/AAX... only Studio One 3/4/5 has this issue. 

I can reproduce the same issue with all of books projects too.

Any advice?

Thank you,

Jean

 

// --- BONUS Parameter
// --- SCALE_GUI_SIZE

PluginParameter* piParamBonus = new PluginParameter(SCALE_GUI_SIZE, "GUI_SIZE", "%10, %25, %50, Normal, %150, %200", "Normal");
addPluginParameter(piParamBonus);

Avatar
Admin
June 22, 2021 - 2:48 pm
Member Since: January 29, 2017
Forum Posts: 690
sp_UserOfflineSmall Offline

Yes it should show up as normal. I have not tried S1 in a long time (though it is actually one of my favorites). I will have to look into it, but currently not sure why that would happen. If you leave the SCALE_GUI_SIZE alone (do not implement it) then it is supposed to open at 100% normal size. 

Will 

Avatar
Admin
June 23, 2021 - 3:16 am
Member Since: January 1, 2020
Forum Posts: 103
sp_UserOfflineSmall Offline

This issue has also been affecting VSTHost and SaviHost since at least early last year.

I just spent a little more time on this problem but got nowhere. The menu selection check box also gets set inaccurately to 0 (tiny) on opening each new plugin instance. Strangely no other parameter seems to act in a like way.

Avatar
Admin
June 30, 2021 - 4:37 pm
Member Since: January 29, 2017
Forum Posts: 690
sp_UserOfflineSmall Offline

I am working on ASPiK 1.6.8 right now for VST3 SDK 3.7.2 and will look at this during the release phase to see if I can catch it. There has been a long-standing issue with host calls to the canResize( ) function that are DAW-dependent and I've had to change that code several times in the past. 

Will 

Avatar
Member
Members
September 10, 2021 - 8:29 am
Member Since: June 1, 2021
Forum Posts: 37
sp_UserOfflineSmall Offline

Hi Guys,

Anyone tried to change the GUI_Size on S1? If you have any advice please let me know.

 

Thank you,

Jean

Avatar
Member
Members
September 12, 2021 - 6:22 pm
Member Since: June 1, 2021
Forum Posts: 37
sp_UserOfflineSmall Offline

jeanlecode said
Hi Guys,

Anyone tried to change the GUI_Size on S1? If you have any advice please let me know.

 

Thank you,

Jean  

no one has this issue? Embarassed

Avatar
Admin
September 21, 2021 - 9:42 am
Member Since: January 1, 2020
Forum Posts: 103
sp_UserOfflineSmall Offline

Hi Jean,

I just made some headway on this. The problem at least doesn't seem to be specific to any part of the SCALE_GUI_SIZE function which all works fine.

Rather I think their is a bug in how the kTypedEnumStringList control variable type is initialized. I haven't traced the real root of the problem though, seems strange to be DAW specific. But if I'm right then any string list enumerated parameter will fail to initialise correctly in S1. At least that seems to be the case for VST/SaviHost over here.

For now you could try not using that control type by setting

PluginParameter* piParamBonus = new PluginParameter(SCALE_GUI_SIZE, "size", "%", controlVariableType::kInt, 0, 5, 3, taper::kLinearTaper);

 

Downside is you've now lost names for each menu entries. So you could use a slider instead or create a custom menu object with overwritten name entries.

Let me know if that works for you in S1.

Avatar
Admin
September 21, 2021 - 9:43 am
Member Since: January 1, 2020
Forum Posts: 103
sp_UserOfflineSmall Offline

Hi Jean,

I just made some headway on this. The problem at least doesn't seem to be specific to any part of the SCALE_GUI_SIZE function which all works fine.

Rather I think there is a bug in how the kTypedEnumStringList control variable type is initialized. I haven't traced the real root of the problem though, seems strange to be DAW specific. But if I'm right then any string list enumerated parameter will fail to initialise correctly in S1. At least that seems to be the case for VST/SaviHost over here.

For now you could try avoiding that control type by setting

PluginParameter* piParamBonus = new PluginParameter(SCALE_GUI_SIZE, "size", "%", controlVariableType::kInt, 0, 5, 3, taper::kLinearTaper);

 

Downside is you've now lost names for each menu entry. So you could use a slider instead or create a custom menu object with overwritten name entries.

Let me know if that works for you in S1.

Cheers

Avatar
Member
Members
September 24, 2021 - 7:12 pm
Member Since: June 1, 2021
Forum Posts: 37
sp_UserOfflineSmall Offline

jim said
Hi Jean,

I just made some headway on this. The problem at least doesn't seem to be specific to any part of the SCALE_GUI_SIZE function which all works fine.

Rather I think there is a bug in how the kTypedEnumStringList control variable type is initialized. I haven't traced the real root of the problem though, seems strange to be DAW specific. But if I'm right then any string list enumerated parameter will fail to initialise correctly in S1. At least that seems to be the case for VST/SaviHost over here.

For now you could try avoiding that control type by setting

PluginParameter* piParamBonus = new PluginParameter(SCALE_GUI_SIZE, "size", "%", controlVariableType::kInt, 0, 5, 3, taper::kLinearTaper);

 

Downside is you've now lost names for each menu entry. So you could use a slider instead or create a custom menu object with overwritten name entries.

Let me know if that works for you in S1.

Cheers  

Hi Jim,

Thanks for the help.

Unfortunately it doesn't fix the issue. I added a custom menu object and tried everything but it's still there the issue.

PluginParameter* piParamBonus = new PluginParameter(SCALE_GUI_SIZE, "SIZE", "A, B, C, Normal, D, E", controlVariableType::kInt, 0, 5, 3, taper::kLinearTaper);
addPluginParameter(piParamBonus);

Thank you,

jean

Avatar
Admin
September 26, 2021 - 11:22 am
Member Since: January 1, 2020
Forum Posts: 103
sp_UserOfflineSmall Offline

Further mystery then. Unless you hadn't initialized the slider correctly in the VST GUI editor? Maybe try deleting the menu controls and just try it with a fader.

Else,

Do you receive a build output in xcode? It's a bunch of text that tells when you've successfully compiled in VStudio.

Check these lines that come before the validitors output, to see if the plug is being built with the correct initialized value.

1>[Scan Parameters]
1>Info: ===Scan Parameters ====================================
1>Info: This component exports 142 parameter(s)

...

1>Info: Parameter 010 (id=131077): [title="SIZE"] [unit="A, B, C, Normal, D, E"] [type = F, default = 0.600000, unit = 0]

Here 0.6 is the correct value of 3 normalized to 1.

 

I attempted to try this out on Studio One but unfortunately Presonus have dropped Win7 support and I'm unable to run the installer.

Avatar
Member
Members
September 27, 2021 - 4:47 pm
Member Since: June 1, 2021
Forum Posts: 37
sp_UserOfflineSmall Offline

jim said
Further mystery then. Unless you hadn't initialized the slider correctly in the VST GUI editor? Maybe try deleting the menu controls and just try it with a fader.

Else,

Do you receive a build output in xcode? It's a bunch of text that tells when you've successfully compiled in VStudio.

Check these lines that come before the validitors output, to see if the plug is being built with the correct initialized value.

1>[Scan Parameters]
1>Info: ===Scan Parameters ====================================
1>Info: This component exports 142 parameter(s)

...

1>Info: Parameter 010 (id=131077): [title="SIZE"] [unit="A, B, C, Normal, D, E"] [type = F, default = 0.600000, unit = 0]

Here 0.6 is the correct value of 3 normalized to 1.

 

I attempted to try this out on Studio One but unfortunately Presonus have dropped Win7 support and I'm unable to run the installer.  

Thanks Jim.

I'll have a look on this later and keep you informed.

Jean

Forum Timezone: America/New_York

Most Users Ever Online: 152

Currently Online:
5 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

Chaes: 56

Skyler: 48

StevieD: 46

Derek: 46

Frodson: 45

Peter: 43

TheSmile: 43

Nickolai: 43

clau_ste: 39

jeanlecode: 37

Member Stats:

Guest Posters: 1

Members: 775

Moderators: 1

Admins: 6

Forum Stats:

Groups: 13

Forums: 42

Topics: 846

Posts: 3353

Moderators: W Pirkle: 690