/srv/irclogs.ubuntu.com/2015/05/05/#ubuntustudio.txt

=== wook is now known as Guest58246
UncleJedIn 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=1101602:50
UncleJedI mean..it's the exact issue I'm facing - hardware and all.02:51
holsteinUncleJed: you shouldnt need to 'change priorities' any more02:56
holsteinUncleJed: what are you trying to do? exactly?02:57
UncleJedholstein - ok. I'm toying with just the front-end GUI setting first and will see if that works.02:57
holsteini suggest you do as follows.. unplug the audiobox, and get jack running on the internal audio device02:57
holsteinyou can use the live iso to isolate your current install and any "tweaks" you may have done that may be causing you issue02:58
holsteini 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 audacious02:58
UncleJedI have actually reimaged everything from scratch yesterday. so I'm at base level right now.02:59
holsteinbe sure you are making the connections in jack, and routing.. i use qjackctl.. the "connect" tab there is where i make the routing happend02:59
holstein*after* you are comfortable using jack, with the internal audio device, i suggest doing as follows02:59
holsteinfirst, 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 change03:00
holsteinso, 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 present03:00
holsteinif you want to keep both, and go between, you can, just know that that can happen03:01
UncleJedok03:01
holsteini would simply try and see the USB audio device in the terminal under lsusb.. that means the device is present03:01
holsteini 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 works03:02
holsteini 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" it03:02
UncleJedok - 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
holsteinUncleJed: it wont be03:03
UncleJedah...ok03:03
holsteinUncleJed: ardour uses *anything* connected, and configured properly with jack03:03
holsteinUncleJed: 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 ardour03:04
UncleJedright...lol...gotcha03:04
holsteinanyways..03:04
holsteini would then use the GUI, qjackctl.. i open the03:04
holstein"setup" tab...03:04
holsteinim looking under the "interface" drop down.. i will literally try *all* of those options there, if i dont know what is what03:05
holsteini will note that i cant likely trust any of those labels there.. you may see it read something like "generic USB device" or, who knows03:05
holsteinthats another reason why, i like to remove or disable the internal audio device, so there is just the one options03:06
holsteinoption*03:06
holsteini then, simply try and start jack, with the same relaxed, default settings i had that worked with the internal audio device earlier03:06
holsteini 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 device03:07
holsteinif jack doesnt start there, i will typically open a terminal, and i will run "gksudo qjackctl".. i then try starting jack..03:08
holsteini 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 issue03:08
holsteinif 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 configure03:09
holstein*then*, i'll move on to ardour.. after know how to start and run jack.. and route..03:10
holsteini'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 whatever03:10
holsteinUncleJed: you shouldnt need any steps anymore with ubuntustudio 15.04.. or 14.04, for that matter.. not for nice , or priorities.. or permissions.. etc03:11
UncleJedholstein - thank you so much for your help! I truly appreciate your time!03:12
holsteinyou 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 synths03:12
holsteinUncleJed: if you come here, and its completely dead, which happens... try #opensourcemusicians ..also, #ardour is helpful..03:12
UncleJedI 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
holsteinwell, you either need lower latency, or not03:13
UncleJedOk - thanks again! I will start working on your steps later tonight.03:14
holsteinit wont really relate to skill, so much03:14
holsteini personally work at quite a higher latency when mixing, since, i dont need to push the machine for lower latency03:14
holsteinlower latency doesnt sound better, or different.. or imply a level of quality03:14
holsteinits 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, likely03:15
holsteinsame with live synths.. playing a midi keyboard as a live instrument03:15
holsteinif you are not doing those things, then, you dont need it03:15
UncleJedi'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:15
holsteinyou likely are using the computer to monitor03:16
holsteindont do that03:16
UncleJedthat was my problem i'm sure03:16
holsteinif you dont need to, just monitor live, and track03:16
holsteinthen, when you play back, you are playing back03:16
UncleJedok - gotta run for now. thanks again!03:16
holsteinyou play live, thats happening live.. my interface has a mix knob that allows me to mix in live sound03:17
holsteinsure.. good luck, UncleJed .. cheers03:17
=== wook is now known as Guest85229
jarnosIs it ok to use general kernels with ubuntu studio? What differences might I notice, if I did?06:52
zequencejarnos: linux-lowlatency is more or less a general kernel06:53
zequenceThe difference is in latency06:53
zequenceOnly important for live audio processig06:53
zequencelinux-lowlatency might use more battery power06:53
zequencelinux-lowlatency is not suitable for server environments, as it has a larger throughput06:54
zequenceSmaller, I mean06:54
sunstargood to know07:07
jarnos zequence thanks for the info07:20
aloiece  My brightness adjust keys work on recovery mode, but not in normal boot. I'm using nouveau graphic drivers09:59
aloieceIt would be great if someone could send me in the right direction09:59
aloiecelast time I asked, I was using kernel 3.13, someone told me this should b fixed in newer kernels10:00
aloiece  My brightness adjust keys work on recovery mode, but not in normal boot. I'm using nouveau graphic drivers11:09
aloieceIt would be great if someone could send me in the right direction11:09
aloiecelast time I asked, I was using kernel 3.13, someone told me this should b fixed in newer kernels11:09
robinflorianjj22:54
Unit193gg22:56
=== wook is now known as Guest76218

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!