Robin Schmidt

you need to make some "wrapper" AudioModule, i.e. a parent module that contains all these instruments as child modules. looks almost like you are going through a similar process as...

hmmm...so you want to write some temporary throw-away code to adapt the old patches? i guess i would check in setStateFromXml for the tag-name of the xml, and if it...

ok, then just keep it. i would still try to do it that way

> it should not depend on module name, it needs to retrieve the filter setting you could just check the passed xml for an attribute of the name, under which...

generally, in state recall, i just loop through all parameters of the module and check the xml for an attribute with the same name as the parameter name. if i...

modulations are stored gloabally in their own xml element with source and target where the target is given as a sort of path (in the format module.submodule.subsubmodule.parameter) like this: ```xml...

so, if the names of the parameters and the module.submodule.etc... structure with all the module names matches, it should work - otherwise, you need to update these identifiers in the...

hmmm...in this case, i would probably override `AudioModule::convertXmlStateIfNecessary`, retrieve the "Modulations" (child) xml there, loop through all the "Connection" (child) xmls, retrieve the "Target" attribute, and if it is "MushroomGenerator.Lowpass",...

or, if it's more convenient (because it also appears in the "Range" settings and who knows where else), you could convert the whole xml to a string via https://docs.juce.com/master/classXmlElement.html#a4a55313aba630bc87deb927375f06cff and...

or maybe a few more, if you need the same thing also for highpass, bandpass, etc. yeah.. changing the preset format or (even worse) the module structure while retaining backward...