From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] CVS audio-api.txt : 1st question
Date: Fri, 29 Jun 2007 17:21:42 +0200 [thread overview]
Message-ID: <46852386.8050608@free.fr> (raw)
Hi Bluez developer,
I'm trying to move forward on the design of the Bluez audio API. I'm
gonna suggest some new methods and signals to handle HFP and A2DP,
however at first i feel the need to understand the following methods and
signals:
Methods:
--------
void Play()
void Stop()
uint16 GetSpeakerGain()
uint16 GetMicrophoneGain()
void SetSpeakerGain(uint16 gain)
void SetMicrophoneGain(uint16 gain)
Signals:
------------
void SpeakerGainChanged(uint16 gain)
void MicrophoneGainChanged(uint16 gain)
Here is the question : aren't those actions and events not supposed to
be handled by the various ALSA plugins,
that would communicate using a dedicated unix socket ?
In fact i'm afraid of the following issues if those methods/signals are
available:
* An application could use snd_pcm_start to start playing, and another
one could shut down the stream using
Stop() : the result would certainly be an unexpectedly broken stream.
* Application developpers could be rather confused (Which one of Play()
or snd_pcm_start should i use? Or maybe i should use both? In this case
which one am i supposed to call first ?)
* If the ALSA plugin is supposed to call those method by itself, this
would mean bring dbus in each
application process' space, which is not that nice...
* Gain management signals and functions are redundant with equivalent
ALSA&GStreamer functions.
I hope this will bring some light on the expected use of those
methods/signals...
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
next reply other threads:[~2007-06-29 15:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 15:21 Fabien Chevalier [this message]
2007-06-29 18:10 ` [Bluez-devel] CVS audio-api.txt : 1st question Luiz Augusto von Dentz
2007-06-29 20:38 ` Brad Midgley
2007-07-02 17:03 ` Fabien Chevalier
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=46852386.8050608@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