[06:33] <tarzeau> OvenWerks: no my build/test host is 10 years old i386 that's why. preferred is source package
[06:34] <tarzeau> OvenWerks: i can rebuild it for amd64 though (don't install i386 pkgs on amd64, that's BAD)
[06:46] <tarzeau> should appear here, when finished building: https://people.phys.ethz.ch/~myczko/debian/qtractor/
[06:55] <tarzeau> done, reload. feedback welcome
[15:43] <OvenWerks> tarzeau: everything I know how to test works :P this is not much really. I can record audio or midi, I can add plugins both with GUI and with generic gui supplied by qtracktor. I can manipulate individual midi notes by time and frequency but have not figured out how to edit velocity
[15:50] <OvenWerks> tarzeau: I do see lots of "QXcbConnection: XCB error: 3 (BadWindow), sequence: 3118, resource id: 9353275, major code: 40 (TranslateCoords), minor code: 0" kinds of messages, but that may be because the lib versions are sightly diffetrent from your machine to mine (yours is debian based mine is ubuntu 18.04)
[15:52] <OvenWerks> However these do not seem to affect performance I have had no hangs crashes etc. RUI obviously thinks differently than I do. It would not be hard for me to use qtracktor for what I do, but not optimal either. But then I have been recording strickly audio where Ardour shines.
[15:59] <OvenWerks> WHat I do find interesting is that qtrcktor seems to have audio/midi preferences... that is Audio is jack no questions, not alsa, not pulse, not OSS (thankfully) Midi is alsa, not jack or anything else. Though of course qtrcktors midi ports show up in jack through a2amidid
[16:00] <OvenWerks> Now that may be because jack was running before I started qtracktor, I dont know. Certainly, qtracktor expects to be packaged with qjackctl :) it borrows connection graphs etc. :)
[18:35] <tarzeau> OvenWerks: sounds good!
[18:35] <tarzeau> so i should go for updating it, i guess?
[21:43] <OvenWerks> tarzeau: I don't see why not.