[09:10] Hi everyone [09:10] caodepalha, greetings [09:12] I have a question here. I read in a book that it is advisable to remove the pusleaudio package in ubuntustudio. it read that both servers running at the same time jackd & pulseaudio) can cause problems. is this correct? [09:22] does anyone know anything about this? [09:24] i havent had any problems [09:37] caodepalha: Not correct [09:37] caodepalha: What book was that? [09:42] let me check again [09:42] its a book called crafting digital media [09:43] Crafting digital media, Audacity, Blender,Drupal, GIMP, Scribus and other open source tools [09:44] caodepalha, read it. since published, it seems the pulse/jack conflicts have been ironed out. and if YOU haven't experienced problems, why would you even consider it? [09:44] by Daniel James [09:44] i get a lot of xruns when recording [09:45] caodepalha: Is it a Ubuntu Studio install? [09:45] in the book it says it is related to the settings in jack and problems with pulse audio [09:45] yes it is ubuntu studio [09:45] the book is wrong [09:45] ok thank you [09:45] "a lot"? anyway, try it and compare. [09:45] jack settings, yes. but not because of pulseaudio [09:45] do you know what xruns are about? [09:46] xruns means that jack was not able to process the audio in time [09:46] theres another word for that: audio dropout [09:46] is that a problem when recording? [09:46] Yes, because you get click sounds [09:46] sorry i'm still a newbie [09:46] any tips on how to avoid that? [09:46] caodepalha: do this command: cat ~/.jackdrc [09:46] caodepalha, FYI, the 12.04 kernel seemed to fix that issue [09:47] cfhowlett: Which issue is that? [09:47] zequence, jack/pulse audio conflicts [09:47] cfhowlett: not related to the kernel [09:47] there was a bug in pulseaudio, which I fixed [09:48] had to do with pulseaudio not letting go of the audio device, when jack asked for it [09:48] jack1 is not able to grab the card at all [09:48] only jack2 [09:48] zequence, entirely possible/likely that I used the wrong term there ... [09:48] there was another problem with jack earlier, making it impossible to kill it sometimes [09:48] that was fixed too [09:49] neither problem was causing xruns [09:49] I didn't code the fix, but I pathched both packages, just to be clear [09:50] so should i run the: cat ~/.jackdrc ? [09:51] zequence, you contributions are MUCH appreciated! [09:51] caodepalha: Yes. Paste the results here [09:54] zequence, here's mine. What's it all mean? /usr/bin/jackd -p 128 -R -P 60 -T -d alsa -n 2 -r 48000 -p 1024 -d hw:0,0 [09:58] "-p" stands for frames per period. It is quite low, so should give you ok latency, and hopefully no xruns [09:58] To see what the rest means, do: jackd -d alsa --help [09:59] holstein: I got the source from their website because I wanted to compile it on Debian. But I failed. So I downloaded their binary for Ubuntu and after hours of installing dependencies ... it kind of works. [09:59] Actually, some options are not alsa specific, so to see them, do: jackd --help [09:59] Except for freezing X for several minutes and OOMs .-/ [10:02] ok these are the results: /usr/bin/jackd -p128 -dalsa -r192000 -p128 -n2 -Xseq -D -Chw:0 -Phw:0 [10:02] do i need to start jack before running the command? [10:04] caodepalha: What you did was print out the contents of the file .jackdrc in your home folder [10:04] caodepalha: If you would start jack manually using a terminal, you could use a command like that. But, you don't need to [10:04] caodepalha: That command is how you have set up qjackctl [10:04] ok... [10:05] is it correct? [10:05] caodepalha: The reason why you are getting xruns is because you have a very low latency setting [10:05] ah ok. what can i change on jack setting then? [10:05] caodepalha: -p128 means 128 frames/period. Together with 192000 samplerate, that gives jack a very small amount of time to finish its processes [10:06] caodepalha: Use qjackct, and raise the frames/period, or use a lower samplerate. Do you need 192kHz= [10:06] ? [10:06] ok let me check! [10:08] caodepalha: Do you monitor yourself through the software? What do you use for recording? Ardour? [10:08] If you have a mixer for monitoring, you don't need low latency - unless of course you are playing a soft synth, or using some FX, like a virtual amp while recording [10:08] I use ardour [10:09] caodepalha: What sort of stuff do you record? Is it all line in, and no live FX from your computer? [10:10] I use ardour. I connect the electir guitar directly to the laptop input. my midi is connected directly to the laptop as well. when i record vocals i connect a condenser mic through a mixer and then onto the laptop [10:10] caodepalha: midi, as in midi cable, or the audio output from a keyboard? [10:11] i use electric guitars, acoustic guitars, a condenser mic and a shure sm58, a small beringer mixer and oxygen8 [10:11] midi is not audio. It's a data control format. you can use it to control synthesizers [10:11] i connect oxygen8 via usb [10:12] yes [10:12] caodepalha, yeesh. that's kind of asking a lot. you got a super duper system or something? I used an interface when I recorded for my laptop. [10:12] ok, so do you use soft synthesizers? That would be the live FX I'm talking about [10:12] yes eventually i use amsynth and phasex [10:13] caodepalha: While you are not using any live processing, i.e. a soft synth, you can raise latency while recording [10:13] caodepalha: Raise frames/period to at least 1024 [10:13] you can even use 2048 [10:14] And use your mixer for monitoring for the external audio sources, as your guitars and vocals [10:14] When you record soft synths, you need to find out an optimal latency level. You might not need 192kHz. 48kHz is quite enough. [10:15] And while recording, don't mess with the computer. Just click record, and then use your keyboard [10:15] iḿ getting started on linux. i'm a total newbie.in the first experiences i made with ardour i dropped a few loops on it, then went to record some electric guitars [10:16] latter added some synths [10:16] and more guitars [10:16] caodepalha: What kind of audio card do you have? [10:17] you're saying i should raise the frames or use a lower sample rate right? [10:17] this is a laptop i got from a friend [10:17] how can i know about the soundcard? lol [10:17] caodepalha: Both would be good, actually [10:17] caodepalha: Oh, so it's the builtin audio device? [10:18] cat /proc/asound/cards [10:18] yes... for now it is. i'm planning on getting an external soundcard [10:18] ..for seing the audio devices [10:18] 0 [Intel ]: HDA-Intel - HDA Intel [10:18] HDA Intel at 0x92400000 irq 43 [10:18] caodepalha, see presonus 1box/audiobox. works with linux out of the box. [10:18] here it is [10:18] caodepalha: 128 frames/period might work if you use 48kHz samplerate. If that doesn't work, try 256 frames/period with 48kHz samplerate [10:19] ok! [10:19] caodepalha: If you still have a lot of xruns, come back [10:20] I cannot thank you enough! Its a bit of a learning curve to get around linux but i'm loving it. people are very helpfull. this is great! thanks alot [10:22] caodepalha: Have fun [10:45] this is what i've made with ardour so far: https://soundcloud.com/caodepalha/fairground-voodoo-mix-cheap [10:53] caodepalha: Nice stuff [10:55] caodepalha: There is actually one thing that could cause xruns, and that is the pulseaudio to jack module. It's a package called pulseaudio-module-jack. You can disable the module, either by uninstalling that package, and restarting pulseaudio (pulseaudio -k), or by disabling dbus support for jack in qjackctl -> Misc [10:55] The module acts as any other jack client [10:55] but, it can use a lot CPU power. If you don't need to listen to youtube while recording, you can just uninstall that package [10:56] i dont need to listen to youtube while recording [10:57] can it be unistalled in the software center? [10:57] uninstalled* [10:58] caodepalha: sudo apt-get remove pulseaudio-module-jack [10:58] caodepalha: or use synaptic. You can install synaptic from the software center [10:58] just remember to restart pulseaudio. Also, quit jack before you do. To restart pulseaudio, kill it: pulseaudio -k [10:59] jack is not started right now. can i perform those commands anyway? [11:23] ok i've just done those commands [12:39] 0913 === mo is now known as Guest6012 [12:39] 0913 === Fyodorovna is now known as wilee-nilee [22:16] After allowing some updates earlier today my soundcard started making funny noises as the volume level indicator showed up time after time. After rebooting, I am getting no more audio from my card, even though everythinh 'seems' normal. any ideas? TIA! [22:18] Application Launcher -> Terminal Emulator -> alsamixer [22:18] make sure its not muted, turned down and that the correct card is being used [22:27] XRS1, Master level is at 57, but Headephone , does not show a value (zeroed?) How do I raise the volume lvel in alsamixer? [22:31] use the tab key and the arrow keys to navigate