[02:50] <UncleJed> In case anyone had read my earlier question, I'm currently reading through this thread to see if any of it helps. The original post about his issues is exactly what i'm looking at now. http://linuxmusicians.com/viewtopic.php?f=6&t=11016
[02:51] <UncleJed> I mean..it's the exact issue I'm facing - hardware and all.
[02:56] <holstein> UncleJed: you shouldnt need to 'change priorities' any more
[02:57] <holstein> UncleJed: what are you trying to do? exactly?
[02:57] <UncleJed> holstein - ok. I'm toying with just the front-end GUI setting first and will see if that works.
[02:57] <holstein> i suggest you do as follows.. unplug the audiobox, and get jack running on the internal audio device
[02:58] <holstein> you can use the live iso to isolate your current install and any "tweaks" you may have done that may be causing you issue
[02:58] <holstein> i suggest you get used to starting jack there on the internal audio device, and loading a few simple apps, and making sounds.. such as, yoshimi, or a simple audio player, such as audacious
[02:59] <UncleJed> I have actually reimaged everything from scratch yesterday. so I'm at base level right now.
[02:59] <holstein> be sure you are making the connections in jack, and routing.. i use qjackctl.. the "connect" tab there is where i make the routing happend
[02:59] <holstein> *after* you are comfortable using jack, with the internal audio device, i suggest doing as follows
[03:00] <holstein> first, consider disabling the internal audio device, so that you only have *one* device. know that, between boots, the labels in jack/alsa can and likely will change
[03:00] <holstein> so, you can have jack runinng perfectly, reboot, and assume the labels stay the same, but actually experience that error you linked, since the device is not present
[03:01] <holstein> if you want to keep both, and go between, you can, just know that that can happen
[03:01] <UncleJed> ok
[03:01] <holstein> i would simply try and see the USB audio device in the terminal under lsusb.. that means the device is present
[03:02] <holstein> i would remove *any* and *all* usb hubs in the chain.. i would make sure i am on a "known good" usb port.. one that a USB stick mounts in and works
[03:02] <holstein> i would then in the terminal use "aplay -l" and "arecord -l".. this will tell me, *if* i see the device there, that alsa is "seeing" it
[03:03] <UncleJed> ok - jack definitely sees it...it's just getting it to ardour that has been the problem. I can hear playback audio just fine through it.
[03:03] <holstein> UncleJed: it wont be
[03:03] <UncleJed> ah...ok
[03:03] <holstein> UncleJed: ardour uses *anything* connected, and configured properly with jack
[03:04] <holstein> UncleJed: you'll notice that i have literally filled the screen with "tips" and suggestions, which should take a lot of time to get to, but, none of them *yet* suggest using or opening ardour
[03:04] <UncleJed> right...lol...gotcha
[03:04] <holstein> anyways..
[03:04] <holstein> i would then use the GUI, qjackctl.. i open the
[03:04] <holstein> "setup" tab...
[03:05] <holstein> im looking under the "interface" drop down.. i will literally try *all* of those options there, if i dont know what is what
[03:05] <holstein> i will note that i cant likely trust any of those labels there.. you may see it read something like "generic USB device" or, who knows
[03:06] <holstein> thats another reason why, i like to remove or disable the internal audio device, so there is just the one options
[03:06] <holstein> option*
[03:06] <holstein> i then, simply try and start jack, with the same relaxed, default settings i had that worked with the internal audio device earlier
[03:07] <holstein> i then dont have to wonder "do i need a special kernel?" or "some settings for priorities need be made?".. i *know* jack worked, and the variable i changed is the audio device
[03:08] <holstein> if jack doesnt start there, i will typically open a terminal, and i will run "gksudo qjackctl".. i then try starting jack..
[03:08] <holstein> i dont want to, intend to, or suggest using jack as root long-term.. but, i can see if jack starts as root, then its likely a simple user permission issue
[03:09] <holstein> if jack starts, then i do as before, and open a simple audio application such as yoshimi, or a simple audio player such as audacious.. i use the same application that i know worked before, that i know how to route and configure
[03:10] <holstein> *then*, i'll move on to ardour.. after know how to start and run jack.. and route..
[03:10] <holstein> i'll open ardour, and import some audio to a track, and get playback working. then, i'll make a new audio track and route into the track from one of my line on the interface..mic or guitar or whatever
[03:11] <holstein> UncleJed: you shouldnt need any steps anymore with ubuntustudio 15.04.. or 14.04, for that matter.. not for nice , or priorities.. or permissions.. etc
[03:12] <UncleJed> holstein - thank you so much for your help! I truly appreciate your time!
[03:12] <holstein> you dont need an RT kernel to use it.. though, you may prefer one.. i suggest using it "as-is" first, and more to an rt kernel as needed.. which is for realtime effects processing, and live software synths
[03:12] <holstein> UncleJed: if you come here, and its completely dead, which happens... try #opensourcemusicians ..also, #ardour is helpful..
[03:13] <UncleJed> I don't think I need RT right now either. I'm all for working with "as is" as much as possible! Great for noobs. :)
[03:13] <holstein> well, you either need lower latency, or not
[03:14] <UncleJed> Ok - thanks again! I will start working on your steps later tonight.
[03:14] <holstein> it wont really relate to skill, so much
[03:14] <holstein> i personally work at quite a higher latency when mixing, since, i dont need to push the machine for lower latency
[03:14] <holstein> lower latency doesnt sound better, or different.. or imply a level of quality
[03:15] <holstein> its just that.. if you need realtime audio effects, as in, playing live with a guitar, and you want to add distortion etc from rakarrack, or whatever.. you'll need/want around 8ms latency, likely
[03:15] <holstein> same with live synths.. playing a midi keyboard as a live instrument
[03:15] <holstein> if you are not doing those things, then, you dont need it
[03:15] <UncleJed> i'm trying it because I was first trying sonar LE on a windows machine and kept getting delays between playback and live recording....was annoying.
[03:16] <holstein> you likely are using the computer to monitor
[03:16] <holstein> dont do that
[03:16] <UncleJed> that was my problem i'm sure
[03:16] <holstein> if you dont need to, just monitor live, and track
[03:16] <holstein> then, when you play back, you are playing back
[03:16] <UncleJed> ok - gotta run for now. thanks again!
[03:17] <holstein> you play live, thats happening live.. my interface has a mix knob that allows me to mix in live sound
[03:17] <holstein> sure.. good luck, UncleJed .. cheers
[06:52] <jarnos> Is it ok to use general kernels with ubuntu studio? What differences might I notice, if I did?
[06:53] <zequence> jarnos: linux-lowlatency is more or less a general kernel
[06:53] <zequence> The difference is in latency
[06:53] <zequence> Only important for live audio processig
[06:53] <zequence> linux-lowlatency might use more battery power
[06:54] <zequence> linux-lowlatency is not suitable for server environments, as it has a larger throughput
[06:54] <zequence> Smaller, I mean
[07:07] <sunstar> good to know
[07:20] <jarnos>  zequence thanks for the info
[09:59] <aloiece>   My brightness adjust keys work on recovery mode, but not in normal boot. I'm using nouveau graphic drivers
[09:59] <aloiece> It would be great if someone could send me in the right direction
[10:00] <aloiece> last time I asked, I was using kernel 3.13, someone told me this should b fixed in newer kernels
[11:09] <aloiece>   My brightness adjust keys work on recovery mode, but not in normal boot. I'm using nouveau graphic drivers
[11:09] <aloiece> It would be great if someone could send me in the right direction
[11:09] <aloiece> last time I asked, I was using kernel 3.13, someone told me this should b fixed in newer kernels
[22:54] <robinflorian> jj
[22:56] <Unit193> gg