[00:00] <OvenWerks> For me it is the choice between getting really frustrated with windows (I have pulled windows out of laptops over frustration) and paying huge amouts of money for apple hardware
[00:00] <studiobot> <Johannes Menzel> I'm also more in the "analog" realm, but I really like to put some good piano vsts to compose.
[00:00] <OvenWerks> (and then paying huge amounts for plugings)
[00:01] <OvenWerks> pianotech is available for linux and probably the best... or at least most realistic
[00:02] <OvenWerks> sorry pianoteq
[00:02] <studiobot> <Johannes Menzel> I feel you. But I got the XLN Keys for 0-10$
[00:03] <studiobot> <Johannes Menzel> Yes, but my hearts bleeding at every dualboot windows startup
[00:05] <studiobot> <Johannes Menzel> The sad thing is that it's so easy to port plugins to linux, it's all about the f'ing cop protection.
[00:06] <OvenWerks> copy protection could be done in linux too. I think it is more a thing about not wanting to support it
[00:07] <OvenWerks> Linux does not have a one version for everyone as well as a small user base.
[00:07] <studiobot> <Johannes Menzel> This is the reason devs tell me if I ask them
[00:07] <OvenWerks> So linux may mean gnome xfce zde or fxwm
[00:08] <studiobot> <Johannes Menzel> But yes, support is another thinf
[00:08] <OvenWerks> It may mean x under or watland.
[00:08] <OvenWerks> Harrison has managed just fine.
[00:09] <studiobot> <Johannes Menzel> Yes, some dedicated plugin devs too, like u-he
[00:09] <OvenWerks> I find it interesting that while many copanies use Linux as the OS inside their synths, mixing desks, audio interfaces, few offer Linux setup utilities.
[00:10] <studiobot> <Johannes Menzel> Or overdone-dsp, but they currently don't seem to be in that good condition
[00:11] <studiobot> <Johannes Menzel> Yes, I guess even Waves are using Linux in their process.
[00:15] <studiobot> <Johannes Menzel> I'm not so much into this development thing, but I thought everything you need to support is to tell your customers is on which libraries (graphics and so on) your plugin relies.
[00:18] <studiobot> <Johannes Menzel> The typical linux audio user wouldn't be so hard to handle in these basic "where to put my plugin file" questions.
[00:35] <OvenWerks> A plugin should be self contained, compiled statically with almost all libs.
[06:58] <android> which kernal has trusty
[06:58] <android> for make a realtime kernel
[06:58] <android> from source
[06:58] <android> that is why creativity gets wasted
[06:59] <android> the disk is coding itself latent
[06:59] <android> when it adapts it adapts to suite the nullified environment
[07:00] <android> redoing the same junk over and over
[07:00] <android> like floating apps what is that  windows 3.1 for android
[07:01] <android> uncle C constraints