Hi All,
I am new to this list. I was looking at options of connecting my
Bluetooth headset to my laptop running Fedora 7, and came across this site.
So first up, I have built sample spec files that generate rpm files out
of sbc and plugz. In case you are interested then I can share them with
you all.
Now, I have installed both plugz and sbc. I am trying to use sco for
doing the two-way communication. I have copied over the
plugz/alsa-plugins/asound.conf (as ~/.asoundrc) and changed the BT
address to my headset's.
I ran the headset daemon and I noticed that my gnome-volume applet looks
different and shows a new control called PCM-2. But beyond this I am
unable to do much.
I also noticed that the website states that I need kernel patches. Is
this still true for kernels > 2.6.21 ??
I would really appreciate it if people could help me out with figuring
out this headset integration.
thanks,
Rogue
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Frederic,
Frederic Dalleau wrote:
> Just one line more,
>
>> However, when the softvol plugin is declared in .asoundrc, it appears in
>> the mixer.
>>
>>
> Wouldn't this explain the PCM-2device you saw in gnome-xxx?
>
>
Sorry for the late response. Thunderbird had moved this message to the
junk folder. Yes, the PCM-2 device in the applet was due to the
.asoundrc file. Once I removed the file everything was back to normal.
Ideally I would have expected the new devices mentioned in the file to
get appended to the available set, but I guess I need to spend some more
time understanding how the alsa-sound architecture works and how does it
treat the asoundrc file.
later,
Rogue
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
hey
> > sure... I could put them in contrib/
> >
> Do you want me to send them directly to you?
ok
> I see that there are some alsa-lib modules being built. So, do I still
> need to specify a custom asoundrc file? Wouldn't the device show up
> automatically in the applet's preferences?
I don't make the rules--I only complain about them. You might think
that the device would show up, but alsa has two apis for listing
devices: hardware only and hardware and plugins. No one uses the
latter so even when you do everything right, the alsa clients don't
know the device is there. you have to type in the name (some apps
won't let you do that). You won't escape creating the asoundrc.
The ray of hope here is that we want to get the bluez version to
behave well enough that it can be set as the default device, so no one
has to worry about what device is selected any more.
the bluez wiki discusses the bluez utils version
http://wiki.bluez.org/wiki/Audio
http://wiki.bluez.org/wiki/HOWTO/AudioDevices
brad
brought to you in non-html :)
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Just one line more,
> However, when the softvol plugin is declared in .asoundrc, it appears in
> the mixer.
>
Wouldn't this explain the PCM-2device you saw in gnome-xxx?
Frederic
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Rogue,
> I see that there are some alsa-lib modules being built. So, do I still
> need to specify a custom asoundrc file? Wouldn't the device show up
> automatically in the applet's preferences?
>
As far as I know, the device won't show up whether there is an .asoundrc
or not.
However, when the softvol plugin is declared in .asoundrc, it appears in
the mixer. So I suspect there is a way to make the plugin appears in the
players. I have never looked after that for now.
At least the entry must be declared in .asoundrc or
/usr/share/alsa/alsa.conf. I just found a utility called asoundconf.
This may be funny to try.
Hope this helps.
Frederic
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Brad Midgley wrote:
> hey
>
> So first up, I have built sample spec files that generate rpm
> files out
> of sbc and plugz. In case you are interested then I can share them
> with
> you all.
>
>
> sure... I could put them in contrib/
>
Do you want me to send them directly to you?
Secondly, if I build an rpm of plugz, i see that the following files are
being generated:
plugz /etc/dbus-1/system.d/a2dpd.conf
plugz /usr/bin/a2dpd
plugz /usr/bin/a2dpd_ctl
plugz /usr/bin/headsetd
plugz /usr/lib/alsa-lib/libasound_module_ctl_sco.a
plugz /usr/lib/alsa-lib/libasound_module_ctl_sco.la
plugz /usr/lib/alsa-lib/libasound_module_ctl_sco.so
plugz /usr/lib/alsa-lib/libasound_module_ctl_sco.so.0
plugz
/usr/lib/alsa-lib/libasound_module_ctl_sco.so.0.0.0
plugz /usr/lib/alsa-lib/libasound_module_pcm_a2dpd.a
plugz /usr/lib/alsa-lib/libasound_module_pcm_a2dpd.la
plugz /usr/lib/alsa-lib/libasound_module_pcm_a2dpd.so
plugz /usr/lib/alsa-lib/libasound_module_pcm_a2dpd.so.0
plugz
/usr/lib/alsa-lib/libasound_module_pcm_a2dpd.so.0.0.0
plugz /usr/lib/alsa-lib/libasound_module_pcm_sco.a
plugz /usr/lib/alsa-lib/libasound_module_pcm_sco.la
plugz /usr/lib/alsa-lib/libasound_module_pcm_sco.so
plugz /usr/lib/alsa-lib/libasound_module_pcm_sco.so.0
plugz
/usr/lib/alsa-lib/libasound_module_pcm_sco.so.0.0.0
plugz /usr/lib/liba2dpdcommon.a
plugz /usr/lib/liba2dpdcommon.la
plugz /usr/lib/liba2dpdcommon.so
plugz /usr/lib/liba2dpdcommon.so.0
plugz /usr/lib/liba2dpdcommon.so.0.0.0
plugz
/usr/share/dbus-1/services/com.access.a2dpd.service
I see that there are some alsa-lib modules being built. So, do I still
need to specify a custom asoundrc file? Wouldn't the device show up
automatically in the applet's preferences?
I am sorry if these are ignorant questions, but I am trying to learn
what I can about this package. Regarding the work that Marcel is doing
for bluez utils audio service, is there a project / development package
that I can play around with?
thanks,
Rogue
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Brad,
> So first up, I have built sample spec files that generate rpm
> files out
> of sbc and plugz. In case you are interested then I can share
> them with
> you all.
>
> sure... I could put them in contrib/
please do me a favor and stop using HTML email on the BlueZ mailing
list. It is bad enough that some people have no choice, but as one of
the core developers you should set a good example and not encourage
others with crappy HTML email.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
hey
So first up, I have built sample spec files that generate rpm files out
> of sbc and plugz. In case you are interested then I can share them with
> you all.
sure... I could put them in contrib/
Now, I have installed both plugz and sbc. I am trying to use sco for
> doing the two-way communication. I have copied over the
> plugz/alsa-plugins/asound.conf (as ~/.asoundrc) and changed the BT
> address to my headset's.
>
> I ran the headset daemon and I noticed that my gnome-volume applet looks
> different and shows a new control called PCM-2. But beyond this I am
> unable to do much.
most apps don't know about the plugin and you have to manually type in
"headset" for the alsa device. if the app doesn't let you type in the name,
you could make it the default device or hand-edit the config file.
I also noticed that the website states that I need kernel patches. Is
> this still true for kernels > 2.6.21 ??
I have not seen the flowcontrol patch land upstream.
I would really appreciate it if people could help me out with figuring
> out this headset integration.
you know this is a sort of testbed for this stuff. Marcel is allowing the
parts of the design that aren't broken to be rewritten into the bluez utils
audio service.
brad