holstein | zequence: you mean, we'll backport that kernel to 14.04? | 15:03 |
---|---|---|
zequence | holstein: No, kernels are SRU'd by the Canonical kernel, each time a new release is out. | 15:13 |
zequence | -lowlatency is maintained by them as of trusty. It's merged with the -generic code, so it will automatically be SRU'd too | 15:14 |
holstein | so.. the kernel gets backported? then? | 15:16 |
zequence | holstein: No, it's a Stable Release Update | 15:18 |
zequence | It ends up in the updates pocket. Not backports | 15:19 |
holstein | so, that kernel? with the changes, by *some* means.. gets into 14.04? | 15:19 |
zequence | Yes, once Utopic is out | 15:20 |
zequence | If you check in /etc/apt/sources.list, trusty-updates - that's where it ends up | 15:21 |
holstein | i had to bail on ubuntu on my production machine | 15:21 |
zequence | Yeah? | 15:22 |
holstein | i'll have to setup a testing scenario on another box.. | 15:22 |
holstein | or, a partition | 15:22 |
zequence | What was your problem with Ubuntu? | 15:22 |
holstein | just little things.. | 15:22 |
holstein | avlinux is a better fit for my studio right now | 15:22 |
holstein | easier to get what i need | 15:22 |
holstein | no real "problem" with ubuntu", necessarily | 15:23 |
zequence | Give me an example | 15:23 |
holstein | a few mixbus plugins that i paid for wont draw | 15:23 |
holstein | the kernel in AV is more stable with my gear | 15:23 |
holstein | its not up to ubuntu to stay behind and make my hardware work great.. i get that | 15:24 |
holstein | but, AV is more of an appliance.. and when i got all in on mixbus, i wanted the "Best" environment for it.. so i took a long weekend and did a bunch of tests.. and landed with av on the production rig | 15:24 |
holstein | though, it does feel like a bit of a step back, and i miss some things from the ubuntu repos, its the easiest way to address all the little issues i was having | 15:25 |
holstein | mostly growing pains with the mixbus plugins.. "Our plugins use the "OpenGL" drawing functions, and this problem indicates a bug in a particular OpenGL driver function that only the XT plugins use." | 15:27 |
zequence | ok | 15:27 |
holstein | i tried working in a few places.. but at the end of the day, i just need to do some work there.. | 15:27 |
holstein | i was hoping harrison would get more into it | 15:27 |
zequence | What kind of kernel problems where you having? | 15:27 |
holstein | and, since mixbus is proprietary, there seems to be little interest in our particular community for support | 15:28 |
holstein | zequence: no "problems".. i just get *much* better stable performance with an older RT kernel.. | 15:28 |
holstein | i feel ubuntu is on a better path though, for the future.. | 15:28 |
zequence | You mean lower latency? | 15:28 |
holstein | zequence: i can achieve lower latency, sure.. but, i can also get better performance at the same latency setting | 15:29 |
holstein | like, re-drawing mixbus's mixer.. in ubuntu would take about 12+ seconds.. maybe more to see the entire output.. at the same settings in AV, its less than a second | 15:30 |
holstein | its *all* changing.. and gl drivers, open and proprietary.. its all related.. and a mess | 15:31 |
zequence | ok, so it seems a lot of it had to do with Mixbus specifically then. | 15:31 |
holstein | im not promised support for linux from nvidia, so i get what i get there.. and, do i need nvidia? i want dual head, and that was the easiest way for me to add it | 15:31 |
zequence | I'm sure there are other things too. Stuff that we aren't providing in simple steps, like a2jmidid | 15:32 |
holstein | zequence: sure.. but, should it take 12+ seconds to draw? | 15:32 |
holstein | zequence: its not open and not in our repos.. so it would be up do Ben.. | 15:32 |
holstein | he says, it would be more up to ubuntu.. and im actually sure ardour3 is dealing with a lot of this, and will trickle into the next version of mixbux | 15:32 |
holstein | but.. for me, right now.. with my current hardware/software, AV was a better and easier fit | 15:33 |
holstein | i dont think its doing anything particularly new or ground breaking, though | 15:33 |
holstein | zequence: you havent had a chance to fire up 14.10 and your firewire device? | 15:34 |
zequence | Nope. But, I don't think it's supported yet anyhow | 15:35 |
holstein | i havent either.. but, i may try and do that from a live environment on the main machine | 15:35 |
zequence | It wasn't on a list I saw | 15:35 |
holstein | zequence: oh.. | 15:35 |
holstein | i mean, i dont really care or want/need that.. but it would make it handy for folks to use the firewire device in audacity, for example | 15:35 |
holstein | if you have a firewire device, you use JACK. and it has such a high barrier of entry.. and if you have the wrong firewire chipset, it'll just never start ;) | 15:36 |
holstein | its challenging | 15:36 |
zequence | Yeah | 15:38 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!