i can't remember if it ever got to be clean and quiet, ever :) gtk lv2 uis are wrapped trough x11embed via libsuil (gtk2 on qt4). i must say that it works just barely enough and quite frankly it does it mostly due to great part of qt4 playing nice with glib so well--just try running qtractor with QT_NO_GLIB=1 and see (not) your gtk plugins falling apart if showing at all
all that to say that the above warning is the least of the problems when dealing with lv2 gtk plugin guis under a non-gtk host. yes i know that it says "critical" up there but well, i'd be lying if i say i care that much ;)
otoh. if that's one of your own plugins (ones of guitarix if i'm not mistaken), i'd recommend you to include support for lv2_external_ui in some near future. please. in the long run, when qt5 comes mainstream, that will be the only option for qtractor, as libsuil will be of no use, actually it will be hell counter-productive under qt5. sad but true :)
i can't remember if it ever got to be clean and quiet, ever :) gtk lv2 uis are wrapped trough x11embed via libsuil (gtk2 on qt4). i must say that it works just barely enough and quite frankly it does it mostly due to great part of qt4 playing nice with glib so well--just try running qtractor with QT_NO_GLIB=1 and see (not) your gtk plugins falling apart if showing at all
all that to say that the above warning is the least of the problems when dealing with lv2 gtk plugin guis under a non-gtk host. yes i know that it says "critical" up there but well, i'd be lying if i say i care that much ;)
otoh. if that's one of your own plugins (ones of guitarix if i'm not mistaken), i'd recommend you to include support for lv2_external_ui in some near future. please. in the long run, when qt5 comes mainstream, that will be the only option for qtractor, as libsuil will be of no use, actually it will be hell counter-productive under qt5. sad but true :)
cheers