Add new comment

i can only say that it's all due to graphical toolkit galore mess-up (or mash-up if you wish).

fact is, by running ardour you're doing a lot of trouble to show and work with a plugin that uses such an alien gui toolkit or framework to start with (qt4)... it works barely but it is far from safe for general or heavy use. it won't survive much beyond the strictly spartan use cases :)

ntl. my suggestion goes like this anyway--please use the stand-alone application (drumkv1_jack) to edit your drumkv1 presets. then load them later while on ardour; do not make heavy use of the gui when you're doing it under ardour control. or else, use the lv2 gui very carefully (ie. save often) to edit your drumkv1 presets.

make it a strong note that drumkv1 is a pure qt4 gui which raises some undetermined troubles under a gtk host like ardour. if you run it stand-alone, jalv or under (4-x-sake, god-forbids-you) qtractor, it should be all fine.

aha. once you get those presets loaded and saved under your ardour session realm you won't even have to mess with the drumkv1 gui ever after and thus, you'll be fine and happy forever more ;)

hth. cheers