[02:35] <Mathnerd314> how do I check that jack is running properly?
[03:43] <Len-nb> Mathnerd314, properly for what use? Properly includes is it using the right device, is the latency appropriate for the current project, is pulse connected.... etc.
[03:45] <Mathnerd314> hmm, well currently I don't think it's running at all, qjackctl says "Cannot lock down 82274202 byte memory area (Cannot allocate memory)" and then that it couldn't start jack
[03:56] <Mathnerd314> so from that I gather it's not running at all - which doesn't seem right IIRC
[03:56] <Mathnerd314> ^ Len-nb
[03:57] <Len-nb> Ok, are you running ubuntustudio or something else
[03:59] <Len-nb> Mathnerd314, or have you added another user?
[03:59] <Mathnerd314> Len-nb: I started with a ubuntu installation, then installed ubuntustudio-desktop and the other packages
[04:00] <Len-nb> Ah, that makes sense
[04:00] <Mathnerd314> I think kubuntu and edubuntu might be in there too :p
[04:00] <Len-nb> you need to add your user to the audio group
[04:01] <Mathnerd314> ah, stuff here: https://help.ubuntu.com/community/Ubuntu%20Studio%20Upgrade%20from%20Ubuntu ?
[04:01] <Mathnerd314> I wasn't certain how much of that was outdated
[04:02] <Len-nb> and make sure the file jack put in /etc/security/limits.d/ is named audio.conf
[04:03] <Mathnerd314> yep, contents seem OK
[04:04] <Mathnerd314> I guess I need to reboot one more time for linux to notice I'm in the audio group?
[04:04] <Len-nb> logout and in
[04:04] <Len-nb> reboot is ok too, but shouldn't be needed
[04:08] <Mathnerd314> well, at least the error message changed: "ERROR: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode"
[04:11] <Len-nb> which device do you have?
[04:11] <Mathnerd314> hmm, I'm not certain TBH
[04:12] <Len-nb> Yes it sounds like it is able to start up.
[04:13] <Mathnerd314> the message before that is ": creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit"
[04:13] <Len-nb> from qjackctl there is a setup dialog
[04:13] <Mathnerd314> yep
[04:14] <Len-nb> on the left side there is a > beside interface
[04:14] <Len-nb> if you click on it it should list what devices you have
[04:15] <Len-nb> Right now you are using the first one hw:0
[04:16] <Mathnerd314> there's two "HD-Audio Generic"'s (hw:0 and hw:1) and "ALC892 Analog" (hw:0,1)
[04:17] <Len-nb> Are all of those internal?
[04:18] <Len-nb> I guess I am asking if you added an audio interface, or just have the ones that came with your computer?
[04:18] <Mathnerd314> they're all internal, I think.
[04:19] <Mathnerd314> > jackd -d alsa just says "device busy", so maybe it's a pulseaudio problem
[04:20] <Len-nb> Which version of ubuntu?
[04:20] <Len-nb> 12.04 or .10
[04:20] <Mathnerd314> .10
[04:21] <Mathnerd314> I might just switch to Arch, I don't really need these fancy GUI's :-)
[04:21] <Len-nb> Also did you set up an input and an output device? or just the interface?
[04:22] <Len-nb> That is why studio went with xfce
[04:23] <Mathnerd314> I'm using xfce right now, actually; maybe gnome is less fancy... :p
[04:24] <Len-nb> Seems a lot like the old gnome2
[04:25] <Mathnerd314> unity was OK, my alt-tab seemd broken though
[04:25] <Mathnerd314> I really only installed ubuntustudio to try this out: http://yaxu.org/demonstrating-tidal/
[04:26] <Mathnerd314> but after some discussion with him, I'm not certain ubuntustudio is enough
[04:27] <Len-nb> I will take a look...but really it shouldn't matter that much.
[04:28] <Mathnerd314> well, tidal depends on dirt, which depends on jack: https://github.com/yaxu/Dirt/blob/master/jack.c
[04:29] <Len-nb> Really it probably means building things from source whatever DE/distro you choose
[04:29] <Mathnerd314> well, building dirt and tidal was easy, the problem is figuring out how to run them
[04:30] <Len-nb> I can see that.
[04:31] <Mathnerd314> do you think wiping the disk and installing Ubuntu Studio from scratch would fix it?
[04:32] <Len-nb> I think it is just a matter of getting the right audio device set up.
[04:32] <Len-nb> You have jack running, Now find out why  it doesn't see the output
[04:33] <Mathnerd314>  well, I have audio playing now, and ps -Af doesn't list anything with 'jack' in the name...
[04:33] <Len-nb> It may be set up so that you need one device for input and another for output
[04:34] <Len-nb> default would be jackdbus if it was running
[04:36] <Len-nb> From a terminal what does aplay -l say? and arecord -l
[04:37] <Mathnerd314> is there a pastebin somewhere?
[04:38] <Len-nb> !pastebin
[04:38] <Mathnerd314> 'k. http://paste.ubuntu.com/5595066/
[04:39] <Mathnerd314> so there is a jackd running, actually, but it's running as me, and it seems like pulseaudio got started before it at boot
[04:39] <Mathnerd314> *jackdbus
[04:40] <Len-nb> PA starts at session start and jackdbus when you run qjackctl
[04:40] <Len-nb> it looks like you need to be using hw:1 and not hw:0
[04:42] <Mathnerd314> ... and that works
[04:43] <Len-nb> hw:0 is the audio port on your monitor out for DVI
[04:43] <Mathnerd314> hmm, but I think that's what I'm using for audio actually
[04:44] <Len-nb> DVI audio is not something I have experience with.
[04:45]  * Mathnerd314 checks the cables
[04:45] <Len-nb> But I think it would not have a plug on the computer itself
[04:47] <Mathnerd314> I guess there is a separate audio cable
[04:48] <Mathnerd314> but yeah, no audio playing at all now
[04:49] <Len-nb> What was the "it works" above for.
[04:49] <Mathnerd314> well, it creates/connects to the server successfully :p
[04:51] <Len-nb> If you are going to use DVI out, then it has to be set up as output only
[04:52] <Mathnerd314> ok, that sounds right
[04:52] <Mathnerd314> I do only have a pair of speakers...
[04:52] <Mathnerd314> (built into the monitor)
[04:54] <Mathnerd314> let me check my various manuals just to be sure...
[05:03] <Len-nb> hw:0 only shows as play back in your pastebin
[05:06] <Mathnerd314> so this is the motherboard: http://www.asus.com/Motherboard/F1A75M_PRO/#specifications
[05:07]  * Len-nb has an old P4
[05:08] <Mathnerd314> it probably has much better linux support :-)
[05:09] <Len-nb> The owner has gotten to know it quite well
[05:10] <Mathnerd314> so part of the problem is there are 6 outputs, so I have to specify 1) that I'm only using one output and 2) which output I'm using
[05:11] <Len-nb> Anyway, to use the dvi out you have to set jack to just use that as output. If you wish you can set up HW:1 for inout.
[05:11] <Len-nb> Jack will show all 6
[05:11] <Len-nb> you just connect to the ones you want.
[05:11] <Mathnerd314> hmm, yeah, so that part works
[05:13] <Len-nb> The way qjackctl works is that you can use either an Interface for one device for in and out or below that there is input and output for doing them different.
[05:15] <Len-nb> So you can set input to HW:1 and output to HW:0
[05:16] <Mathnerd314> well, if I just tell it to use the ALC892 Analog then it successfully connects and finds 8 playback ports and 2 capture ports. which I think is the right device/setup
[05:16] <Mathnerd314> so I think that's working
[05:16] <Len-nb> Yup
[05:16] <Mathnerd314> but there's no audio coming through, so somehow I have to specify which playback port to use
[05:16] <Len-nb> Just have to plug speakers in to hear it :)
[05:17] <Mathnerd314> but I only have these (crappy) monitor speakers, which I connected through trial-and-error...
[05:18] <Mathnerd314> and they only take up one port
[05:18] <Len-nb> Yup
[05:19] <Len-nb> mine looks like 12/10 i/o but it is really 6x6, 4x4 audio plus 2x2 spdif
[05:20]  * magic_silver_box slaps Len-nb around a bit with a large trout
[05:20]  * magic_silver_box slaps Len-nb around a bit with a large trout
[05:21]  * Mathnerd314 googles to see where that meme came from
[05:21] <Mathnerd314> hmm: http://en.wikipedia.org/wiki/Wikipedia:Whacking_with_a_wet_trout
[05:22] <Mathnerd314> or http://www.youtube.com/watch?v=WsfiD78Cy0s
[05:23] <Mathnerd314> but that reminds me, I still have no audio
[05:24] <Len-nb> the plugs should be line out (-10db) and so might be really quiet if not amplified.
[05:25] <Len-nb> Also some of them may be muted.
[05:25] <Len-nb> alsamixer (in a terminal) should show this
[05:26] <Len-nb> pulse would have turned up HW:0, but maybe not HW:!
[05:26] <Len-nb> HW:1
[05:27] <Mathnerd314> they all seem to be at max volume
[05:27] <Mathnerd314> * max gain
[05:29] <Len-nb> No Ms at the bottom?
[05:31]  * Len-nb hasn't used an internal sound card for a long time.
[05:31] <Mathnerd314> http://imagebin.org/249380
[05:34] <Len-nb> Looks right
[05:36] <Len-nb> What are you using as a source?
[05:37] <Mathnerd314> trying to get Rhythmbox to work, I think it routes through pulseaudio first
[05:38] <Len-nb> So you should see pulse in jack then. In the connect window
[05:40] <Len-nb> And in pavucontrol Rhythmbox should be routed to jacksink
[05:42] <Mathnerd314> hmm, I don't see those
[05:42] <Len-nb> Ok, in qjackctl there is an icon that says connections
[05:43] <Len-nb>  The audio tab will have system it should also have pulse
[05:44] <Mathnerd314> and it doesn't... so I need to configure pulseaudio to connect to jack?
[05:44] <Len-nb> pavucontrol can be started from a terminal though it show u
[05:44] <Len-nb> opps
[05:45] <Len-nb> it should be there.
[05:45] <Len-nb> pactl list short modules
[05:46] <Len-nb> about number 6 or 7 should something like dbus-jack-detect-module
[05:47] <Len-nb> module-jackdbus-detect
[05:50] <Mathnerd314> yep, it's there
[05:51] <Len-nb> and jack connections has system?
[05:54] <Mathnerd314> yep
[05:55] <Mathnerd314> http://imagebin.org/249382
[05:55] <Len-nb> Odd
[05:56] <Mathnerd314> I need to sleep; pick this up in 8 hours?
[05:57] <Len-nb> with some one, I need sleep too. I 8 I'l be at work.
[05:57] <Len-nb> But there should be others around then in their tz
[05:57] <Mathnerd314> yeah, the weekend be more active too, I'm guessing
[05:58] <Len-nb> Never reall active.
[05:58] <Mathnerd314> see you around, I guess
[05:58] <Len-nb> ok
[05:58] <Len-nb> good night
[11:57] <faLUCE> hello. I have a windows 8 guest on virtualbox under linux (ubuntu, with pulseaudio). when playing audio, I hear some clicks. Is there a way to improve that?
[12:16] <zequence> faLUCE: use a bigger buffer.
[12:16] <faLUCE> zequence: on what?
[12:16] <zequence> faLUCE: The latency you can get with virtualboc, running audio apps, is quite high
[12:16] <zequence> virtualbox*
[12:17] <zequence> I mean, you can't run on a low latency, without clicks
[12:17] <faLUCE> zequence: ok, I understand
[12:18] <faLUCE> zequence: but where can I set the bigger buffer?
[12:18] <zequence> faLUCE: Probably in the application you are using in Windows
[12:18] <zequence> Or, you mean, audio in general?
[12:18] <faLUCE> audio in general
[12:18] <zequence> I don't know how to do that in Windows 8
[12:19] <faLUCE> zequence: the problem is in ubuntustudio
[12:19] <faLUCE> I launch virtualbox through ubuntustudio
[12:19] <faLUCE> and vbox uses pulseaudio
[12:19] <zequence> faLUCE: No, the problem is in virtualbox
[12:20] <zequence> You can try on any linux distro if you want
[12:21] <faLUCE> zequence: so, I should try to reduce latency in the windows app?
[12:21] <zequence> No, you should raise it
[12:21] <zequence> virtualbox doesn't handle low latencies
[12:21] <faLUCE> zequence: yes, sorry
[12:21] <faLUCE> I would have said: red
[12:21] <faLUCE> I would have said: raise
[12:41] <faLUCE> zequence: I raised the latency from the default level, for the program, and it did not made difference. However, if I decrease latency from the default level, I hear more glitches
[12:41] <faLUCE> zequence: then, I think I should raise latency for the whole virtualbox
[12:42] <zequence> faLUCE: I'm quite able to run Win XP without glitches
[12:43] <zequence> faLUCE: I wouldn't know how to do that. But you could look at changing the latency for PA, something I've never tried doing
[12:45] <faLUCE> ok
[14:00] <faLUCE> hello. I have a windows 8 guest on virtualbox under linux (ubuntu, with pulseaudio). when playing audio, I hear some clicks. Is there a way to improve that?
[14:01] <smartboyhw> faLUCE, well VMs don't normally have good audio quality
[14:11] <faLUCE> smartboyhw: but it would be strange to have so many glitches
[14:11] <smartboyhw> faLUCE, dunno.
[14:15] <zequence> faLUCE: It's not strange, since you're running an entire OS on top of another one. There will be a bigger latency
[14:16] <zequence> faLUCE: You have to take into account that Win8 is more demanding on graphics too
[14:16] <zequence> faLUCE: I would use WinXP, if I were you
[14:16] <smartboyhw> faLUCE, if I were you I would not use Windows at all:P
[14:20] <faLUCE> smartboyhw: I know, but I'm forced :-( .... look, I'm forced to use windows on virtulbox under ubuntu. that's bullshit
[14:20] <smartboyhw> faLUCE, 1. Oh sorry and 2. No foul languages please:)
[14:22] <faLUCE> smartboyhw: ok :-)
[14:23] <faLUCE> sorr
[14:23] <faLUCE> sorry
[14:27] <faLUCE> zequence: the problem is that the software that I have to use is for windows7-8 only
[14:29] <zequence> faLUCE: So, why not install Win on your machine, or use a Win machine?
[14:29] <zequence> It would make sure you get the full power from the machine
[14:29] <faLUCE> zequence: it's a bit hard to explain, but I can't
[14:30] <zequence> faLUCE: Then see if you can raise latency on PA. You could try #pulseaudio
[14:30] <faLUCE> zequence: already tried
[14:44] <zequence> faLUCE: You raised PA latency, and got the same issue?
[14:44] <zequence> If so, the problem is entirely in Win8
[14:44] <zequence> I mean, added to the latency problem introduced by VirtualBox
[14:45] <zequence> If Virtualbox is given more time to work, since you gave PA higher latency, it's not a problem between VB and Linux
[15:53] <faLUCE> zequence: It's not clear how to raise latency on pa. I tried several options, but none worked
[15:53] <zequence> faLUCE: I've never tried to find out why, but I'm sure someone at #pulseaudio aught to know
[18:48] <Mathnerd314> ok, getting JACK to work, round 2. I restarted pulseaudio, now I have a PA sink and source in qjackctl. But still no sound...
[20:45] <holstein> Mathnerd314: ?
[20:45] <holstein> i would take pulse out of the equation
[20:46] <holstein> get JACK working. test JACK with a known good audio file in something like audacious
[20:46] <holstein> these are the steps i would do...
[20:46] <holstein> from a fresh start, or checking with ps aux | grep jack to make sure jack is not working...
[20:46] <holstein> 1. test an audio file with audacious and pulse...
[20:47] <holstein> 2. troubleshoot and get jack started
[20:47] <holstein> 3. test same audio file with audacious using jack output
[20:47] <holstein> !proaudio | Mathnerd314 this can help troubleshoot jack
[20:48] <zequence> Mathnerd314: When you have the sink and source ready, you still need to set the PA mixer to use the jack sink and source
[20:48] <Mathnerd314> well, I'm playing audio now, through pulse
[20:49] <Mathnerd314> jack is not running AFAICT
[20:49] <holstein> Mathnerd314: then test JACK.. not pulse through JACK.. when JACK is working, then you can test pulse into jack