I ask that because I use my Laptop with the 5.1 Soundcard from my Desktop. If I could use the desktop sound card on my phone I could turn my phone to the only voice chat tool I have to need and could be able to use my Headset at home also with my phone.

DLNA output could be Great for using my TV as Audio output device (Maybe as VideoFile so a Videostrem in Future could be add). Every TV is able to use DLNA but remotecontrole a TV from a Phone needs an extra App (and I do not know what they stream to the TV manufacturer)

What I also wish, is an Auto configuration tool for Pulseaudio. If I connect a Microphone Pulse Audio could maybe Use it to detect what Speaker are connected, what latency they have and what volume control in fact is able to change the volume.

Maybe it could exist a time in a Future state, who One little Server could handle all Audiostreams at home.

kind regards AdlerHorst

I am trying to stream audio from my PC to OMAP4 based board running ICS on it using BT. I have enabled BT audio sink profile & able to connect it. But no audio.

So I tried the patch you have given on Android 4.1 ICS source. It gives some compilation error. ” Unable to locate format.h file. Tried googling, still no luck. ” How do I resolve this?

Any inputs? Thanks in advance.

Regards, Ramya.M

Unfortunately, PulseAudio doesn’t build any longer with 4.2 AOSPs using the instructions you have posted.

Pulseaudio for Android would provide developers with exciting possibilities. Are you planning on continuing this work? This would be great.

I routinely used this on my laptop and I really miss it on my tablet. Latency? Well who needs ms when you are happy with a use case that allows for several seconds delay.

Maybe another use case for selling the concept to OEMs.

PA 3.0 was released last December, and I am curious if anyone has tried the port instructions with v3

The long answer is: base volumes are used to signal a case when 0 dB is not 100%. Some devices (usually capture, but sometimes also playback) have the ability to provide amplification, and this is exposed via ALSA. In such cases, we define the “base volume” as the 0 dB point, and 100% as the maximum amplification that the ALSA mixers expose.

Our current recommendation for volume UIs is to show this base volume as a tick somewhere between o and 100%. This is really not terribly useful for most users, so we’re inclined to stop showing that base volume tick. The rest of the functionality remains the same.

Hope this helps! :)

I had a question about the “base volume” part of this report, but first let me say that if I should ask on a different mailing list or location, I’m happy to do that.

I’m a user who semi-regularly uses pavucontrol’s UI to boost volume for audio sinks past 100%. The reason (crazy as it may sound) is that I have a passive speaker in my shower that I connect to my laptop to play music, and the passive speaker doesn’t quite sound loud enough when my laptop volume is at 100%. So I usually blast it to 110% or 120% in pavucontrol, and that does the trick. (Naturally, once I reach a certain point, ~130% in my case, the sound gets “clipped.”)

From what I read of your base volume discussion, you intend to make it so that user-oriented UIs no longer show options past 100%. Let me know if that’s a mis-read.

I have noticed that “regular user-oriented” UIs like the GNOME volume knob and Rhythmbox’s volume knob already don’t seem to let me go past 100%.

I’m hoping that your “base volume” changes still let me do the above in pavucontrol. In general, I find pavucontrol extremely useful but hardly mentioned nowadays (I’ve been using pulseaudio since before the name change mid last-decade), so I figure it’s considered an advanced tool for people like me and will continue to work in that fashion.

So… from what I can tell, the “base volume” discussion means that pavucontrol will still let me do what I’m doing now, and that regular UIs like Rhythmbox’s will continue to only show a range of 0 to 100% (where 100% is what you refer to as 0dB). You said you’d remove indications of 0dB AKA 100% in user-oriented UIs… does that mean pavucontrol will stop showing me the helpful 100% marker? Or just that non-pavucontrol UIs will only show a range of 0 to 100% (which as far as I can tell is what they already do)?

Thanks! Sorry for all that repetition; I’m hoping that by explaining what I think your note means, you’ll spot any confusion or mis-reading on my part quickly. Again, I appreciate all the work that goes into pulseaudio and also post-event notes; I’ve had a lot of experience with post-event writeups recently so I definitely know they take quite some thinking and writing!

I’d be happy to give you some examples of how to try out low latency playback and see its effects. One easy way: run pulseaudio with verbose output (-vvvv) and then run paplay --latency-msec=12 --process-time-msec=3 /path/to/some/wav/file. You’ll see output in the server logs from the alsa-sink bits about the minimum latency it is able to deliver amongst other things.

Thanks a lot, - Juri