Add new comment

First things first: Everything works fine, QTractor rules.
thanks

- Everytime I display the mixer window (either by pressing F9 or clicking its button) it jumps 5 pixel up :) So I'm always putting it back in place...!? (in Unity [...])
i'm sure that's a dang WM issue all along. for years and years ever since Unity come into scene. well, there are some gnome'sh WM's that suffers from the same illness. let me lobby about kwin: it's a bliss. look, anyway, you'll have to brag about this one to the unity WM devs. if they care. i'll wish you the best good luck on that one :))

- The KB shortcuts don't work anymore ! [...] In the menus, they are greyed out ;-(
wait, is that Unity top application's menu all about? i guess things just doesn't work with Unity when you try to emulate that "bitten fruit" environment whatever :) let me say that Unity is reading its own book, not giving a damn to roads paved by others way too long and years before. get over it!

In clip edit, more KB shortcut work, maybe all, no time to test everything, at least copy and paste work (thank God).
why thank god? it's all (hu)man's, all the way down/up ;)

Now about the SVN version, since I could only build it using QT5 [...]
Only the generic UI, but then no more access to Hydrogen banks.
i think you either didn't read the "nota bene" call on the above annoucement (risking to be pedantic myself, "nb." is latin for "pay attention to this note!":))

but still, ask the drmr devs to add lv2_external_ui support, or better yet, the neweest lv2_idle/show_interface. that will do it ;)

bottom line says that all gtk (or anything else but qt5) lv2 uis won't ever work through suil or will never get shown on a qt5 lv2 host unless they implement the lv2_external_ui/idle+show_interface stuff. not even those qt4 ui plugins (yep, v1s included), which will crash qtractor on sight (not)--beware! :)

PS - The "Help/About..." window says "JACK Metadata support disabled." [...]
ignore that. it only gets away for latest jack1 (>= 0.124.1). afaict. jack2 doesn't yet implement the metadata API. so sorry. anyway, that would only deal with jack audio client/ports pretty-names aliases (designated via jack metadata properties).

i'm an old-schooller, i use jack1 (every once in a while i do test jack2 in some sandbox, but that's all:))

hth.
cheers