Metaparameter Automation on Host DAWS
-
- KVRist
- 42 posts since 3 May, 2021
In the picture, I have the cutoff parameter from inside the hipass module assigned to the metaparameter, as shown. This cannot be seen from Reaper. But if I go inside the Basic Effect Module, any Metaparameter in that module can be seen. I could wrap my head around this if Reaper can read from the Metaparameters shown in the picture since those are the highest tier Metaparamters and all sub-modules can be assigned to those parameters, but I can't assign the cutoff filter from inside the Basic Effect module and none of the Metaparamters inside the hipass module can be seen from Reaper. I am either not understanding the architecture of this system, or there is a setting that takes care of this so any module can be seen inside Reaper, or this is a bug since the manual said that it should be recognized.
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
MuLab publishes the parameters of the "Project Main Module" to the host DAW.
I assume in this case that is the Basic Effect module.
You can verify this via right-click on that module, the Project Main Module will have its "Set As Projet Main Module" greyed out.
The reason why MuLab publishes the parameters of the Project Main Module to the host DAW and not the project meta parameters is because the main module is the one that will be visible in the main editor and when switching presets there then the newly loaded parameters are also immediately visible in the host DAW.
So if you want to publish the Hipass Filter parameters to the host DAW, best to insert that HiPass Filter into the Project Main Module and map the necessary meta-parameters.
Does this clarify it?
I assume in this case that is the Basic Effect module.
You can verify this via right-click on that module, the Project Main Module will have its "Set As Projet Main Module" greyed out.
The reason why MuLab publishes the parameters of the Project Main Module to the host DAW and not the project meta parameters is because the main module is the one that will be visible in the main editor and when switching presets there then the newly loaded parameters are also immediately visible in the host DAW.
So if you want to publish the Hipass Filter parameters to the host DAW, best to insert that HiPass Filter into the Project Main Module and map the necessary meta-parameters.
Does this clarify it?