Re: [Bluez-devel] question: what does this patch from snd-bt-sco do?

[Marcel Holtmann <marcel@holtmann.org>]

Hi Lars,

> won't be a problem. I know what to do because I changed them before,
> from S8 to MULAW_8 :)
> 
> My only problem/wish is that I'd like to support all three audio
> encodings, but I understand this is impossible right now.

only because mulaw and alaw are 8bit.

> What exactly are the influences of the "alternate setting"? Does this
> only change SCO/Audio behaviour, or is the whole bluez stack affected by
> this (if hci_usb is used, of course). I just want to understand the
> pros/cons of 8bit/16bit setting.

Look at the Bluetooth specification of H:2. This is USB specific and it
is because of the ISOC transfers that are used for the SCO packets.

> There's one more (alsa-related) issue I have with the alsa driver. The
> problem is that, if there's no open sco channel, the audio application
> accessing the interface is stalled because the buffer is never read. It
> would be better if the data could be "dumped" or something.
> 
> Is this possible in an easy way, or do I have to look for audio
> sync/timing and stuff instead of just writing the data to /dev/null and
> tell the app "go for the next buffer".

This is a complete other topic and as I said many times before the SCO
driver must be written to be better integrated into the BlueZ core and
the ALSA sound system.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel