Re: [pulseaudio-discuss] PulseAudio module-rtp-recv
Please use the PulseAudio mailing list for these kind of questions. I'll be reading and answering there. 2011/2/23 ericlesoll ericles...@gmail.com: Hi Maarten, Thanks for your job, I reported some bugs on Launchpad about PulseAudio module-rtp-recv, and I saw that you have commited 6 weeks ago some modification. The bug is that the sound go transforming after 55s. We use this module in association with module-rtp-send to make a chat audio piloting by itALC in our project LLSOLL / LESOLL that is open source digital language laboratory. We don't use loopack module due to the delay to big, we use HAL for loopback. Do you have a link for this bug? It sound like the problem my patches should solve. I download the git://git.0pointer.de/pulseaudio.git on Ubuntu 10.10 and I compiled without error output. I replaced my original module-rtp-recv.so by the fresh one then I run ldconfig. When I launch $ pactl load-module module-rtp-recv, I get a number ID without error but I ear no sound. I replace by the old one it's working until 55s then the sound go transforming. I'm not sure that's the way it's supposed to work. You better do a make install and then run /usr/local/bin/pulseaudio - and then LD_LIBRARY_PATH=/usr/local/lib /usr/local/bin/pactl load-module module-rtp-recv, or something similar. In general you can't expect modules compiled for one version of pulse to work in another version. Have ou some idea ? Have to upgrade others modules ? Can I send you log file when I launch module rtp-recv (I don't know how to log it, because -v option is not available) ? Start pulseaudio manually, like I wrote above. You probably mean that the -v options is not available for the /etc/init.d/pulseaudio script. Best regards Eric Maarten ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Questions about no ports available to select.
On 2011-02-23 04:19, fykc...@gmail.com wrote: Hi David, Thanks for your reply! 2011/2/22 David Henningssondavid.hennings...@canonical.com Your log indicates your HDA codec is a Conexant ID 506e - the Conexant driver does not yet support this codec, so the driver falls back to a generic driver. I intend to make a new attempt later this week to add a quirk for that particular chip. If you, in the meantime, could point me to a bug in Launchpad (filed with the ubuntu-bug audio command), that would be helpful, as that would include valuable codec info. Thanks! I'm not running ubuntu, just using that package from ubuntu, so no that command, sorry. Ok, alsa info works just as well, see wiki.ubuntu.com/Audio/AlsaInfo The codec is Conexant CX20671-21Z, id is '0x14f1506e'. I did some hacks, none works: * Switch the driver to latest one (embemed in linux 2.6.38-rc6) * Add an entry for 0x14f1506e, using patch_conexant_auto or patch_cxt5066 I just sent an entry for 506e upstream to alsa-devel. You might need a second quirk on top of that, just like I added for the Dell machines, see http://mailman.alsa-project.org/pipermail/alsa-devel/2011-February/037157.html BTW, I can see ports in alsamixer (for capture: mic1, mic2, mic3), which they can't be enumerated by PA? I can't tell without having alsa-info but you might to be helped by my input mixer rewrite, which I'm still trying to get tested and committed into PulseAudio. -- David Henningsson, Canonical Ltd. http://launchpad.net/~diwic ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Questions about no ports available to select.
'Twas brillig, and David Henningsson at 23/02/11 13:03 did gyre and gimble: my input mixer rewrite, which I'm still trying to get tested and committed into PulseAudio Oh yeah, let's discuss that at the meeting tomorrow too. Added to agenda. Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] 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] A2DP - Bluetooth source to alsa sink audio routing
Please keep the conversation on the mailing list. (though it looks like I forgot to do that too) 2011/2/23 Cristina Cristea doina.crist...@gmail.com: No, the glitches are now more rarely and smaller. But, after 31 minutes of playing (with only one small glitch, bearly audible, on min 27), PulseAudio started to display a lot of underrun messages and died. Died, as in crashed? Verbose log output would be interesting here. Most likely the CPU load limiter kicked in and pulse shut itself down. Also, module-loopback causes PulseAudio to be a a very big CPU consumer on my system-like about 80%. That should not be. Can you get this behaviour also without module-loopback? (e.g. by recording from the bluetooth source with parec) For further information on how to debug this, see http://pulseaudio.org/wiki/HowToDebugCPULoadBugs I'll do more testing these days and see if I can improve. Thanks for support and I really appreciate what you guys are doing. Cristina I'll do more testing the Maarten On 02/22/2011 09:36 PM, Maarten Bosmans wrote: 2011/2/22 Cristina Cristeadoina.crist...@gmail.com: Thanks Maarten, that really makes the sample rate adjustment to not be noticed by the listener. Unfortunately, I still get the underrun issues. Here is a log snippet: Do the underruns still occur after a minute of playing? Do they result in audible glitches? As I mentioned in the mail that went with these patches a couple of weeks ago, I have not tested it on any non-trivial module-loopback setup (e.g. bluetooth source to alsa sink), so some underrun problems can indeed still be expected. Maarten ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] pavucontrol. Also Nvidia HDMI
Hi, first I'd like to ask if pavucontrol is still maintained, as the last release seems to be from 2009. If it's not, what is currently considered the official way to adjust PA? If it is: what could be the cause for an application-icon becoming this big: http://img200.imageshack.us/img200/4872/screenshotax.png It's an svg, shows correctly in systray and compiz alt+tab. My second question is about sound over hdmi with an Nvidia GTX460 (NVC4 /GF104 family): aplay -L gives hdmi:CARD=NVidia,DEV=0 - pcm3p/ hdmi:CARD=NVidia,DEV=1 - pcm7p/ hdmi:CARD=NVidia,DEV=2 - pcm8p/ hdmi:CARD=NVidia,DEV=3 - pcm9p/ but only pcm7p actually does anything. So currently I use load-module module-alsa-sink device=hw:1,7 to add a sink, but PA automatically adds pcm3p as GF104 High Definition Audio Controller Digital Stereo (HDMI), so I effectively have two nvidia-hdmi sinks, one of which does absolutely nothing. Is there any way to disable the automatically added sink OR define which device to chose as default? I'm sorry if this question has been widely discussed. Regards. Christopher K. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] pavucontrol. Also Nvidia HDMI
'Twas brillig, and Christopher K. at 22/02/11 00:46 did gyre and gimble: Hi, first I'd like to ask if pavucontrol is still maintained, as the last release seems to be from 2009. It is, just no releases for a while. I will be taking over releases for it in the near term, so expect a release soonish. Last commits were fairly recent (in Dec). See: http://git.0pointer.de/?p=pavucontrol.git If it's not, what is currently considered the official way to adjust PA? Well pavucontrol is a bit of a toy utility really. It wont win any HCI or design awards, but it is rather functional. Most of the time we would recommend using the tools provided by your Desktop Environment (i.e. both Gnome and KDE have native tools to control PA and there are several other addons developed by e.g. Canonical which fit in with their own desktop products (I'm not super familiar with these however)). If it is: what could be the cause for an application-icon becoming this big: http://img200.imageshack.us/img200/4872/screenshotax.png It's an svg, shows correctly in systray and compiz alt+tab. Hmm, probably just a run of the mill bug in svg handling. Can you post/pastebin the output of pacmd list when this problem occurs? And if possible also send me the .svg itself so I can try and replicate (feel free to send the .svg by private mail or post it on a URL somewhere). My second question is about sound over hdmi with an Nvidia GTX460 (NVC4 /GF104 family): The HDMI stuff on Nvidia has seen a fair bit of action of late both on the alsa-devel lists and here. Probably best to ask in a separate thread rather than combining issues. That way people can reply in context and it's easier to follow any resulting thread. Also, you are not subscribed to this list. Please subscribe or you may end up missing some replies. Alternative you can use Gmane.org to read and post via NNTP (that's what I usually do). Cheers Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] 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] Add a target to the PA log feature and improve PA log core
Here's my review of that patch. It will be handled in the meeting tomorrow, but I'm sure I've forgotten by then, so I sent it to the list. 2010/11/22 Becker, VincentX vincentx.bec...@intel.com: Hi all, Could you please review this patch ? This is a patch that adds a generic log target for PA log (log.c). This new target can be either a char device or a regular file. For our remote log device needs, it has been necessary to directly log Pulseaudio traces to a file descriptor. Also optimizations in the memory allocations have been done to reuse local pointers to prevent extra memory allocations (on stack or heap), that would happen in case of very big trace buffers, and that could potentially have an impact on audio latency in embedded systems. Modifications : src/daemon/cmdline.c : Update Pulseaudio help and error message for the 'log-target' command argument. The current help message has a width of 80 characters. It would be nice to keep it that way and find another way to fit the new log-target argument in there. src/daemon/daemon-conf.c : Add the condition when the target given is a file name given with relative or absolute path. If the file already exists, it creates a new file that will contain the current date and time inserted in the name. For this purpose, two static utilities functions have been added. The file descriptor is then passed to the PA log in pulsecore. I don't think the renaming with the data appended to the filename is functionality that belongs in pulseaudio. If you want serious logging, use syslog, if you want quick-and-dirty, use the filename. Pulse should just append or overwrite the file, either is fine. Also, as daemon-conf opens the file, it should call pa_close itself too. Then the pa_log_close_fd function can be removed. src/pulsecore/log.c : The function pa_log_levelv_meta formats the text data and sends it to the appropriate target. There are 2 main changes : 1) Add the target PA_LOG_FILED which allows to write the formatted log data to a file descriptor output. Add functions to open and close that file descriptor. This would better be called PA_LOG_FD 2) the algorithms around 'char *t' have been reordered in order to optimize memory use. This could be useful when traces are big. The trace buffer char text has been set to 16*1024Kb which allocates already 16Kb on the stack. This buffer is then copied into t, in the for loop that checks for carriage returns. What needed to be optimized is that extra memory is allocated in case of metadata (location and timestamp) is prepended to t, by creating dynamically a new buffer. The idea is to prepend the data directly into t (and append if it's the case) before we affect the value of 'text'. It avoids one dynamic memory allocation, at least in the case of the new target PA_LOG_FILED. Therefore, a 'metadata' buffer is created and prepended in t whatever the target. One switch/case is actually added to build this metadata buffer and we keep the other one just for write the actual log (text+metadata) in the target. Please separate this change out in another patch. That way it can be reviewed better. P.S. : there are bad indentations due to tabs. I use emacs and tried the indentation Lisp function given here but without success : http://www.pulseaudio.org/wiki/CodingStyle . It keeps putting tabs instead of spaces ! How could I solve that ? Thanks, Vincent Maarten Vincent BECKER Intel - Wireless System Integration Engineer Medfield platform - Intel Corporation SAS (French simplified joint stock company) Registered headquarters: Les Montalets- 2, rue de Paris, 92196 Meudon Cedex, France Registration Number: 302 456 199 R.C.S. NANTERRE Capital: 4,572,000 Euros This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Ah, to bad you send it to a public list then. I guess we're all criminals now ;-) ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] [PATCH] Add a target to the PA log feature and improve PA log core
Here's my review of that patch. It will be handled in the meeting tomorrow, but I'm sure I've forgotten by then, so I sent it to the list. 2010/11/22 Becker, VincentX vincentx.bec...@intel.com: Hi all, Could you please review this patch ? This is a patch that adds a generic log target for PA log (log.c). This new target can be either a char device or a regular file. For our remote log device needs, it has been necessary to directly log Pulseaudio traces to a file descriptor. Also optimizations in the memory allocations have been done to reuse local pointers to prevent extra memory allocations (on stack or heap), that would happen in case of very big trace buffers, and that could potentially have an impact on audio latency in embedded systems. Modifications : src/daemon/cmdline.c : Update Pulseaudio help and error message for the 'log-target' command argument. The current help message has a width of 80 characters. It would be nice to keep it that way and find another way to fit the new log-target argument in there. src/daemon/daemon-conf.c : Add the condition when the target given is a file name given with relative or absolute path. If the file already exists, it creates a new file that will contain the current date and time inserted in the name. For this purpose, two static utilities functions have been added. The file descriptor is then passed to the PA log in pulsecore. I don't think the renaming with the data appended to the filename is functionality that belongs in pulseaudio. If you want serious logging, use syslog, if you want quick-and-dirty, use the filename. Pulse should just append or overwrite the file, either is fine. Also, as daemon-conf opens the file, it should call pa_close itself too. Then the pa_log_close_fd function can be removed. src/pulsecore/log.c : The function pa_log_levelv_meta formats the text data and sends it to the appropriate target. There are 2 main changes : 1) Add the target PA_LOG_FILED which allows to write the formatted log data to a file descriptor output. Add functions to open and close that file descriptor. This would better be called PA_LOG_FD 2) the algorithms around 'char *t' have been reordered in order to optimize memory use. This could be useful when traces are big. The trace buffer char text has been set to 16*1024Kb which allocates already 16Kb on the stack. This buffer is then copied into t, in the for loop that checks for carriage returns. What needed to be optimized is that extra memory is allocated in case of metadata (location and timestamp) is prepended to t, by creating dynamically a new buffer. The idea is to prepend the data directly into t (and append if it's the case) before we affect the value of 'text'. It avoids one dynamic memory allocation, at least in the case of the new target PA_LOG_FILED. Therefore, a 'metadata' buffer is created and prepended in t whatever the target. One switch/case is actually added to build this metadata buffer and we keep the other one just for write the actual log (text+metadata) in the target. Please separate this change out in another patch. That way it can be reviewed better. P.S. : there are bad indentations due to tabs. I use emacs and tried the indentation Lisp function given here but without success : http://www.pulseaudio.org/wiki/CodingStyle . It keeps putting tabs instead of spaces ! How could I solve that ? Thanks, Vincent Maarten Vincent BECKER Intel - Wireless System Integration Engineer Medfield platform - Intel Corporation SAS (French simplified joint stock company) Registered headquarters: Les Montalets- 2, rue de Paris, 92196 Meudon Cedex, France Registration Number: 302 456 199 R.C.S. NANTERRE Capital: 4,572,000 Euros This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Ah, to bad you send it to a public list then. I guess we're all criminals now ;-) ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] pavucontrol. Also Nvidia HDMI
On 02/21/11 17:46, Christopher K. wrote: My second question is about sound over hdmi with an Nvidia GTX460 (NVC4 /GF104 family): aplay -L gives hdmi:CARD=NVidia,DEV=0 - pcm3p/ hdmi:CARD=NVidia,DEV=1 - pcm7p/ hdmi:CARD=NVidia,DEV=2 - pcm8p/ hdmi:CARD=NVidia,DEV=3 - pcm9p/ but only pcm7p actually does anything. So currently I use load-module module-alsa-sink device=hw:1,7 to add a sink, but PA automatically adds pcm3p as GF104 High Definition Audio Controller Digital Stereo (HDMI), so I effectively have two nvidia-hdmi sinks, one of which does absolutely nothing. Is there any way to disable the automatically added sink OR define which device to chose as default? What you want to do is add probe_mask to your snd-hda-intel module options. If you google nvidia hdmi probe_mask you can find an explanation. For example I have in /etc/modprobe.d/snd_hda_intel.conf: options snd-hda-intel probe_mask=0x102 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] pavucontrol. Also Nvidia HDMI
Christopher K. wrote at Monday, February 21, 2011 5:46 PM: ... My second question is about sound over hdmi with an Nvidia GTX460 (NVC4 /GF104 family): aplay -L gives hdmi:CARD=NVidia,DEV=0 - pcm3p/ hdmi:CARD=NVidia,DEV=1 - pcm7p/ hdmi:CARD=NVidia,DEV=2 - pcm8p/ hdmi:CARD=NVidia,DEV=3 - pcm9p/ but only pcm7p actually does anything. For some background, please see: ftp://download.nvidia.com/XFree86/gpu-hdmi-audio-document/gpu-hdmi-audio.html -- nvpublic ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] [PATCH] Add a target to the PA log feature and improve PA log core
-Original Message- From: Maarten Bosmans [mailto:mkbosm...@gmail.com] Sent: Wednesday, February 23, 2011 3:50 PM To: General PulseAudio Discussion Cc: Becker, VincentX Subject: Re: [pulseaudio-discuss] [PATCH] Add a target to the PA log feature and improve PA log core Here's my review of that patch. It will be handled in the meeting tomorrow, but I'm sure I've forgotten by then, so I sent it to the list. 2010/11/22 Becker, VincentX vincentx.bec...@intel.com: Hi all, Could you please review this patch ? This is a patch that adds a generic log target for PA log (log.c). This new target can be either a char device or a regular file. For our remote log device needs, it has been necessary to directly log Pulseaudio traces to a file descriptor. Also optimizations in the memory allocations have been done to reuse local pointers to prevent extra memory allocations (on stack or heap), that would happen in case of very big trace buffers, and that could potentially have an impact on audio latency in embedded systems. Modifications : src/daemon/cmdline.c : Update Pulseaudio help and error message for the 'log-target' command argument. The current help message has a width of 80 characters. It would be nice to keep it that way and find another way to fit the new log-target argument in there. src/daemon/daemon-conf.c : Add the condition when the target given is a file name given with relative or absolute path. If the file already exists, it creates a new file that will contain the current date and time inserted in the name. For this purpose, two static utilities functions have been added. The file descriptor is then passed to the PA log in pulsecore. I don't think the renaming with the data appended to the filename is functionality that belongs in pulseaudio. If you want serious logging, use syslog, if you want quick-and-dirty, use the filename. Pulse should just append or overwrite the file, either is fine. Also, as daemon-conf opens the file, it should call pa_close itself too. Then the pa_log_close_fd function can be removed. src/pulsecore/log.c : The function pa_log_levelv_meta formats the text data and sends it to the appropriate target. There are 2 main changes : 1) Add the target PA_LOG_FILED which allows to write the formatted log data to a file descriptor output. Add functions to open and close that file descriptor. This would better be called PA_LOG_FD 2) the algorithms around 'char *t' have been reordered in order to optimize memory use. This could be useful when traces are big. The trace buffer char text has been set to 16*1024Kb which allocates already 16Kb on the stack. This buffer is then copied into t, in the for loop that checks for carriage returns. What needed to be optimized is that extra memory is allocated in case of metadata (location and timestamp) is prepended to t, by creating dynamically a new buffer. The idea is to prepend the data directly into t (and append if it's the case) before we affect the value of 'text'. It avoids one dynamic memory allocation, at least in the case of the new target PA_LOG_FILED. Therefore, a 'metadata' buffer is created and prepended in t whatever the target. One switch/case is actually added to build this metadata buffer and we keep the other one just for write the actual log (text+metadata) in the target. Please separate this change out in another patch. That way it can be reviewed better. P.S. : there are bad indentations due to tabs. I use emacs and tried the indentation Lisp function given here but without success : http://www.pulseaudio.org/wiki/CodingStyle . It keeps putting tabs instead of spaces ! How could I solve that ? Thanks, Vincent Maarten Thanks for your review Maarten. So you suggest to split this into several patches (2). One for the outer implementation and the other for the inner one. I will try to attend to the irc meeting tomorrow so I can catch your remarks in real time. Cheers, V. Vincent BECKER Intel - Wireless System Integration Engineer Medfield platform Ah, to bad you send it to a public list then. I guess we're all criminals now ;-) :-) ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss - Intel Corporation SAS (French simplified joint stock company) Registered headquarters: Les Montalets- 2, rue de Paris, 92196 Meudon Cedex, France Registration Number: 302 456 199 R.C.S. NANTERRE Capital: 4,572,000 Euros This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de
Re: [pulseaudio-discuss] [RFC] Passthrough support
On Tue, Feb 22, 2011 at 2:52 PM, Tanu Kaskinen ta...@iki.fi wrote: On Wed, 2011-02-23 at 01:00 +0530, Arun Raghavan wrote: On Tue, 2011-02-22 at 13:27 -0600, pl bossart wrote: ok. Looks good. One last comment on proplists. If we don't define a set of mandatory elements, then it's going to be really hard to use this pa_stream_new_extended() routine. How will the client figure out what exactly it needs to send for each format? I was thinking that his would basically develop as convention, though the few basic properties (rate, channels) could be documented along with the pa_encoding_t structure. We can document additional properties (for example bitrate, if some sink ever needs it) as being optional but recommended if available. The set of parameters can potentially grow forever - we don't know what parameters may become relevant in the future. So, I think we should start by documenting the parameters that we know are important today, and define the approach for adding new parameters in the future. I suggest we first work with known mandatory parameters such as sampling freq and nb of channels. The connection fails if these parameters are not set. That's enough to make passthrough work for now. Future extensions can be worked out later. let's not fall into academic debates. -Pierre ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] [PATCH] Add a target to the PA log feature and improve PA log core
2011/2/23 Becker, VincentX vincentx.bec...@intel.com: Thanks for your review Maarten. So you suggest to split this into several patches (2). One for the outer implementation and the other for the inner one. I will try to attend to the irc meeting tomorrow so I can catch your remarks in real time. I'm not sure what you mean by outer and inner implementation. What I meant was one patch thats adds the option to log to a file (this patch touches all four files) and one patch that does the metadata, append_data thing (should only change src/pulsecore/log.c) Having two clean patches (see my other comments) tomorrow would help to keep thing moving in the meeting. Sorry for getting this rolling on such a short notice. Maarten Cheers, V. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] pavucontrol. Also Nvidia HDMI
Thanks Stephen, probe_mask=-1,0x2 works fine for me. I thought this was a pulse-issue, but apparently it's more complex than that. I happen to use pavumixer all the time, the gnome sound-preferences work but screw up read/front and left/right for me. Seems more intuitive and well-designed to me than any other mixer-app so far! I'm going to send the icon in question to Colin. Christopher ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Questions about no ports available to select.
Hi David, Thanks for your work! 2011/2/23 David Henningsson david.hennings...@canonical.com Ok, alsa info works just as well, see wiki.ubuntu.com/Audio/AlsaInfo Collected, see the attachment. I just sent an entry for 506e upstream to alsa-devel. You might need a second quirk on top of that, just like I added for the Dell machines, see http://mailman.alsa-project.org/pipermail/alsa-devel/2011-February/037157.html I tried it, but not work for me. I doubt my 506e is not the one you mentioned: 1. The vendor told me it's a Conexant 'CX20671-21Z', but yours is 'CX20590'. 2. patch_conexant_auto works better than patch_cxt5066, the former doesn't break playback and bring PA sink ports, but still no source ports. -- Regards, - cee1 upload=truescript=truecardinfo= !! !!ALSA Information Script v 0.4.60 !! !!Script ran on: Thu Feb 24 09:23:36 UTC 2011 !!Linux Distribution !!-- Debian GNU/Linux squeeze/sid \n \l !!DMI Information !!--- Manufacturer: Product Name: Product Version: !!Kernel Information !!-- Kernel release:2.6.36+ Operating System: GNU/Linux Architecture: mips64 Processor: unknown SMP Enabled: Yes !!ALSA Version !! Driver version: 1.0.23 Library version:1.0.23 Utilities version: 1.0.23 !!Loaded ALSA modules !!--- !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes ESound Daemon: Installed - Yes (/usr/bin/esd) Running - No !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0x1420 irq 5 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) !!Advanced information - PCI Vendor/Device/Subsystem ID's !! 00:14.2 0403: 1002:4383 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- !!Modprobe options (Sound related) !! snd-atiixp-modem: index=-2 snd-intel8x0m: index=-2 snd-via82xx-modem: index=-2 snd-pcsp: index=-2 snd-usb-audio: index=-2 !!Loaded sound module options !!-- !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Conexant ID 506e Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x14f1506e Subsystem Id: 0x14f10101 Revision Id: 0x10 No Modem Function Group found Default PCM: rates [0x160]: 44100 48000 96000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A GPIO: io=4, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x10 [Audio Output] wcaps 0xc1d: Stereo Amp-Out R/L Control: name=Master Playback Switch, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Control: name=Master Playback Volume, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name=HDA Generic, type=Audio, device=0 Amp-Out caps: ofs=0x4a, nsteps=0x4a, stepsize=0x03, mute=1 Amp-Out vals: [0x4a 0x4a] Converter: stream=5, channel=0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 D3cold EPSS Power: setting=D0, actual=D0 Node 0x11 [Audio Output] wcaps 0xc1d: Stereo Amp-Out R/L Amp-Out caps: ofs=0x4a, nsteps=0x4a, stepsize=0x03, mute=1 Amp-Out vals: [0x3c 0x3c] Converter: stream=0, channel=0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 D3cold EPSS Power: setting=D0, actual=D0 Node 0x12 [Audio Output] wcaps 0x611: Stereo Digital Converter: stream=0, channel=0 Digital: Digital category: 0x0 PCM: rates [0x160]: 44100 48000 96000 bits [0xe]: 16 20 24 formats [0x5]: PCM AC3 Power states: D0 D1 D2 D3 D3cold EPSS Power: setting=D0, actual=D0 Node 0x13 [Beep Generator Widget] wcaps 0x7c: Mono Amp-Out Amp-Out caps: ofs=0x07, nsteps=0x07, stepsize=0x0f, mute=0 Amp-Out vals: [0x00] Node 0x14 [Audio Input] wcaps 0x100d1b: Stereo Amp-In R/L Control: name=Capture Source, index=0, device=0 Control: name=Mic Capture Volume, index=0, device=0 ControlAmp: chs=3, dir=In, idx=2, ofs=0 Control: name=Mic 1 Capture Volume, index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Control: name=Mic 2 Capture Volume, index=0, device=0 ControlAmp: chs=3, dir=In, idx=1, ofs=0 Device: name=HDA
Re: [pulseaudio-discuss] Questions about no ports available to select.
On 2011-02-24 03:27, fykc...@gmail.com wrote: Hi David, Thanks for your work! You're welcome! 2011/2/23 David Henningssondavid.hennings...@canonical.com Ok, alsa info works just as well, see wiki.ubuntu.com/Audio/AlsaInfo Collected, see the attachment. I just sent an entry for 506e upstream to alsa-devel. You might need a second quirk on top of that, just like I added for the Dell machines, see http://mailman.alsa-project.org/pipermail/alsa-devel/2011-February/037157.html I tried it, but not work for me. I doubt my 506e is not the one you mentioned: 1. The vendor told me it's a Conexant 'CX20671-21Z', but yours is 'CX20590'. I have no idea of what the real name of the chip is - I picked 20590 because 506e is hexadecimal for 20590. 2. patch_conexant_auto works better than patch_cxt5066, the former doesn't break playback and bring PA sink ports, but still no source ports. From your alsa info I can note the following: 1) The node graph is just like the other 506e:s I've seen, and identical to the 5066 family. So the 506e patch is correct. 2) Given your pin configurations, you should add either options snd-hda-intel model=asus or options snd-hda-intel model=thinkpad to /etc/modprobe.d/alsa-base.conf. That is, in addition to the 506e patch I sent to alsa-devel. 3) For some reason, parsing has gone wrong on finding the PCI subsystem ID. To write a quirk that does model=thinkpad permanently, we'll need the PCI subsystem ID for the HDA Intel device. 4) Architecture: Mips64? Never seen HDA Intel connected to anything but amd64/i386, but I guess it's possible :-) Btw, feel free to move this thread to alsa-devel, as we're into ALSA level stuff rather than PulseAudio stuff. -- David Henningsson, Canonical Ltd. http://launchpad.net/~diwic ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
