Re: [pulseaudio-discuss] Pulse audio does not work with my hdmi output
Am Samstag, den 17.04.2010, 11:00 -0600 schrieb Dark Shadow: I could not get a pulseaudio -vvv because every time I killed it it re-spawned on it's own before I could start it. Did you search for »pulseaudio respawn« on the Web? You would have found [1]. Anyway the term used in PA seems to be »autospawn«. Reading `man pulse-client.conf` is also informational. (Although finding that is a little harder, because it is not referenced by `man pulseaudio`.) [2] and [3] in the PA Wiki are also good to read when debugging a problem. […] Thanks, Paul [1] https://fedoraproject.org/wiki/How_to_debug_PulseAudio_problems [2] http://pulseaudio.org/wiki/Community#BugsPatchesTranslations [3] http://pulseaudio.org/wiki/Troubleshooting signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulse audio does not work with my hdmi output
'Twas brillig, and Dark Shadow at 17/04/10 18:00 did gyre and gimble: card 1: NVidia [HDA NVidia], device 3: NVIDIA HDMI [NVIDIA HDMI] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 7: NVIDIA HDMI [NVIDIA HDMI] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 8: NVIDIA HDMI [NVIDIA HDMI] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 9: NVIDIA HDMI [NVIDIA HDMI] Subdevices: 1/1 Subdevice #0: subdevice #0 Hmm, that seems odd. I've not got much hardware to compare with but do you know why there are so many devices there? (and why some of them appear not to work!) Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mandriva Linux Contributor [http://www.mandriva.com/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/] ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] New kernel 2.6.34-rc4, no audio
'Twas brillig, and Gene Heskett at 17/04/10 21:37 did gyre and gimble: Greetings Colin; I rebooted to a new kernel as above, and now there is no audio, but the diff is that there is, but it is apparently not getting from PA to the sound system. pavucontrol says its using /dev/null for a sink. But if I crank up the mic gain the sound is alive well. Are you sure it's using /dev/null? I can believe a Null Sink but not anything related to /dev/null. kde when started, also wanted to forget about all the emu10k1 stuff, but the moddules are loaded and running if the mic nopise in the speakers is to be believed. You have to take the KDE messages with a pinch of salt. KDE scans the devices manually outside of PA in order to present a GUI to the user when PA is not running. I suspect this message is just a product in some capacity of a wider failure. I have put the output of pulseaudio -vvv at: http://gene.homelinux.net:85/gene/Genes-os9-stf Can you see what is wrong? I can only see that you posted the wrong link :p Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mandriva Linux Contributor [http://www.mandriva.com/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/] ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] New kernel 2.6.34-rc4, no audio
On Sunday 18 April 2010, Colin Guthrie wrote: 'Twas brillig, and Gene Heskett at 17/04/10 21:37 did gyre and gimble: Greetings Colin; I rebooted to a new kernel as above, and now there is no audio, but the diff is that there is, but it is apparently not getting from PA to the sound system. pavucontrol says its using /dev/null for a sink. But if I crank up the mic gain the sound is alive well. Are you sure it's using /dev/null? I can believe a Null Sink but not anything related to /dev/null. kde when started, also wanted to forget about all the emu10k1 stuff, but the moddules are loaded and running if the mic nopise in the speakers is to be believed. You have to take the KDE messages with a pinch of salt. KDE scans the devices manually outside of PA in order to present a GUI to the user when PA is not running. I suspect this message is just a product in some capacity of a wider failure. I have put the output of pulseaudio -vvv at: http://gene.homelinux.net:85/gene/Genes-os9-stf Can you see what is wrong? I can only see that you posted the wrong link :p Col Pulseaudio-vvv is the file you want to click on. I am seeing a file list at http://gene.homelinux.net:85/gene/Genes-os9-stf/ are you not? Or do you mean it should have been 'pacmd ls'? -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) BOFH excuse #262: Our POP server was kidnapped by a weasel. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] New kernel 2.6.34-rc4, no audio
On Sun, Apr 18, 2010 at 2:44 PM, Gene Heskett gene.hesk...@verizon.net wrote: Pulseaudio-vvv is the file you want to click on. I am seeing a file list at http://gene.homelinux.net:85/gene/Genes-os9-stf/ From your posted log file: D: module-udev-detect.c: /dev/snd/controlC0 is accessible: no [...] D: module-always-sink.c: Autoloading null-sink as no other sinks detected. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] New kernel 2.6.34-rc4, no audio
'Twas brillig, and Daniel Chen at 18/04/10 20:50 did gyre and gimble: On Sun, Apr 18, 2010 at 2:44 PM, Gene Heskett gene.hesk...@verizon.net wrote: Pulseaudio-vvv is the file you want to click on. I am seeing a file list at http://gene.homelinux.net:85/gene/Genes-os9-stf/ From your posted log file: D: module-udev-detect.c: /dev/snd/controlC0 is accessible: no [...] D: module-always-sink.c: Autoloading null-sink as no other sinks detected. Yup, so for whatever reason we can't access this file. Possibly because it doesn't exist. i.e. your problem is with the alsa setup. Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mandriva Linux Contributor [http://www.mandriva.com/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/] ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] [PATCH] pulse: Fix invalid buffer pointer return value
Colin Guthrie wrote: 'Twas brillig, and David Henningsson at 16/01/10 07:07 did gyre and gimble: David Henningsson wrote: Lennart Poettering wrote: On Sat, 09.01.10 10:00, David Henningsson (launchpad@epost.diwic.se) wrote: The pulse ALSA plugin has been known, for a while, to not work properly, causing underruns, hangs etc. I sat down yesterday trying to figure it out, and I'm pretty certain this patch improves the situation, but I don't mind getting some help testing it before it is committed upstream. I am kinda convinced that the actual fix for this issue is this patch. Could you check that? http://git.0pointer.de/?p=pulseaudio.git;a=patch;h=8d356659e69556fa25d0579a66084f820683e2b8 I have now checked it with the latest version of pulseaudio and without my patch posted earlier, I still experience hangs. That and positive feedback given from https://bugs.launchpad.net/bugs/485488 makes me believe that the patch is ready for inclusion upstream (it is already in Ubuntu, thanks Dan). Now onto the next problem. If an underrun occurs in the pulseaudio front-end, it is delivered asynchonously to an underrun callback. This sometimes happens after more buffers are sent (through pa_stream_write()). So these new buffers will end the underrun in parallell with the processing of the underrun in the client, making the underrun obsolete. After all, seen from the client program's perspective, if I write a buffer and it returns underrun (-EPIPE), I assume that all other buffers I've written, which returned successfully, have already been played back. The best action in this case should be to ignore the underrun, if I can determine that the above case is true. Now, how do I do that? I have tried to look at pa_stream_get_timing_info() [1], but I can't find a reliable way to distinguish valid underruns from obsolete ones. // David [1] which needs to be updated, and I can't use pa_wait_operation from the callback so I'll have to use a second callback for the timing info... Just pinging this one up. I forgot I'd applied this to my own personal alsa-plugins build and only noticed it when I updated to 1.0.23 upstream version. I've not seen any specific problems with this but also not sure what it fixes. It fixes (at least) the mpg123 startup race (which lead to dropped buffers on an underrun). Is this still applied in Ubuntu Daniel Chen volunteered to do some testing and he found no regressions, so he applied my remove underrun handling patch, and AFAIK it is still applied. I haven't heard of any regressions so far, so I believe it should be pretty safe to upstream. and should we get further review from Lennart when he's got a mo (which is sadly not often in recent months) about the issue with a view to getting it upstreamed? Lennart's, anyone else's opinion, and upstreaming, is very welcome. If you feel I should do something to help this happen, go ahead and tell me. :-) // David ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] New kernel 2.6.34-rc4, no audio
On Sun, 18.04.10 21:09, Colin Guthrie (gm...@colin.guthr.ie) wrote: 'Twas brillig, and Daniel Chen at 18/04/10 20:50 did gyre and gimble: On Sun, Apr 18, 2010 at 2:44 PM, Gene Heskett gene.hesk...@verizon.net wrote: Pulseaudio-vvv is the file you want to click on. I am seeing a file list at http://gene.homelinux.net:85/gene/Genes-os9-stf/ From your posted log file: D: module-udev-detect.c: /dev/snd/controlC0 is accessible: no [...] D: module-always-sink.c: Autoloading null-sink as no other sinks detected. Yup, so for whatever reason we can't access this file. Possibly because it doesn't exist. i.e. your problem is with the alsa setup. Looks more like a perms problem to me. Check if the ACLs are properly set up and follow the user that is logged in and active on the seat. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] New kernel 2.6.34-rc4, no audio
On Sun, 18.04.10 16:34, Gene Heskett (gene.hesk...@verizon.net) wrote: On Sunday 18 April 2010, Colin Guthrie wrote: 'Twas brillig, and Daniel Chen at 18/04/10 20:50 did gyre and gimble: On Sun, Apr 18, 2010 at 2:44 PM, Gene Heskett gene.hesk...@verizon.net wrote: Pulseaudio-vvv is the file you want to click on. I am seeing a file list at http://gene.homelinux.net:85/gene/Genes-os9-stf/ From your posted log file: D: module-udev-detect.c: /dev/snd/controlC0 is accessible: no [...] D: module-always-sink.c: Autoloading null-sink as no other sinks detected. Yup, so for whatever reason we can't access this file. Possibly because it doesn't exist. i.e. your problem is with the alsa setup. Col IIRC that particular config didn't pre-allocate the oss stuff, and wasn't building any oss compat stuffs either. Is that related? I don't know if the one that works does, from the working .config: This has nothing to do with OSS. I generally recommend using distribution kernels, since they are usually compiled in a way that most things like this work. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulse audio does not work with my hdmi output
On Sat, 17.04.10 01:03, Dark Shadow (shadowofdarkn...@gmail.com) wrote: With todays Alsa 1.0.23 release I finally have working HDMI audio on my laptop with the exception of through Pulse Audio. mplayer video.mkv -ao alsa:device=plughw=1.3 works perfect, but when I set Pulse Audio to output to my hdmi device I get silence with the occasional popping sound. Well, plughw:1,3 is a hack, and specific to your hardware. Normally the hdmi:1 device should work right-away. If it doesn't, then this is an ALSA problem. Note that HDMI on Linux is still very shaky ground and little tested. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulse audio does not work with my hdmi output
On Sat, 17.04.10 03:51, Dark Shadow (shadowofdarkn...@gmail.com) wrote: Ok I found out more, it can work but I have to do a step first. My testing before was pulseaudio then alsa but I never went back to notice that pulse started working. It seems on my hdmi output that after ever boot I have to use 1,9 first then it initializes 1,3 1,7 1,8 and they work fine after that. So all I need to know is how can I force Pulse Audio to use plughw:1,9 always instead of the first detected 1,3? Specifying device indexes in addition to card indexes is highly card dependant. If other device indexes need to be used, then the hdmi:xxx string needs to be fixed in ALSA. PA will then automatically pick up things the right away. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] My computer thinks I'm schizophrenic, is PA for me?
On Fri, 16.04.10 21:02, Jan Braun (janbr...@gmx.de) wrote: Hi list, and sorry for bringing up this topic again, but I'm another user who has difficulties with PA's multi-user policy. You see, currently I'm the only person with access to my desktop pc, but I have several user accounts on it[1]. And I use them all. Simultaneously. As in: several consoles open, often more than 1 xserver running, You know, they invented window managers that support multiple workspaces. Fantastic stuff. You should try it once. xterms ssh'd to otheru...@localhost . Why would you ssh to the local machine? Anyway, having one user with a split personality and hence is actually five users is certainly nothing I designed PA for. Sorry, Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] My computer thinks I'm schizophrenic, is PA for me?
On Sat, 17.04.10 16:42, Jan Braun (janbr...@gmx.de) wrote: My suggestion is basically the same as your option 3, without the double mixing and tcp overhead (I'm not sure whether using the loopback interface has much more overhead than unix domain sockets, though - you still won't be able to use shared memory for audio transport). Hmm, why not? I've set up PA as you describe (except for the additional auth-group parameter), and PA is creating entries in /dev/shm , even for other users than albert. The PA client libs always allocate their memory from an shm region, regardless whether it is later used for data transfer or not. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] My computer thinks I'm schizophrenic, is PA for me?
On Sat, 17.04.10 18:28, Tanu Kaskinen (ta...@iki.fi) wrote: On Sat, 2010-04-17 at 16:42 +0200, Jan Braun wrote: Hmm, why not? I've set up PA as you describe (except for the additional auth-group parameter), and PA is creating entries in /dev/shm , even for other users than albert. Oh, maybe shm does work? I assumed that the logic was that only connections from the same user could use shm, but maybe the logic is that shm is forcibly disabled only in the system wide mode. We do compare the local and remote uid and refuse SHM if they don't match. On top of that we always disable SHM for root. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulse audio does not work with my hdmi output
Must be since I just remembered to try aplay with a capital L and you notice that nothing other then the basic info shows up. Strange that Pulse works at all but then again I am just a end user and don't know how stuff works #aplay -L null Discard all samples (playback) or generate zero samples (capture) default:CARD=Intel HDA Intel, ALC889 Analog Default Audio Device front:CARD=Intel,DEV=0 HDA Intel, ALC889 Analog Front speakers surround40:CARD=Intel,DEV=0 HDA Intel, ALC889 Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=Intel,DEV=0 HDA Intel, ALC889 Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=Intel,DEV=0 HDA Intel, ALC889 Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=Intel,DEV=0 HDA Intel, ALC889 Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=Intel,DEV=0 HDA Intel, ALC889 Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers iec958:CARD=Intel,DEV=0 HDA Intel, ALC889 Digital IEC958 (S/PDIF) Digital Audio Output hdmi:CARD=NVidia HDA NVidia, NVIDIA HDMI HDMI Audio Output ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Getting cork notifications/subscritpions for other streams
On Thu, 15.04.10 09:05, Colin Guthrie (gm...@colin.guthr.ie) wrote: Hi Lennart, I've looked at the API, but maybe I was too drunk... Is there any way that I can get a subscription callback or similar when a stream is corked? Due to the nature of this integration, the playback stream itself is actually hidden from me... so I cannot check pa_stream_is_corked() or anything like that. We currently expose no information about that, but we probably could add that to the sink_input_info data. Ideally it would just be another subscription that I could subscribe to. Is this possible? If not, is there a reason it's not, and if there is no reason, would you mind if I implemented it :) What would you use this for? Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] [alsa-devel] pulseaudio eats 19% CPU power in Fedora 12
On Wed, 14.04.10 15:56, Wu Fengguang (fengguang...@intel.com) wrote: Hi Lennart, We found that pulseaudio eats CPU ~19% CPU time, a little more than mplayer when playing video. This is horrible for laptop batteries. This is not a particularly useful report. You know, this can have so many different reasons, the only thing I can really say, is that you can rest assured that it is not supposed to eat that much in normal use. The CPU usage of PA is primarily dependant of the latency requested by the clients. Low latency means high CPU load. Lower latency means higher CPU load. Try pacmd list-sink-inputs to figure out the latency the various applications requested. Then there can be driver problems, where the timing information is not entirely correct that ALSA passes on to, with the result that we get dropouts where we shouldn't, with the results that we shorten our sleep times, with the final effect that the CPU usage goes up. Of course, if PA is used resampling and suchlike is moved from the clients into the sound server and hence will be added to its CPU usage. And PA uses a better resampler by default than ALSA traditionally did, hence the CPU use will be a bit higher than plain ALSA. And then of course, the CPU usage depends on the CPU used. Is this some embedded hardware? In summary: if you want to know what is going on, you need a suitable tool, like a profiler and do the dirty work to figure out what is going on. Just saying 19% is not helpful to figure out what is going on. On my machine here it uses 3% CPU while playing. Can we make it just work -- in green CPU mode? Yes, sure. If you use pacat you can play audio with almost zero CPU usage, because it is one of the few clients that actually asks for sensible latency (2s), which allows us to minimize the wakeup intervals to less than a second. I can find many users complaining about this, and it seems like some fix is available in this link: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/207135 Fix? Where? Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] [alsa-devel] pulseaudio eats 19% CPU power in Fedora 12
On Sun, Apr 18, 2010 at 11:28 PM, Lennart Poettering mzn...@0pointer.de wrote: On Wed, 14.04.10 15:56, Wu Fengguang (fengguang...@intel.com) wrote: I can find many users complaining about this, and it seems like some fix is available in this link: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/207135 Fix? Where? Sigh, another drivel of a bug report with a mis-summary. It really ought to be For Ubuntu 9.04, the sampler was changed to X. (Note that it's speex-float-1 in 9.10 and newer.) I have seen plenty of bugs in hardware, some of which can be worked around in the driver -- for these I've been pushing patches here and to stable@ -- but, like Lennart suggests, these are by no means *caused* by PulseAudio. Best, -Dan ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] New kernel 2.6.34-rc4, no audio
On Sunday 18 April 2010, Lennart Poettering wrote: On Sun, 18.04.10 21:09, Colin Guthrie (gm...@colin.guthr.ie) wrote: 'Twas brillig, and Daniel Chen at 18/04/10 20:50 did gyre and gimble: On Sun, Apr 18, 2010 at 2:44 PM, Gene Heskett gene.hesk...@verizon.net wrote: Pulseaudio-vvv is the file you want to click on. I am seeing a file list at http://gene.homelinux.net:85/gene/Genes-os9-stf/ From your posted log file: D: module-udev-detect.c: /dev/snd/controlC0 is accessible: no [...] D: module-always-sink.c: Autoloading null-sink as no other sinks detected. Yup, so for whatever reason we can't access this file. Possibly because it doesn't exist. i.e. your problem is with the alsa setup. Looks more like a perms problem to me. Check if the ACLs are properly set up and follow the user that is logged in and active on the seat. Lennart Well, ATM it is working, but the /dev/snd devices: g...@coyote /]$ ls -l /dev/snd total 0 drwxr-xr-x 2 root root 60 2010-04-18 07:47 by-path/ crw-rw+ 1 root audio 116, 0 2010-04-18 07:47 controlC0 crw-rw+ 1 root audio 116, 4 2010-04-18 07:47 hwC0D0 crw-rw+ 1 root audio 116, 8 2010-04-18 07:47 midiC0D0 crw-rw+ 1 root audio 116, 9 2010-04-18 07:47 midiC0D1 crw-rw+ 1 root audio 116, 24 2010-04-18 23:44 pcmC0D0c crw-rw+ 1 root audio 116, 16 2010-04-18 23:44 pcmC0D0p crw-rw+ 1 root audio 116, 25 2010-04-18 07:47 pcmC0D1c crw-rw+ 1 root audio 116, 26 2010-04-18 07:47 pcmC0D2c crw-rw+ 1 root audio 116, 18 2010-04-18 07:47 pcmC0D2p crw-rw+ 1 root audio 116, 19 2010-04-18 07:47 pcmC0D3p crw-rw+ 1 root audio 116, 1 2010-04-18 07:47 seq crw-rw+ 1 root audio 116, 33 2010-04-18 07:47 timer [g...@coyote /]$ And that is after killing the daemon with killall as root, and restarting it as me, gene with a pulseaudio -vvv and getting several screens of output. Is that the right perms? Thanks -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) You will wish you hadn't. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Standardising on the amount of software amplification is presented to the user
On Wed, 14.04.10 11:38, Colin Guthrie (gm...@colin.guthr.ie) wrote: In VLC the 400% relates to a +6dB overdrive so a +3dB for them is 200% (and one of their devs said to me that he didn't think that anything over +3dB should be shown to the user). Perhaps even this is too far? In PA +6dB is at 125% or so (with the current mapping algorithm). Ahh good. I figured it wouldn't be 400% in PA, but hadn't done the actual sums :) Hmm, one more addition to this. I find myself pulling up the volume slider to the full 150% exposed in g-v-c from time to time when using unamplified headphones on a USB sound card on a movie, and I am kinda happy that I can do that. That's +10dB (amplitude) or so. So limiting things to +6dB looks a bit too low for me. We currently use the same cubic mapping both below and above 100%. I am not sure that is even a good choice, and if we shouldn't change that one of those days. From what I've discussed with the VLC guys this morning (and I wont pretend to fully grok all the mappings involved) they seem to suggest a +3dB = 200% and a +6dB = 400%. This seems to me like they've used a linear mapping and that they use 10log(x) rather than 20log(x) which is normally used for sound pressure (as far as I understand it - which is admittedly limited). Hmm, their dB scale is based on power, not amplitude. As it seems. Interesting choice, but I am kinda sure that most vol controls focus on amplitude, not power. And PA does too. And ALSA as well. Choosing a linear mapping is a pretty bad choice, so much as definite. http://www.robotplanet.dk/audio/audio_gui_design/ http://lists.linuxaudio.org/pipermail/linux-audio-dev/2009-May/thread.html#23151 #define PA_VOLUME_OVERDRIVE (PA_VOLUME_NORM+PA_VOLUME_NORM/2) OK, so if I've done my sums right (150% = 1.5 relative to PA_VOLUME_NORM = linear[1.5^3] = linear[3.375] = dB[20*log(3.375)] = db[20*0.528] = db[10.57]) we could actually do: #define PA_VOLUME_OVERDRIVE (pa_sw_volume_from_dB(+10.57f)) This will map to the current 150% used by g-v-c. e.g. this is the amount by which it currently allows overdrive. Yepp, that is true. Though this is actually a double, not a float, the 'f' should go. So the real question is, what should the overdrive dB value be? The 3dB or 6dB currently supported in vlc's UI or something we define ourselves. I agree that making it a dB value is sensible tho' ;) I am quite happy with the current mapping in g-v-c to be honest, and so far I haven't heard any complaints that it was too little. So to make things clean we could just say +11dB (amplitude) as max. And claim this is the ultimate truth. ;-) #ifndef PA_VOLUME_OVERDRIVE # define PA_VOLUME_OVERDRIVE (pa_sw_volume_from_dB(+10.57f)) #endif So that I can use the new constant in the code to replace any hardcoded (1.5*PA_VOLUME_NORM)s or just PA_VOLUME_NORMs on their own depending on app. Does that seem sensible? Yes, absolutely. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] New kernel 2.6.34-rc4, no audio
On Sunday 18 April 2010, Lennart Poettering wrote: On Sun, 18.04.10 16:34, Gene Heskett (gene.hesk...@verizon.net) wrote: On Sunday 18 April 2010, Colin Guthrie wrote: 'Twas brillig, and Daniel Chen at 18/04/10 20:50 did gyre and gimble: On Sun, Apr 18, 2010 at 2:44 PM, Gene Heskett gene.hesk...@verizon.net wrote: Pulseaudio-vvv is the file you want to click on. I am seeing a file list at http://gene.homelinux.net:85/gene/Genes-os9-stf/ From your posted log file: D: module-udev-detect.c: /dev/snd/controlC0 is accessible: no [...] D: module-always-sink.c: Autoloading null-sink as no other sinks detected. Yup, so for whatever reason we can't access this file. Possibly because it doesn't exist. i.e. your problem is with the alsa setup. Col IIRC that particular config didn't pre-allocate the oss stuff, and wasn't building any oss compat stuffs either. Is that related? I don't know if the one that works does, from the working .config: This has nothing to do with OSS. I generally recommend using distribution kernels, since they are usually compiled in a way that most things like this work. Lennart Unforch Lennart, the distro kernels drm is old, and that drives my monitor into un-controlled fits of blanking, off for 3-4 seconds, on for 50ms, back off again, anytime some small window touches the right edge of the screen, sometimes even the mouse cursor triggers it. I have been putting up with this, even filed bz reports for nearly 2 years, and I'm understandably ecstatic that a drm fix that went in with 2.6.34-rc1 has finally fixed that problem. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) The universe is an island, surrounded by whatever it is that surrounds universes. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] New kernel 2.6.34-rc4, no audio
On Sun, 18.04.10 23:48, Gene Heskett (gene.hesk...@verizon.net) wrote: g...@coyote /]$ ls -l /dev/snd total 0 drwxr-xr-x 2 root root 60 2010-04-18 07:47 by-path/ crw-rw+ 1 root audio 116, 0 2010-04-18 07:47 controlC0 crw-rw+ 1 root audio 116, 4 2010-04-18 07:47 hwC0D0 crw-rw+ 1 root audio 116, 8 2010-04-18 07:47 midiC0D0 crw-rw+ 1 root audio 116, 9 2010-04-18 07:47 midiC0D1 crw-rw+ 1 root audio 116, 24 2010-04-18 23:44 pcmC0D0c crw-rw+ 1 root audio 116, 16 2010-04-18 23:44 pcmC0D0p crw-rw+ 1 root audio 116, 25 2010-04-18 07:47 pcmC0D1c crw-rw+ 1 root audio 116, 26 2010-04-18 07:47 pcmC0D2c crw-rw+ 1 root audio 116, 18 2010-04-18 07:47 pcmC0D2p crw-rw+ 1 root audio 116, 19 2010-04-18 07:47 pcmC0D3p crw-rw+ 1 root audio 116, 1 2010-04-18 07:47 seq crw-rw+ 1 root audio 116, 33 2010-04-18 07:47 timer [g...@coyote /]$ And that is after killing the daemon with killall as root, and restarting it as me, gene with a pulseaudio -vvv and getting several screens of output. Is that the right perms? You need to check the ACLs: see getfacl(1). Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] New kernel 2.6.34-rc4, no audio
On Sunday 18 April 2010, Lennart Poettering wrote: On Sun, 18.04.10 23:48, Gene Heskett (gene.hesk...@verizon.net) wrote: g...@coyote /]$ ls -l /dev/snd total 0 drwxr-xr-x 2 root root 60 2010-04-18 07:47 by-path/ crw-rw+ 1 root audio 116, 0 2010-04-18 07:47 controlC0 crw-rw+ 1 root audio 116, 4 2010-04-18 07:47 hwC0D0 crw-rw+ 1 root audio 116, 8 2010-04-18 07:47 midiC0D0 crw-rw+ 1 root audio 116, 9 2010-04-18 07:47 midiC0D1 crw-rw+ 1 root audio 116, 24 2010-04-18 23:44 pcmC0D0c crw-rw+ 1 root audio 116, 16 2010-04-18 23:44 pcmC0D0p crw-rw+ 1 root audio 116, 25 2010-04-18 07:47 pcmC0D1c crw-rw+ 1 root audio 116, 26 2010-04-18 07:47 pcmC0D2c crw-rw+ 1 root audio 116, 18 2010-04-18 07:47 pcmC0D2p crw-rw+ 1 root audio 116, 19 2010-04-18 07:47 pcmC0D3p crw-rw+ 1 root audio 116, 1 2010-04-18 07:47 seq crw-rw+ 1 root audio 116, 33 2010-04-18 07:47 timer [g...@coyote /]$ And that is after killing the daemon with killall as root, and restarting it as me, gene with a pulseaudio -vvv and getting several screens of output. Is that the right perms? You need to check the ACLs: see getfacl(1). Lennart Okaay, looks like the same info, different format: [r...@coyote linux-2.6.34-rc3]# getfacl /dev/snd getfacl: Removing leading '/' from absolute path names # file: dev/snd # owner: root # group: root user::rwx group::r-x other::r-x And [r...@coyote linux-2.6.34-rc3]# getfacl /dev/snd/controlC0 getfacl: Removing leading '/' from absolute path names # file: dev/snd/controlC0 # owner: root # group: audio user::rw- user:gene:rw- group::rw- mask::rw- other::--- ??? Teach please, thanks. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) There's no real need to do housework -- after four years it doesn't get any worse. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
