[00:30]  * tsimonq2 waves
[00:31] <tsimonq2> Eickmeyer: I'll be happy to vouch, just CC me on the ticket.\
[02:59] <Eickmeyer> OvenWerks: They're all from the same control and copyright file, so that can be fixed.
[02:59] <Eickmeyer> OvenWerks: Overall, these issues can be overcome.
[03:00] <OvenWerks> Yes, just a) pointing them out, B) showing the command line I used for them.
[03:01] <Eickmeyer> Yeah, I got that. I think getting it to compile, package, and install was at least half the battle.
[03:01] <OvenWerks>  I don't remember if it also works running lintian against src directory. I do remember that running against different places shows different things
[03:01] <OvenWerks> Yes, good work.
[03:02] <Eickmeyer> I had been working on it since Wednesday, so you can imagine my relief when it actually _worked_.
[03:02] <OvenWerks> :)
[03:02] <OvenWerks> What I remember is that, it was easy to build from git, but hard to get it into a src package
[03:04] <OvenWerks> I could create a binary package directly, but that is not acceptable for the debian/ubuntu repos.
[03:04] <OvenWerks> (And I do agree with that idea)
[03:04] <Eickmeyer> Yeah. It took a little finessing the makefile, control, and rules files since they were a bit, shall we say, off?
[03:04] <OvenWerks> :) yes
[03:05] <Eickmeyer> It was looking for a lot of -static build depends and there were parts of the makefile and rules file that had been depricated in February.
[03:06] <OvenWerks> the plugin parts should be static.
[03:06] <Eickmeyer> It barked at me every time if the requested package name was *-static.
[03:07] <Eickmeyer> So, I just switched to the *-dev package for the build deps.
[03:08] <OvenWerks> I think falktx may have his own set of -static packages.
[03:09] <Eickmeyer> Exactly, I just had to point it to what is already in main & universe.
[03:10] <OvenWerks> The "debian way" is to load libs on demand to save memory. However, lib modules tht share namespace can conflict from one plugin to the next.
[03:10] <OvenWerks> Statically compiles plugins are "correct"
[03:11] <OvenWerks> This is why many of the good plugins use the author's own GUI toolkit rather than gtk or qt.
[03:12] <OvenWerks> Or they use something like fltk where the header file _is_ the lib.
[03:13] <OvenWerks> This is also why Calf and guitarix cause trouble in some setups.
[03:13] <Eickmeyer> I see.
[03:18] <OvenWerks> I haven't tried for some time, but it used to be that after viewing the guitarix plugin GUI, Ardour's colour scheme would change till restart.
[03:21] <OvenWerks> Doesn't seem to now.
[03:23] <OvenWerks> Hmm, It doesn't look like we install guitarix... at least I don't remember removing it.
[03:23] <OvenWerks> we do have guitarix-lv2 though
[03:25] <Eickmeyer> I've used those plugins with Ardour and have never had an issue.
[03:26] <Eickmeyer> Of course, I use lv2 nearly exclusively.
[03:26] <OvenWerks> It may be because you are using Ardour from ubuntu and not from Ardour.org, but who knows?
[03:27] <Eickmeyer> I've used it both ways.
[03:30] <OvenWerks> I am wondering why I have only the guitarix-lv2 package installed as our seeds list guitarix
[03:39] <OvenWerks> guitarix when run from the commandline works ok, but on exit it core dumps. Not something I would notice running ti from the menu.
[03:45] <Eickmeyer> Interesting.
[03:47] <OvenWerks> But it works fine as a plugin (so far) which is a much more likely place for me to use it.
[03:49] <Eickmeyer> Same. I don't even use Calf natively.
[03:50] <OvenWerks> I haven't used Calf for ages, nothing in there I need I think.
[03:52] <Eickmeyer> I use mostly mono input, EQs, and delays for live performance.
[03:52] <Eickmeyer> The delays simulate tape delays, which is pretty cool.
[03:52] <OvenWerks> I use a-eq or fil4
[03:53] <OvenWerks> Damian's stuff is pretty good too.
[23:45] <OvenWerks> Eickmeyer: did you ever get phones/speakers working? What computer do you have?