=== len-1204 is now known as len-1304 | ||
Baker_ | Hey, I had a question about installing Ubuntu Studio. Do I have to partition my drive to run Windows 7 alongside Ubuntu, or can I have them both installed onto my C: drive without performing a partition? | 01:05 |
---|---|---|
Baker_ | Sorry for the noob question. It's been a long time since I've installed an OS. | 01:05 |
xnox | Baker_: for best performance - partition. note that you can access your windows7 files from ubuntu. | 01:08 |
xnox | Baker_: the installer will offer you to resize - install ubuntu alongside windows 7 | 01:08 |
Baker_ | Ah, I tried that with the wubi installer that came with the iso, but it wouldn't let me access my C drive with the simple partition tool. It made me use the advanced partition tool and I know nothing of how to use it. | 01:10 |
studio-user703 | exit | 15:27 |
=== aki is now known as Guest39106 | ||
Woogie | Hallo! | 19:30 |
zequence | Woogie: Hi | 19:30 |
Woogie | Does anyone knows how to set a default usb interface in jackd? | 19:32 |
Woogie | I can see it, it's right there, ALSA uses it to play music through audacius, I could record one Ardour after a few tweaks on the setup page, but could not replicate the behavior. | 19:33 |
Woogie | Plus, I could neither play it back nor monitor it while recording. | 19:33 |
Woogie | It's a Behringher Guitar Link interface. | 19:34 |
zequence | Woogie: When you use audacious, you are using Pulseaudiom, which in turn uses alsa drivers | 19:34 |
zequence | The "default" audio device in Pulseaudio is not the same as the "default" audio device in jack | 19:34 |
zequence | In jack, "default" is actually whatever is hw:0 | 19:34 |
zequence | And that can be different at each boot | 19:35 |
zequence | To see your devices, do this in a terminal: cat /proc/asound/cards | 19:35 |
Woogie | Yeah that happened, I set up a default but when rebooted I had a USB mouse plugged in and they exchange places I guess | 19:35 |
zequence | Woogie: Here's an example of what I have http://paste.ubuntu.com/1439667/ | 19:36 |
zequence | The device I use with jack is "2", M-audio | 19:36 |
zequence | The name withing the brackets [M66 ], can be used to start jackd | 19:36 |
zequence | There are two ways | 19:37 |
zequence | Either: jackd -d alsa -d hw:2 | 19:37 |
zequence | Or: jackd -d alsa -d hw:M66 | 19:37 |
Woogie | cat /proc/asound/cards | 19:37 |
Woogie | 0 [Intel ]: HDA-Intel - HDA Intel | 19:37 |
Woogie | HDA Intel at 0x98900000 irq 48 | 19:37 |
Woogie | 1 [CODEC ]: USB-Audio - USB Audio CODEC | 19:37 |
Woogie | Burr-Brown from TI USB Audio CODEC at usb-0000:00:1d.0-1, full speed | 19:37 |
zequence | You can do this in qjackctl as well | 19:37 |
zequence | Ah, so your device is hw:1, or hw:CODEC | 19:38 |
zequence | In Qjackctl -> Setup -> Interface | 19:38 |
zequence | Write: hw:CODEC | 19:38 |
Woogie | That's how it's set | 19:38 |
zequence | This way it will always start your usb device, no matter which order it is in | 19:39 |
zequence | Woogie: Are you having starting jackd, or just starting it with your usb device? | 19:39 |
zequence | having problems, is what I wanted to ask | 19:39 |
Woogie | I have made it record, using jack, and hw:CODEC as my default | 19:40 |
Woogie | but I won't get sound when playing it back | 19:41 |
Woogie | can't monitor it euther | 19:41 |
Woogie | either* | 19:41 |
zequence | If you are able to start it, it works | 19:41 |
zequence | If you get input, then audio works | 19:41 |
zequence | The rest is just connecting, and levelling | 19:41 |
Woogie | I just got it to work on audacity | 19:41 |
Woogie | lemme try with ardour | 19:41 |
zequence | Audacity, with alsa? (which is alsa->pulseaudio) | 19:42 |
Woogie | jackd | 19:42 |
zequence | Then it works, no problem | 19:42 |
Woogie | I didn't really changed anything but it works | 19:43 |
Woogie | thanks for your time zequence | 19:43 |
Woogie | now i have to figure out ardour ways | 19:44 |
Woogie | i.e. monitoring input | 19:44 |
zequence | Woogie: An easy way to monitor is just to connect your input to an output in Qjackctl -> Connect | 19:44 |
Woogie | nice! | 19:45 |
Woogie | thanks! | 19:45 |
Woogie | it's like magic | 19:45 |
Woogie | gotta tweak it tho, got some nasty lag | 19:45 |
zequence | period/buffer. Set it at least as low as 128 | 19:46 |
zequence | Sorry, Frames/period | 19:46 |
zequence | But, make sure to disable dbus in Setup -> Misc | 19:46 |
zequence | It will disable the pulseaudio bridge, which cause xruns at lower latencies | 19:46 |
zequence | Also, it might be impossible to get xrun free performance at 128 or lower, depending on your HW | 19:47 |
Woogie | done and done | 19:47 |
Woogie | now we're talking; i have made 100x progress in this chat that i've ever had done fiddling through out the interwebz, thanks again zequence | 19:47 |
zequence | Woogie: np. Have fun | 19:48 |
Woogie | oh yeah, i'm having so much fun already | 20:13 |
Woogie | got wired like 5 different apps | 20:13 |
Woogie | what exactly are xrun and why does ardour create a location marker when it happens? | 20:46 |
zequence | Woogie: That's an audio dropout | 20:46 |
Woogie | do that's why audio skips? | 20:47 |
zequence | When the software was not able to send all of the audio data in time | 20:47 |
zequence | The lower latency, the bigger the risk | 20:47 |
Woogie | got it | 20:48 |
Woogie | just out of curiosity, what's your usual software setup? | 20:49 |
zequence | Woogie: Ubuntu Studio ships with linux-lowlatency, which is a version of the linux kernel to enable lower latency | 20:50 |
zequence | It might be preferable to get a realtime kernel instead, but there are not many packaged out there | 20:50 |
zequence | Ubuntu Studio used to include one, but not since 9.10 | 20:51 |
zequence | Not all versions of the kernel get a realtime patch, which you need for patching the vanilla kernel | 20:51 |
zequence | So, it's not very easy to distribute a realtime kernel with Ubuntu | 20:51 |
zequence | Well, we could ship with an older kernel too | 20:52 |
zequence | Maybe in the future | 20:52 |
Woogie | so the rt check box in jackd is not really real time? | 20:57 |
zequence | Woogie: It is | 20:58 |
zequence | You can use jack in realtime on any kernel | 20:58 |
zequence | You just get dropouts easier on a normal kernel | 20:59 |
zequence | And less with -lowlatency | 21:00 |
zequence | Probably, even less with -realtime | 21:00 |
zequence | If you can find a good build of -realtime, that is | 21:00 |
zequence | Or, -rt (-rt usually means it is built from the same source as the distro uses for its kernel) | 21:00 |
zequence | Different distros have slightly different kernel sources | 21:01 |
zequence | They add their own patches on top | 21:01 |
Woogie | i do notice that when monitoring thru jack I get fewer xruns then monitoring on ardour | 21:02 |
zequence | If you don't have any fx between the source, and the monitor output, the difference should be so tiny, it can't be measured | 21:04 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!