[00:35] <len-dt> ailo, where is your list of USB devices known to work?
[00:37] <len-dt> Both the ART devices seem to work as intended. They are both USB 1.1, so stereo, 44100/48000 at 16bit.
[00:49] <len-dt> ailo, looking at the specs I would say all 4 of the ART USB IF would work, but I have only tried the ART USB Dual Tube PRE and the ART USB Dual Pre Project Series. SO I know they both work for sure. Plug and go.
[00:50] <len-dt> ailo, I bought the dual tube and have found that even on my netbook, I can get good solid -p 64 service out of it with no xruns at all.
[00:53] <len-dt> ScottL, I hope you read the logs :-) The blue print works for me ok.
[00:54] <len-dt> Scott, the changing settings on the fly is done. The gui to set up what those changes are is not :-)
[00:56] <len-dt> ailo, Scott, others,  I am thinking that turning off cron, anacron and atd in record/tweak/performance mode is the way to go.
[01:00] <len-dt> My reasoning is this: even though, on any good(modern?) system it should not matter, because of it's intermittentcy, it would be very hard to track down. However, it can be turned on and off by installing/removing three files, so maybe it doesn't matter if it is configurable. In fact it may be easiest to just rename the files.
[04:59] <astraljava> Ooh, blueprints!
[05:00] <astraljava> Sorry guys, I crashed last night. Hopefully it'll mean I'll have more efficient bug fixing hours ahead. :)
[08:19] <ailo> len-dt: I regard fully supported those that function within their specs. So, if they are specified to work at 96kHz/24bits, that is what you need to be able to get
[08:19] <ailo> Are you saying your ART tube is a usb 1.1 device only?
[13:35] <len-dt> ailo, yes, the ART devices are USB 1.1, The USB is 16 bit and the spdif is 24 bit using two different ADCs
[13:37] <len-dt> They do have some USB2 devices, but they are many more pennies.
[13:49] <ailo> len-dt: Then it is a fully supported usb 1.1 device, which most usb2 devices are able to operate at also
[13:50] <ailo> So, for usb 1.1 operation, the list may be quite long
[13:50] <ailo> But not for usb 2
[13:50] <len-dt> ailo, Ya. I am looking at the moe expecive ones manual just now.
[13:55] <len-dt> ailo,  The voice channel has 24bit up to 192k USB and follows USB2 spec (no extra drivers for mac/win)
[14:01] <len-dt> their USB mic, which is USB2, Calls itself Linux compatible. However ailo, it does not have much info on how.
[14:04] <len-dt> It does bring to light one of the downfalls of USB mic. The package list says "3 meter USB cable ". It reminds me that is about the max length it should be.
[14:04] <len-dt> 3 meters for a USB cable is already long.
[14:06] <len-dt> I'm off.
[14:07] <knome> the "linux-compatible" part probably means that it works if you write the drivers yourself. :)
[14:09] <len-dt> knome, I think it means if you plug it into a linux system audio will get in... the question is will it be anything more than 16 bit at 44.1/48k
[14:09] <knome> :)
[14:09] <len-dt> The unit is too many pennies for me to buy and try out..
[21:13]  * Len-nb is thinking out loud
[21:14] <Len-nb> ailo, since I am using runlevels to determine modes of operation, there are some things that need to be taken care of.
[21:16] <Len-nb> The first thing is that a user can from the boot command line have the system boot directly into "Audio mode" (or video mode should such a thing come into being)
[21:16] <Len-nb> Also, a user while in "audio mode" may log out and back in without changing the mode.
[21:17] <Len-nb> This can be either a feature or a bug. I would prefer to call it a feature.
[21:18] <Len-nb> I might even go so far as to try to have the system boot to whatever mode it was in at shutdown.
[21:21] <Len-nb> However that would take away the option for the user to determine a mode at boot time.
[21:22] <Len-nb> Anyway, that takes care of system side things (anything requiring root perm)
[21:23] <ailo> I've been working on the web site today
[21:23] <Len-nb> userland things like pulse on or not would have to be set at login time depending on what the runlevel is.
[21:23] <Len-nb> ailo, how has that gone?
[21:23] <Len-nb> is that wiki or US web site?
[21:23] <ailo> Pretty well. I'm slimming it down, and trying to get it ready for publishing asap
[21:24] <ailo> ubuntustudio.org, which is worked at https://staging.ubuntustudio.org
[21:24] <Len-nb> Good, that is the one thing really missing.
[21:24] <ailo> Right now I'm working on the feature tour
[21:25] <Len-nb> I have to run, kids to take to the dentist... so I am gone a few hours.
[21:25] <ailo> ok. I'll be going to sleep in a moment. Catch you later
[21:25] <Len-nb> I'll take a look when I get back
[21:37] <ailo> Right now it would just be nice to finish up the feature tour. Try to keep it simple, and attractive looking
[21:38] <ailo> After that, and making sure all the text is correct and up to date, it just needs to be published
[21:38] <ailo> A more thorough documentation, hosted at the main site can be published for next release
[23:32] <len-dt> ailo, on https://staging.ubuntustudio.org/tour/ubuntu-studio/, you have "Ubuntu Studio is Linux-based" it should be "Ubuntu Studio is a Linux-based"
[23:32] <len-dt> ailo, I'm assuming you want me to be picky ;-)
[23:34] <len-dt> One paragraph down, second sentence "Ubuntu Studio free" should be "Ubuntu Studio is free"
[23:35] <len-dt> next page: https://staging.ubuntustudio.org/tour/audio/, under Jack, "eve" should be "even"
[23:36] <ailo> len-dt: I haven't done any text editing on those pages yet
[23:37] <len-dt> Did you want comments on spelling then?
[23:37] <ailo> I'm not really finished with much yet
[23:37] <ailo> The downloads page is mostly done
[23:38] <ailo> I've just started adding some pics to the feature tour thing
[23:38] <ailo> That will take most time I think
[23:39] <ailo> The links on the download page don't work yet. I'll fix that
[23:39] <ailo> For next release, I'll want to move installation instructions to a doc page
[23:39] <ailo> For now, I think it's fine as it is, given there isn't any strangeness with the wording etc
[23:45] <ailo> Ok, I better go to sleep now. I estimate it will take me another couple of weeks to finish my efforts for the web site and the wiki, so testing will come after that for me. So, perhaps in two weeks time