sfizz: sfizz.lv2 breaking the Ardour5 "Controllers" automation?
Hi all,
I’m getting a weird issue when using sfizz as a plugin in Ardour5. Basically, for tracks that equip the sfizz lv2 plugin, I can’t configure any controller-related automation: when going over the “Controllers” menu in the Automation list, nothing appears apart from a thin line, that makes me suspect Ardour5 is actually trying to show an empty list. This doesn’t seem to happen for other MIDI tracks using different plugins (e.g., Calf Fluidsynth), where the proper sublist appears (“Controllers 0-15”, “Controllers 16-31”, etc.).
I think this started happening in a recent update, as I most definitely used Controller automation in the past with Ardour5/sfizz, since it was a key component of an effort I invested on using CC messages to perform switches in .sfz files. I just pulled the latest version of the sfizz develop branch to make sure it wasn’t something that had been fixed already, but that didn’t seem to help. Not sure if this is because of some change in Ardour5 or sfizz, but as I said this only seems to happen with sfizz-powered tracks, so I thought I’d open an issue here first to see if this rang any bell.
Thanks for your amazing work!
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 21 (16 by maintainers)
OK after some discussion with Robin and Paul it seems that Ardour 5.12 assumes that the controls are fixed for the life of a plugin, so since we send an empty list at the beginning it stays empty until the plugin (instance I suppose?) is reloaded.
If you are willing to upgrade to Ardour 6—which brings numerous improvements as far as I understand!—it would be the best way as apparently it works well there and it is fully dynamic. If not, reloading the session after you set all the sfizz instances to their proper file is a workaround. I don’t really see a cleaner way at the moment, sorry.