[pulseaudio-discuss] Google ChromeOS reinventing the wheel, ignoring PulseAudio
Dear PusleAudio developers, I'd like to let you know that Google ChromeOS recently started a brand new project called ADHD, which from what I can tell aims to do the same thing that PulseAudio already does, bypassing it in favor of interacting directly with ALSA: http://git.chromium.org/gitweb/?p=chromiumos/third_party/adhd.git;a=summary http://git.chromium.org/gitweb/?p=chromiumos/third_party/adhd.git;a=commit;h=8982204dee44ece1cef2178747a27f08beb374cf Perhaps it is worth trying to convince the Google ChromeOS developers to instead build/improve/adapt PulseAudio for their needs? It would seem that would benefit everybody by preventing fragmentation in the Free Software stack. Thanks, Vlad ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] [ANNOUNCE] PulseAudio 1.0
On Tue, 2011-09-27 at 10:37 +0100, Colin Guthrie wrote: Hi! Yup, that's right it's 1.0 time at last. So this has been a long time coming, but finally it's out there! I've covered a lot of things already in the previous release notes and we have a fairly extensive summary of things over on the release notes page here: http://pulseaudio.org/wiki/Notes/1.0 The Trac instance on pulseaudio.org is crying in a corner again. While it recovers, the same notes are available at http://www.freedesktop.org/wiki/Software/PulseAudio/Notes/1.0 Cheers, Arun ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Google ChromeOS reinventing the wheel, ignoring PulseAudio
Le mardi 27 septembre 2011 17:27:14 Arun Raghavan, vous avez écrit : Do you have any more details? Seems to be more of a policy daemon than an audio server. Isn't audio policy daemon just a fancier name for (modern) audio server? Does PulseAudio not implement audio policy? Sure, PulseAudio certainly does not police video devices. That's partly done by the X server (XVideo grabs), partly by the window manager, but mostly not done at all. But still... -- Rémi Denis-Courmont http://www.remlab.net/ http://fi.linkedin.com/in/remidenis ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] pulseaudio-discuss Digest, Vol 5, Issue 52
Hello Everybody, First of all Congrajulations on the release. Hopefully, we will turn in some patches soon. Please see additional comments inline. Date: Mon, 26 Sep 2011 20:41:26 +0100 From: Colin Guthrie gm...@colin.guthr.ie Subject: Re: [pulseaudio-discuss] No audio heard from loopback To: pulseaudio-discuss@lists.freedesktop.org Message-ID: j5qkh2$m66$1...@dough.gmane.org Content-Type: text/plain; charset=UTF-8 'Twas brillig, and Sriram Gopalan at 26/09/11 19:35 did gyre and gimble: We are facing an issue with loopback in pulse audio 0.9.22 Just as a standard approach I'd generally recommend, have you tried 0.9.23? it includes several fixes that could certainly help. If you wait a day, you can also try the shiney new 1.0 release which will be escaping very soon [Sriram] Certainly Col -- Date: Mon, 26 Sep 2011 22:02:41 +0200 From: Maarten Bosmans mkbosm...@gmail.com Subject: Re: [pulseaudio-discuss] No audio heard from loopback To: General PulseAudio Discussion pulseaudio-discuss@lists.freedesktop.org Message-ID: ca+cvckqmqgrcz5jsjbrkrr8tzp1ao5trftgiq6ddjanldql...@mail.gmail.com Content-Type: text/plain; charset=UTF-8 2011/9/26 Sriram Gopalan mgs...@gmail.com: Hello everybody, We are facing an issue with loopback in pulse audio 0.9.22. We recently ported pulseaudio to an ARM 11 based evaluation board and are running pulseaudio in system mode. Great. Did you find it easy to get pulse to run, did you need to patch anything to make it working? If so, please submit upstream. [Sriram] Except for few glitches with the hal-detect module, there was no issue If we develop a patch, we will certainly upstream it. As a matter of fact, looking forward to it. 3) However, when we attempt the followings, it does not work. We cannot hear any audio, whereas the same works on my Ubuntu 10.10 desktop #arecord | aplay Are you saying that this doesn't work, or is the silence expected? Are you sure you're recording from the alsa hardware card and not from the pulse virtual alsa device? (I'm sorry for using the wrong terminology here) [Sriram] silence is not expected. I would expect a ramping up echo. #gst-launch alsasrc ! alsasink #pactl load-module module-loopback It would be good to know why you want to do this, as in general (especially on embedded devices) you would not want to use software-based loopback of the mic input. [Sriram] True. the end goal is to looback 2 different alsa devices for bluetooth functionality. We are using a bluetooth chipset which interfaces with the host micro over I2S. The drivers are integrated under the asoc layer of alsa. If I access the devices directly through alsa ( hw:0,0 and hw:0,1) it works exactly as expected. That being said, here are some other things you should try: - set the resampler to trivial or some speex-integer variant - try running with PULSE_NO_SIMD=1 set - try to run the tests of make check and see whether they give a problem [Sriram] Will surely try 1.0 now that it is launched and post the results here :-) With the first 2 commands, there is only silence. With the third option, pulse audio dies after sometime with a floating point exception. A backtrace would be nice. (preferably running from git master) Maarten -- Message: 4 Date: Tue, 27 Sep 2011 07:18:46 +0530 From: Arun Raghavan arun.ragha...@collabora.co.uk Subject: Re: [pulseaudio-discuss] No audio heard from loopback To: General PulseAudio Discussion pulseaudio-discuss@lists.freedesktop.org Message-ID: 1317088131.6608.6.camel@snowflake Content-Type: text/plain; charset=UTF-8 On Tue, 2011-09-27 at 00:05 +0530, Sriram Gopalan wrote: Hello everybody, We are facing an issue with loopback in pulse audio 0.9.22. We recently ported pulseaudio to an ARM 11 based evaluation board and are running pulseaudio in system mode. The application being targeted is In-vehicle-Infotainment and the board has a Mono Mic ( 16-bit, 1 channel) and a Stereo Speaker ( 2 channels, 16-bit, 44.1 Khz). 1) With gstreamer we are able to playback audio to the speakers using the following command. pulseaudio promptly gets into action and plays the file at 44.1 Khz without a glitch - #gst-launch filesrc location=/home/test/songs/test.mp3 ! mad ! alsasink 2) When we do a capture with the mic using the command below, again it works fine ( By default arecord and aplay use 8Khz, 8-bit mono channel for capture and playback) - #arecord test.wav #aplay test.wav 3) However, when we attempt the followings, it does not work. We cannot hear any audio, whereas the same works on my Ubuntu 10.10 desktop #arecord | aplay #gst-launch alsasrc ! alsasink #pactl load-module module-loopback Incidentally, why are all the tests with alsasrc/alsasink and not pulsesrc/pulsesink? [Sriram] I will try pulsesrc and pulsesink as well. I have not done that -- Arun
Re: [pulseaudio-discuss] Google ChromeOS reinventing the wheel, ignoring PulseAudio
On Tue, 2011-09-27 at 18:02 +0300, Rémi Denis-Courmont wrote: Le mardi 27 septembre 2011 17:27:14 Arun Raghavan, vous avez écrit : Do you have any more details? Seems to be more of a policy daemon than an audio server. Isn't audio policy daemon just a fancier name for (modern) audio server? Does PulseAudio not implement audio policy? Sure, PulseAudio certainly does not police video devices. That's partly done by the X server (XVideo grabs), partly by the window manager, but mostly not done at all. But still... Looking at what there is currently, there doesn't seem to be any trace of a client interface. That would suggest that it won't handle the actual audio stream data. Of course, the project is in a *very* early stage, so the client interface bits might get added later. In order to replace speculation with actual facts, I'll CC Taylor Hutt, who seems to be doing the development. Taylor, would you possibly have time to share some information about ADHD? For convenience, here's a link to the beginning of this thread: http://lists.freedesktop.org/archives/pulseaudio-discuss/2011-September/011452.html -- Tanu ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] [RFC] [PATCH 0/1] VLC pass-through to PulseAudio
Hello all, The following patch makes VLC negotiates S/PDIF pass-through with PulseAudio for A/52 and DTS audio tracks. This requires PulseAudio client library version 1.0.0 (or later) to compile, and a similarly recent PulseAudio server to actually work. I do not have S/PDIF speakers, so I was only able to test that normal PCM playback and PCM fallback work. So the probability that this does not work properly is about 99%. -- The following changes since commit 67889ac99eceb167f4fade5c73a3438ace4925ff: Move character escaping from the model contents, to the output helpers. (2011-09-27 18:07:04 +0300) are available in the git repository at: git://git.remlab.net/vlc-courmisch.git spadif Rémi Denis-Courmont (1): PulseAudio: negotiate digital pass-through for A/52 and DTS modules/audio_output/pulse.c | 73 +- 1 files changed, 72 insertions(+), 1 deletions(-) -- Rémi Denis-Courmont http://www.remlab.net/ http://fi.linkedin.com/in/remidenis ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Routing questions of module-switch-on-connect, module-device-manager and device profiles
On Wed, Sep 21, 2011 at 02:16:23PM +0800, David Henningsson wrote: [...] In a later version of these patches I have removed this functionality from m-s-on-c and put it into a separate module. I haven't posted that here yet as I didn't think it would be much reason to do so before 1.0 is released. Hi David, Do you have a separate git tree which tracks your latest developement on this jack detection stuff? If there's one, that'll be great. -- guanqun ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
