hi Pierre
I append below code in default.pa for loading the PA module when it start
up.
"load-module module-bluetooth-device profile=a2dp channels=2
address=00:0D:3C:EE:A5:F7 name=mcoBT"
But, my audio is still missing when I use "gst-launch-0.10 audiotestsrc !
pulsesink" for audio testing.
Here is my further question.
(1). Do I still keep the code in /etc/alsa/pulse-default.conf for bluetooth?
Below is what I append!
pcm.bluetooth {
type bluetooth
device XX:XX:XX:XX:XX:XX
profile "a2dp"
}
(2) Do I use the right sink element (i.e. pulsesink) to test audio from BT?
(3) How do I make sure that the bluez audio has connects to the PA
correctly?
Thanks
2011/2/24 pl bossart <[email protected]>
>
>
> On Wed, Feb 23, 2011 at 2:27 AM, <[email protected]> wrote:
>
>>
>> Hi there
>> I am working on testing audio via bluetooth headset on my device
>> now, I can heard the audio from the BT earpiece by "aplay" or "alsasink" .
>> However, I failed to route the test audio to Pulseaudio sound server by
>> "pulsesink" or "paplay" with error message return as below.
>> my question is ...
>> Do I need to install extra pkgs (sort of plug-in ) for bluez audio service
>> to make it work?
>>
>>
>> [meego@localhost test]$ gst-launch-0.10 audiotestsrc ! pulsesink
>> device=bluetooth
>>
>
> It's probably the wrong sink name. use
> pactl list
> and find out the actual name of the BT sink. You may also have to configure
> the sink to be in A2DP mode.
> -Pierre
>
> _______________________________________________
> MeeGo-dev mailing list
> [email protected]
> http://lists.meego.com/listinfo/meego-dev
> http://wiki.meego.com/Mailing_list_guidelines
>
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
