public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] CVS audio-api.txt : 1st question
Date: Mon, 02 Jul 2007 19:03:40 +0200	[thread overview]
Message-ID: <46892FEC.7000705@free.fr> (raw)
In-Reply-To: <2d5a2c100706291110i473d080bv6ba634f0eb8d9deb@mail.gmail.com>

Hi Luiz Augusto,
Thanks for your answers !!

Please find some more comments below.
> Hello Fabien,
> 
> The API is not properly design for audio over hci that's why you are 
> confused.

Oh you're damn right. I knew about this sco over PCM way of doing 
things, i just completely forgot about it when i read the interface, 
sorry about that :-(


> Those methods make no sense as you had mentioned the commands always
> come from/goes to alsa plugin (we have just one plugin for pcm that should
> handle any kind of audio device) via unix socket. So a normal scenarios when
> sco over hci is to CreateHeadset in the very first time, this will salve 
> the device
> in the storage so it is no longer necessary to create it anymore. This 
> mean we
> don't need any method call to the API to get audio working while in hci 
> mode,

Oh that's nice :-)

> the plugin already works on demand and I currently fixing the concurrent
> connections when an application want to open the device for playback and
> capture at same time.
> The current API is only useful for audio over PCM, in that case I guess 
> we need
> the API methods to be able to control the streams.

Yes and no. The issue with this approach is that applications need to be 
modified to work with sco-over-pcm, which is not very nice :-(
I guess it could be possible to have the pcm_bluetooth ALSA plugin to be 
used even in sco over PCM case, using the ALSA device as slave pcm.
What do you think of thus idea ?


> We could disable those concurrent method while in hci mode as they 
> probably break
> the plugin stream, actually they normally affects only the rfcomm socket 
> because
> sco socket got duped in the process so plugin got its own reference that 
> is not
> affected by API calls, but anyway this is a not common behavior for a 
> headset.

Indeed, and according to HSP/HFP specs, the sco channel is supposed to 
be closed before the RFCOMM one...

Btw, sorry to ask again : has anybody an explanation on the reason for 
the Gain management signals&functions ?

Cheers,

Fabien

-------------------------------------------------------------------------
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2007-07-02 17:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-29 15:21 [Bluez-devel] CVS audio-api.txt : 1st question Fabien Chevalier
2007-06-29 18:10 ` Luiz Augusto von Dentz
2007-06-29 20:38   ` Brad Midgley
2007-07-02 17:03   ` Fabien Chevalier [this message]
2007-07-03  3:31     ` Brad Midgley
2007-07-03  8:04       ` Fabien Chevalier
2007-07-03 19:54         ` Luiz Augusto von Dentz
2007-07-03 21:08           ` Brad Midgley
2007-07-03 22:25             ` Luiz Augusto von Dentz
2007-07-04  1:57             ` Marcel Holtmann
2007-07-05 12:21               ` Fabien Chevalier
2007-07-05 13:53                 ` Luiz Augusto von Dentz
2007-07-05 15:48                   ` Fabien Chevalier
2007-07-05 14:12                 ` Frederic Dalleau
2007-07-05 15:55                   ` Fabien Chevalier
2007-07-05 16:40                 ` Brad Midgley
2007-07-06  7:43                   ` Fabien Chevalier
2007-07-06 13:12                     ` Luiz Augusto von Dentz
2007-07-06 13:32                       ` Fabien Chevalier
2007-07-06 13:43                         ` Frederic Dalleau
2007-07-06 15:01                           ` Luiz Augusto von Dentz
2007-07-06 17:07                             ` Fabien Chevalier
2007-07-06 23:44                               ` Brad Midgley
2007-07-07  6:29                                 ` Luiz Augusto von Dentz
2007-07-11 17:33                                   ` Fabien Chevalier
2007-07-11 21:56                                     ` Brad Midgley
2007-07-06 15:24                           ` Fabien Chevalier
2007-07-06 15:38                             ` Frederic Dalleau
2007-07-06 16:56                               ` Fabien Chevalier
2007-07-05 12:53           ` Fabien Chevalier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46892FEC.7000705@free.fr \
    --to=fabchevalier@free.fr \
    --cc=bluez-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox