Robin Schmidt
Robin Schmidt
what happens is that the output of the modulator gets multipiled by the modulation depth of the connection (and, if relative is active, also by the unmodulated value) and then...
> check also the "relative" option in the popup menu hmm... i think, i should put a button on the modulation setup popup. perhaps next to the min/max fields
you mean the tree-view of the patch? yes - i think, it makes a lot of sense to represent a patch like this for easy "browsing" ...i'm just shooting down...
> modulation assignments aren't saved in xml patch or plugin state ahh - yes, you need to append `xml->addChildElement(modManager.getStateAsXml());` to `getStateAsXml` and `modManager.setStateFromXml(*(xmlState.getChildByName("Modulations")));` to `setStateFromXml`. look at the code, how...
...i guess, the problem is that the array of metaparams is defined in jura::AudioPlugin and you don't know how to access it from your AudioModule subclass? i think you can...
no there is no difference. this MetaName is the name reported to the host
callback? what kind of callback would you expect?
> is there a difference between setting MetaName (name used in the right click menu of slider in plugin GUI) ...or...wait...what right-click menu? i see only "Enter Value", "Meta attach",...
ah - ok - you are talking about setting it from code, not the gui, right?
hmm...ok, i think i could make a class MetaParameterObserver or something. or maybe i just do the renaming myself in the framework when the attachment is changed. that would be...