Initial loading values of GUI elements in aax when plugin is opened....

[Dan Korneff]

@ustk said in Initial loading values of GUI elements in aax when plugin is opened....:

@dustbro Strange... Are they saveInPreset:Enabled?
What about other formats (VST, AU)?

saveinPreset is Enabled. I'm just now noticing that the controls loading properly have been linked to processors thru the Interface Property Editor. The buttons in question have been scripted.
I'm gonna try this and see what happens

.set("defaultValue", 1);

[Dan Korneff]

Doesn't seem to work.
@Christoph-Hart any tricks to get a button to default ON in protools? I've scripted the defaultValue, but it still initialized as OFF.

[d.healey]

@dustbro button.setValue(1);

[Dan Korneff]

@d-healey That doesn't work either.

[Dan Korneff]

@d-healey I was calling this after declaring the variable. It doesn't seem to affect the value of the button either way when hitting F5. Where should this be called?

[d.healey]

After the declaration. My thinking was something wasn't working with the saveInPreset so maybe that would resolve it. Does this problem only happen with AAX?

[Dan Korneff]

@d-healey here's a simple version. I can't seem to change the value of a button?

HiseSnippet 718.3ocsU0taSCCE0tqdhVXSaR7.Dse0IMlRgsARSHF8KTErsJxXh+M443tZsD6HGmAUHdT3cj2.35jzlLnpzEIxux8ii8Im6GYjVw3wwJMB23hoQbD9IDuoRyjtSnBIZXODdSxozXCW6j4pyzHZbL2Ggwq8NqCbi5nzme9lNz.pjwKbgPWpDL9GDgBSg2Qm7dQPv.pO+BQXorO3jgLkrqJPk.7YMhKJhxtkdC+LpMsZDDd899BiR6YnFdLBWuixep2D0WjY4eoHVbc.2ZzF4AGTl6Ap.eKisdQcmHB7GM66NFAmxnBUXsLU3ojSE9h49KTisRC3TfnrdfqsL509eSO2EQObI5UOidaS7XZQjoHhkaOlLTBEpwTnDTlVY4hpsElzUAYHM6GRukOPCFyQz5HW28bNz0c2i2n4FMgBQrw4Np1oShwnjscdsyLv2vMcUgQJIXzZm736jgK2Z+Xt4RZPBuU6cOdbhjYDJoiRdlxvOW1Z2leqYileuoyeFZ73EFydyZUP.Wuvv11H8x.1RlDdMWuG7AAbZdhfdd+B15qVAikIDkRTIGJElyi341KuiCkqj1haNCgTMok1MyKsYBIR.GRCRtphRoe4wKzmF1iZnyNH3Lg6IhqMB6mCtG+NX7KqmoAoGO9ViJJM27xGn.qv09UDlfkvsM09xORmg+qdRXxP4mDPM2ebwtiHO.TRtWeos2SFKLSKuC4ALC4txi3qJc2lLRXXSVLeqs.9BB++a9luQZCR+wi4LSAYqSF74pt94APkOpRLB4MmRMZgsQ3rjPOXAMiCLQJ4Aw1dhZ1l5LaWqsUY73R+TieAO4Aaasw4AaOKHJjxzpqXYiB1cdOJ0CvIY5p+Fv+f.am4S.Dh69tnPXU7ULlUJdFv8Ei44U.yKp.lCp.lCq.lip.lWVALuZoXr+E7sIFUX1XB3XT+zMQXbeIE5xR6HQ+FLl7NlA

I can change it within an inline function, but calling setValue() after declaration doesn't work

[d.healey]

@dustbro Does it only happen with AAX or does it also happen with VST/AU?

[Dan Korneff]

@d-healey This is just AAX. The button initializes properly with VST AU

[d.healey]

Then I don't think there is anything we can do from within HISE to fix this. @Christoph-Hart any ideas?

[Dan Korneff]

@Christoph-Hart I figured it out.
If isPluginParameter is enabled on a button, AAX will default it's value to 0 even if it's set to 1 when you compile

[d.healey]

AAX will default it's value to 0 even if it's set to 1 when you compile

Does this happen in all AAX hosts? (are there any hosts other than pro-tools?).

[ustk]

@d-healey AAX is PT only

[d.healey]

@ustk What a useless format :p

[Fortune]

@d-healey said in Initial loading values of GUI elements in aax when plugin is opened....:

@ustk What a useless format :p

Yeah, it's so useless.
Because it's been widely used by so many pros and legend engineers.
And also it is almost the main mixing environment standart of the Hollywood film and music industry

[Dan Korneff]

@Christoph-Hart Any chance we can dig up this old thread?
If isPluginParameter is enabled on a button or combo, AAX will initialize to 0 no matter what the defaultValue is set to. Disabling isPluginParameter initializes to the proper value.
This only affects AAX. Other formats work properly.