Marcel
I rewrote the dbus proposal. If what's here looks ok we can start
thinking about the named pipe, ipc, or whatever we use for sending audio
and file descriptors around.
http://bluetooth-alsa.sourceforge.net/future.html
Brad
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Fabien
> But what about A2DP ? Wouldn't it make sense to use ALSA mixing facility
> too ?
dmix essentially acts as an audio server. But it's not the only one we
should consider. I've been looking at pulseaudio to see if it fits in
the picture at all. Seems to handle sound adapters that come and go and
includes a sort of audio routing mechanism.
Brad
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Brad,
>> Brad, i think the 'only on sco channel at a time argument' is not very
>> pertinent, for two reasons:
>> * First, i'm not sure there is an added value to be able to mix sound
>> channels to a sco headset.
>> * Second, if we think this is really needed, ALSA provides all
>> required facilities to mix multiple streams to one (think to the dmix
>> plugin). For your information, dmix is now on by default since alsa
>> 1.0.10 if i remember. Previously most cheap computers were only able to
>> play one PCM stream at a time. While annoying, that didn't kill anybody
>> tought ;-)
>
> maybe the documentation could use some improvement, but I'm in agreement
> with you. We should give the plugin its own file descriptor for the sco
> link.
>
hmmm... i must have smoked the carpet again :-(
So it looks that we agree, everything's fine. ;-)
But what about A2DP ? Wouldn't it make sense to use ALSA mixing facility
too ?
Cheers,
Fabien
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Fabien
> Brad, i think the 'only on sco channel at a time argument' is not very
> pertinent, for two reasons:
> * First, i'm not sure there is an added value to be able to mix sound
> channels to a sco headset.
> * Second, if we think this is really needed, ALSA provides all
> required facilities to mix multiple streams to one (think to the dmix
> plugin). For your information, dmix is now on by default since alsa
> 1.0.10 if i remember. Previously most cheap computers were only able to
> play one PCM stream at a time. While annoying, that didn't kill anybody
> tought ;-)
maybe the documentation could use some improvement, but I'm in agreement
with you. We should give the plugin its own file descriptor for the sco
link.
Brad
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Brad&Jose,
>
>> I think that bt.audiod should only handle the audio control portion.
>> The audio plugins should do direct bluetooth I/O.
>
> I'll update the page then. I won't rule out having bt.audiod manage a
> file descriptor for the sco channel and pass it around like Fabien did
> in his daemon. Only one app could use the sco channel at a time.
Brad, i think the 'only on sco channel at a time argument' is not very
pertinent, for two reasons:
* First, i'm not sure there is an added value to be able to mix sound
channels to a sco headset.
* Second, if we think this is really needed, ALSA provides all
required facilities to mix multiple streams to one (think to the dmix
plugin). For your information, dmix is now on by default since alsa
1.0.10 if i remember. Previously most cheap computers were only able to
play one PCM stream at a time. While annoying, that didn't kill anybody
tought ;-)
>
> In the case of a2dp where we're already dealing with long latencies, I
> would like to have bt.audiod mix, encode, and deliver the audio. The
> challenge there is to keep the latency consistent so a video player
> could accommodate it.
>
> Brad
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Brad & Marcel,
I got a number of interrogations regarding the various methods/signals
exposed here. I noticed a few things that won't work. To be able to
pinpoint these issues one by one, i think there is a need to draw some
diagrams that show the dynamic aspects of things. I'm gonna try drawing
a few of those before the end of the year : hopefully i will find some
spare time as i'm gonna be in hollidays from Xmas till new year...
Cheers,
Fabien
> Marcel
>
> I rewrote the dbus proposal. If what's here looks ok we can start
> thinking about the named pipe, ipc, or whatever we use for sending audio
> and file descriptors around.
>
> http://bluetooth-alsa.sourceforge.net/future.html
>
> Brad
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Jose
> I think that bt.audiod should only handle the audio control portion.
> The audio plugins should do direct bluetooth I/O.
I'll update the page then. I won't rule out having bt.audiod manage a
file descriptor for the sco channel and pass it around like Fabien did
in his daemon. Only one app could use the sco channel at a time.
In the case of a2dp where we're already dealing with long latencies, I
would like to have bt.audiod mix, encode, and deliver the audio. The
challenge there is to keep the latency consistent so a video player
could accommodate it.
Brad
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel