From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Jacek Szczech <jszczech@8planet.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: A2DP sink indications + autoclose after suspension
Date: Tue, 23 Feb 2010 22:14:49 +0200 [thread overview]
Message-ID: <2d5a2c101002231214n37b61a6bt5106b6c68ec0bb2@mail.gmail.com> (raw)
In-Reply-To: <20100223125854.GA22065@8planets.net>
Hi,
2010/2/23 Jacek Szczech <jszczech@8planet.net>:
> Hi,
>
> I succeeded writing a program that receives a2dp stream (from my mobile
> phone), decodes and sends to stdout using unix/ipc interface. It'll be run on
> old hw without X enviroment, that's why I didn't use already available
> software (like pulseaudio).
>
> I faced a few problems connected with suspension of stream:
>
> 1) Unix.c does not support indications (am I right?). How can I detect changes
> of states (e.g. OPEN<->STREAMING)? I can detect suspension with EAGAIN on
> stream_fd but it does not seem to be proper solution. Do you plan to support
> indications in unix/ipc interface?
You can listen for State on Audio interface or in the profile specific
interfaces such as AudioSource/AudioSink/Headset.
> 2) Will it be possible to get indications concerning OPEN<->STREAMING changes
> on dbus Media interface?
Media interface is just for endpoint registration, but again you can
achieve the same by listen to State changes e.g. Connected <-> Playing
> 3) After suspension of stream (SUSPEND sent from SRC) the stream
> is CLOSEd after about 10 seconds. What part of code disconnects this? Is it a
> way to avoid this?
Afaik this is not triggered if there is a unix client holding a lock,
so if e.g. the headset reconnects you have to claim the socket
otherwise it will timeout.
--
Luiz Augusto von Dentz
Computer Engineer
prev parent reply other threads:[~2010-02-23 20:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 12:58 A2DP sink indications + autoclose after suspension Jacek Szczech
2010-02-23 20:14 ` Luiz Augusto von Dentz [this message]
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=2d5a2c101002231214n37b61a6bt5106b6c68ec0bb2@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=jszczech@8planet.net \
--cc=linux-bluetooth@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).