I think if you have a plugin that crashes, don’t use it. The plugin code isn’t the DAW’s responsibility. Report it to the plugin developer and you’ll get a more stable plugin.
2 Likes
I’m curious if the flying faders for iCON Platform M+ and other iCON control surfaces has been solved in Ardour 9.0?
I commented about flying faders not working on my M+ on a IGM iCON post and they replied that the Ardour team is working on that bug.
Also, just a nice to have but the ability to make the automation lanes a different color would be helpful. Even after working with Ardounr for 15 years I still have trouble differentiating the tracks from the automation lanes.
Is there a Lua plugin that can hide and expose all fader, pan, etc automation? I’m thinking of vibecoding one but just checking to see if one already exists.
can’t wait to take Ardour 9 for a test drive!
Kim
I was continuing to have issues with the Icon faders and had given up after even a firmware upgrade failed to improve things.
Then I switched from the JACK/Pipewire backend and used ALSA, and they just worked as I expected.
1 Like
Interesting, where did you make that setting to switch from JACK to ALSA?
I’m assuming that Ardour still sees the iCON hardware as MCP & ALSA is just a translation layer?
data point: I don’t have Pipewire installed, still using JACK in Ubuntu Studio 22.04.
Also has anyone else experienced this?
- I’m still using Ubuntu Studio 22.04 and ran an update which pulled in some system stuff.
Now when I load a plugin in Carla with Ardour 8.12 open it crashes. If I don’t have Ardour open plugins will load into Carla without crashing. All plugins seem to load fine into Ardour…Carla crashes only when using it as a host when Ardour is open.
???
Kim
Window > Audio/MIDI then changed the backend to ALSA.
It is not impossible that there’s an error in the JACK backend for this purpose. At the moment, it is tricky for me to test this.