Michael Gregorius

> > > The reason I haven't created a draft PR yet is because I'm still working out the control channels, which I'm kind of stuck on trying to figure...

> > I assume it's related to this PR: #7247 > > The LV2 implementation in LMMS uses linked models, so mono plugins are actually 2 linked plugin instances (L...

I have a first implementation of peak indicators which adds the new class `PeakIndicator`. It inherits from `QLabel` and has a slot to set/update the current peak value if it...

Pull request https://github.com/LMMS/lmms/pull/7295 adds peak indicators. They do not light up in warning colors if a threshold is crossed but already add some nice value. I guess warning colors would...

Hi @tresf, > * Like other plugin-specific warnings, we've tried to move towards context-aware. If a hint as to the plugin name can be provided in the error, this would...

@JohannesLorenz, can you please provide the test file? Or alternatively add code to dump the current state of `DataFile` at the start of `DataFile::findProblematicLadspaPlugins` and then load the file? The...

Hi @JohannesLorenz, it seems to depend on how old the presets are that have been copied into the users directory on the first start. If I for example check the...

> [...] In this case, a manual fix would also be sufficient. Though I would like to take the challenge to write a scripted fix for those 3 - unless...

Please note that there is also pull request #6866 by @consolegrl which intends to improve the structure of the upgrade routines with regards to `DataFile`, etc. I don't know what's...

Proposal to rename this issue to "Crashes with VST plugins that dynamically change parameter count" to better reflect the results of the investigations.