[arch-general] Bluetooth headphone
Hi, I have a mono bluetooth headphone dongle thing that I got paired using the new KDE4 bluetooth manager (the guys really did a great job on this I might add). I added entries in ~/.asoundrc and can play sound files to it using "aplay -D <device>". Now, how do I get other apps to see it? I dont see it as a device or channel in the mixer? Manne
2010/1/26 Manne Merak <mannemerak@gmail.com>:
Now, how do I get other apps to see it? I dont see it as a device or channel in the mixer?
http://en.opensuse.org/Bluetooth/Headphones-HOWTO#Is_it_possible_to_make_any... -- GPG/PGP ID: B42DDCAD
On 01/26/2010 10:16 AM, Ray Rashif wrote:
2010/1/26 Manne Merak<mannemerak@gmail.com>:
Now, how do I get other apps to see it? I dont see it as a device or channel in the mixer?
http://en.opensuse.org/Bluetooth/Headphones-HOWTO#Is_it_possible_to_make_any...
Thanks, did all that already, as I said I can play audio using mplayer or aplay etc. But how do I get all apps that use it. Actually a guide that explains the roles of, alsa, phonon, gstreamer, xine, pulseaudio etc and how they fit together these days will also work for me. (as I understand KDE4 uses Phonon, which uses GStreamer as backend? which uses ALSA? sounds like a bit of abstraction madness going on) Manne
On Tue, Jan 26, 2010 at 5:07 PM, Manne Merak <mannemerak@gmail.com> wrote:
Thanks, did all that already, as I said I can play audio using mplayer or aplay etc. But how do I get all apps that use it. Actually a guide that explains the roles of, alsa, phonon, gstreamer, xine, pulseaudio etc and how they fit together these days will also work for me. (as I understand KDE4 uses Phonon, which uses GStreamer as backend? which uses ALSA? sounds like a bit of abstraction madness going on)
Manne
To get all apps to use it set a pcm.!default Personally, I find using pulseaudio to manage it (moving streams etc) to be much easier. BT headsets run out of battery, if that happens you have to manually change .asoundrc and perhaps restart sound-generating apps, if you're not using a sound server such as pulseaudio. If you want to read up on the different sound components, just do a google search. There's tons of articles out there, some very good, mostly a bit crap. Lennart Pottering (dev for Pulse) has a particularly good one I recall. Most on Arch wouldn't like his conclusions though.
On 01/26/2010 11:28 AM, Ng Oon-Ee wrote:
On Tue, Jan 26, 2010 at 5:07 PM, Manne Merak<mannemerak@gmail.com> wrote:
Thanks, did all that already, as I said I can play audio using mplayer or aplay etc. But how do I get all apps that use it. Actually a guide that explains the roles of, alsa, phonon, gstreamer, xine, pulseaudio etc and how they fit together these days will also work for me. (as I understand KDE4 uses Phonon, which uses GStreamer as backend? which uses ALSA? sounds like a bit of abstraction madness going on)
Manne
To get all apps to use it set a pcm.!default
Personally, I find using pulseaudio to manage it (moving streams etc) to be much easier. BT headsets run out of battery, if that happens you have to manually change .asoundrc and perhaps restart sound-generating apps, if you're not using a sound server such as pulseaudio.
If you want to read up on the different sound components, just do a google search. There's tons of articles out there, some very good, mostly a bit crap. Lennart Pottering (dev for Pulse) has a particularly good one I recall. Most on Arch wouldn't like his conclusions though.
That's what I thought, thanks, will try Pulseaudio (thou I have been warned by others). So am I right in understanding that in a "perfect world", all programs will support Pulseaudio (config and mixing) and in-tern it will use ALSA to do the lowlevel hardware side? (thus Pulseaudio will replace all the other sound servers and layers out there) Manne
On Tue, 2010-01-26 at 12:08 +0200, Manne Merak wrote:
On 01/26/2010 11:28 AM, Ng Oon-Ee wrote:
On Tue, Jan 26, 2010 at 5:07 PM, Manne Merak<mannemerak@gmail.com> wrote:
Thanks, did all that already, as I said I can play audio using mplayer or aplay etc. But how do I get all apps that use it. Actually a guide that explains the roles of, alsa, phonon, gstreamer, xine, pulseaudio etc and how they fit together these days will also work for me. (as I understand KDE4 uses Phonon, which uses GStreamer as backend? which uses ALSA? sounds like a bit of abstraction madness going on)
Manne
To get all apps to use it set a pcm.!default
Personally, I find using pulseaudio to manage it (moving streams etc) to be much easier. BT headsets run out of battery, if that happens you have to manually change .asoundrc and perhaps restart sound-generating apps, if you're not using a sound server such as pulseaudio.
If you want to read up on the different sound components, just do a google search. There's tons of articles out there, some very good, mostly a bit crap. Lennart Pottering (dev for Pulse) has a particularly good one I recall. Most on Arch wouldn't like his conclusions though.
That's what I thought, thanks, will try Pulseaudio (thou I have been warned by others). So am I right in understanding that in a "perfect world", all programs will support Pulseaudio (config and mixing) and in-tern it will use ALSA to do the lowlevel hardware side? (thus Pulseaudio will replace all the other sound servers and layers out there)
Try and find a program which pulse cannot handle, either natively or most likely through the alsa-plugin and padsp, the OSS emulator. Admittedly, there are bugs in the alsa-plugin for pulse, but its actively worked on by a paid developer who listens to well-mannered suggestions (not the typical linux fanatic going "I don't want anything to be different from 10 years ago when sound on linux was perfect"). And no, pulse will not replace all the other sound servers and layers. For pro-audio, JACK reigns, and will do so in the foreseeable future. Pulseaudio is meant for common desktop use, end of. Fortunately, that's exactly where most of us are with regards to sound. I think it bears repetition, for most programs (which don't try to use ALSA in complicated ways) you only need to use pulse's alsa-plugin and it'll work with pulse no problem. Sound APIs such as gstreamer already support direct pulse output.
2010/1/26 Manne Merak <mannemerak@gmail.com>:
On 01/26/2010 10:16 AM, Ray Rashif wrote:
2010/1/26 Manne Merak<mannemerak@gmail.com>:
Now, how do I get other apps to see it? I dont see it as a device or channel in the mixer?
http://en.opensuse.org/Bluetooth/Headphones-HOWTO#Is_it_possible_to_make_any...
Thanks, did all that already, as I said I can play audio using mplayer or aplay etc. But how do I get all apps that use it. Actually a guide that explains the roles of, alsa, phonon, gstreamer, xine, pulseaudio etc and how they fit together these days will also work for me. (as I understand KDE4 uses Phonon, which uses GStreamer as backend? which uses ALSA? sounds like a bit of abstraction madness going on)
"Thus you can use BT headset with applications which support the output configuration to specific alsa device (specified in ~/.asoundrc) [b]. If your application does not allow this kind of configuration you can also try to set the default alsa device to your BT headset too. This will help of course only if this application sends the output to alsa." I think it's not possible to use it as how you expect. -- GPG/PGP ID: B42DDCAD
Am oder ungefähr am Dienstag, 26. Januar 2010, schrieb Ray Rashif:
2010/1/26 Manne Merak <mannemerak@gmail.com>:
"Thus you can use BT headset with applications which support the output configuration to specific alsa device (specified in ~/.asoundrc) [b]. If your application does not allow this kind of configuration you can also try to set the default alsa device to your BT headset too. This will help of course only if this application sends the output to alsa."
I think it's not possible to use it as how you expect.
I don’t really understand why you need to use pulseaudio for this purpose (as some people in this thread mentioned). I had a similar issue with an on-board sound card and an external headset that was plugged in via usb and recognized as a separate sound card. I wrote a simple udev rule (1 line) that switched the symlink /etc/asoundrc to two prepared asoundrc files in one of which the headset was the default device and in the other the on-board sound card. So if the headset was plugged in it was used exclusively and the other way round. :) Ed
On 01/28/10 03:43, Edgar Kalkowski wrote:
Am oder ungefähr am Dienstag, 26. Januar 2010, schrieb Ray Rashif:
2010/1/26 Manne Merak<mannemerak@gmail.com>:
"Thus you can use BT headset with applications which support the output configuration to specific alsa device (specified in ~/.asoundrc) [b]. If your application does not allow this kind of configuration you can also try to set the default alsa device to your BT headset too. This will help of course only if this application sends the output to alsa."
I think it's not possible to use it as how you expect.
I don’t really understand why you need to use pulseaudio for this purpose (as some people in this thread mentioned). I had a similar issue with an on-board sound card and an external headset that was plugged in via usb and recognized as a separate sound card. I wrote a simple udev rule (1 line) that switched the symlink /etc/asoundrc to two prepared asoundrc files in one of which the headset was the default device and in the other the on-board sound card. So if the headset was plugged in it was used exclusively and the other way round. :)
Care to share your mods? I've been using Linux for awhile and that's still something that has me confused. If I boot with my USB headphones plugged in, some sound engines (like Xine) use them, and others (gstreamer) don't. And I don't know how to swap them around. -- Jonathan Arnold (mailto:jdarnold@buddydog.org) Daemon Dancing in the Dark, an Open OS weblog: http://linux.amazingdev.com/blog/
Am oder ungefähr am Donnerstag, 28. Januar 2010, schrieb Jonathan D. Arnold / Daemon Dancing:
On 01/28/10 03:43, Edgar Kalkowski wrote:
I don’t really understand why you need to use pulseaudio for this purpose (as some people in this thread mentioned). I had a similar issue with an on-board sound card and an external headset that was plugged in via usb and recognized as a separate sound card. I wrote a simple udev rule (1 line) that switched the symlink /etc/asoundrc to two prepared asoundrc files in one of which the headset was the default device and in the other the on-board sound card. So if the headset was plugged in it was used exclusively and the other way round. :)
Care to share your mods? I've been using Linux for awhile and that's still something that has me confused. If I boot with my USB headphones plugged in, some sound engines (like Xine) use them, and others (gstreamer) don't. And I don't know how to swap them around.
What I did was change the alsa default device depending on whether or not the USB headset was plugged in. This was done by a udev rule in /etc/udev/rules.d that named 39-alsa-usb.rules that contained the following two lines: KERNEL=="pcmC[D0-9cp]*", DRIVERS=="usb", ACTION=="add", RUN+="/usr/bin/alsa-usb-add" KERNEL=="pcmC[D0-9cp]*", DRIVERS=="usb", ACTION=="remove", RUN+="/usr/bin/alsa-usb-remove" The scripts /usr/bin/alsa-usb-{add,remove} contained a single line that linked /etc/asound.conf to one of two prepared asound.conf files: #!/bin/bash ln -sf /etc/asound.conf.hw0 /etc/asound.conf or #!/bin/bash ln -sf /etc/asound.conf.hw1 /etc/asound.conf I can’t find the asound.conf.hw{0,1} files at the moment (I have a non USB headset now) but they contained a very simple configuration with hw0 as the default alsa sound device or hw1 as the default alsa sound device in the other case. Hope this helps you! :) Ed
participants (5)
-
Edgar Kalkowski
-
Jonathan D. Arnold / Daemon Dancing
-
Manne Merak
-
Ng Oon-Ee
-
Ray Rashif