It's using some notable chunks of Ardour's code, which might help it along.
OTOH, Reaper's lead developer was thinking of doing that at the beginning of Reaper's life, decided against it, and we can see how (well) that worked out! :)
OTOH, Reaper's lead developer was thinking of doing that at the beginning of Reaper's life, decided against it, and we can see how (well) that worked out! :)
For what it's worth, I find Reaper to be a lot better than Ardour in general. It just feels 100% professional and slick. The Ardour interface comes across like your typical GTK app, sluggish and glitchy with that constant feeling that something ain't right. You should have moved to QT a long time ago.
I don't bother to listen (much) to critiques of Ardour's GUI. Every week I get an email that tells me it is totally pile of crap and I should feel embarrassed to even consider it usable, and another telling me how smooth and intuitive it is, much better than any other DAW.
When people say things like "Ardour's workflow for doing <X> is a bit clunky - it takes 6 mouse clicks, but if you did it like <this> it would only take 3" ... I try to listen to that and incorporate these kinds of ideas.
Reaper does a bunch of things that Ardour doesn't. Ardour does a bunch of things that Reaper doesn't. Reaper does some things that we both do better than Ardour, and vice versa.
"300k+ LOC application should have moved to <other GUI toolkit a long time ago" suggests that you have never moved 175k lines of GUI code between toolkits, regardless of which application and which toolkit you're discussing.
Also, Reaper doesn't use Qt.
I have basically stuck with OpenMPT after all this time, since most of the time I want to really sequence something on the grid, and only deviate from that if really necessary(and then usually turn to Mixcraft which has a decent set of defaults and built-in plugins and presets for most things).
Ableton Live changed everything, even for the sequencer-originated DAWs like Cubase, and it's true that in Ardour we haven't (yet) attempted to tackle that sort of thing.
Stay tuned though!
I haven't had any luck getting responses to bug reports, and anyhow it seems that ZynAddSubFX should be a sufficiently common plugin that if this bug were easy to reproduce, someone else would have stumbled upon it by now (and so it probably arises due to a weird interaction with something else that's particular to my setup).