Plugins fail to load into Logic- isMetaParameter not set.

[Lindon]

@gorangrooves

Well I suspect that AUval is not reporting the level of detail you need in lines such as this

WARNING: retrievedValue = 0.490000 (was 0.490000), Parameter did not retain default value when set

I suspect if there were enough decimal places you might see something like this

WARNING: retrievedValue = 0.4900001111 (was 0.4900002345), Parameter did not retain default value when set

..so yes if a control changes any =other control its a metaParameter and needs this value set.

The target controls DONT need this to be set.

But you should remove all this "rounding code" anyway.

[gorangrooves]

@Lindon Thank you very much! Yes, I removed the rounding attempt yesterday when I realized it wasn't doing anything.

It seems I have a lot of components to set this way, probably all sliders and buttons.
I'll see to do it programatically.
It will be a bit of trial and error until I figure out all the components that need to be changed. I'll report back.

[DanH]

@gorangrooves did you try enabling isMetaParameter on the sliders concerned (or all of them?)

[gorangrooves]

@DanH I am going to do that now. Just figuring out the most practical way, since I have 17 plugins to go through.

[d.healey]

@gorangrooves said in Plugins fail to load into Logic- components' default values rounded up:

t figuring out the most practical way, since I have 17 plugins to go through.

Start with 1, to make sure this is the problem before you worry about all 17.

Do all plugins have the same components?

[gorangrooves]

@d-healey Yes. I am going to compile one now and test. I made a few loops to get all components with certain names (Slider, Mute, Solo, Panner...) and set those flags to 1. Once I get one plugin to work, I'll run the script in all other plugins and recompile.

[gorangrooves]

@Lindon @bendurso @d-healey Happy to report that the first plugin I tweaked passed the validation! Yay! Thank you so much for all your help! Going to run the script in all the other plugins, then recompile.

Does any one of you know of any alternative location where AU plugins may be located?

The Logic's Plugin Manager is displaying some of my older plugins that are clearly not in the regular components folder.:
Mac HD > Library > Audio > Plug-Ins > Components

While some of them say "can't open", one of them opens in side Logic, but it is not in the components folder.

[d.healey]

@gorangrooves There are only two places they should be. Either the system library folder or the user library folder

[gorangrooves]

@d-healey Aha. Found it. I see the working plugin. I guess the references to others are just stored in some Logic cache. Thanks, Dave!

[AxiomCrux]

@gorangrooves I realize this is an old post, but I have been going about it simply by using a custom UI look and feel and drawing the widget to show the rounded value, even though under the hood is a slightly different value. Seems to work so far, will double-check in logic

g.drawAlignedText(Math.round(val) + "" + obj.suffix, [a[0], -0.15*a[3], a[2], a[3]], "centred");