From: Johan Hedberg <johan.hedberg@gmail.com>
To: "Thomas Wälti" <twaelti@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, Krisztian.Litkey@nokia.com,
Jyri.Sarha@nokia.com
Subject: Re: HFP Pulseaudio Source destroyed "too quickly" at the end of a call
Date: Wed, 27 Oct 2010 18:26:02 -0400 [thread overview]
Message-ID: <20101027222602.GB24756@jh-x301> (raw)
In-Reply-To: <AANLkTikQqPqJdFgLpUrKiqyAC0HNUFnj+8NtbPxazY18@mail.gmail.com>
Hi Tom,
On Wed, Oct 27, 2010, Thomas Wälti wrote:
> I'm developing an application that records all kinds of audio using GStreamer.
> Target platform is the Nokia N900, the app is called Recaller
> (http://maemo.org/downloads/product/Maemo5/recaller/)
Looks like a pretty cool app!
> All works well except when ending the recording of Bluetooth
> Conversations: Once a party hangs up the call, the PulseAudio source
> and sink disappear before I can stop GStreamer recording (I'm
> listening to D-Bus events). Unfortunately, this causes my GStreamer
> pipeline to crash.
>
> Is there a way to either delay the destruction of the sink/source by
> Bluez or a D-Bus message I could intercept/attach to? How can I "win
> the race"?
Probably this isn't really BlueZ related, but the audio policy module
(on the PulseAudio side) in the N900 kicks in and requests these changes
to the audio streams. Unfortunately I'm not really an expert with that
code (and afaik the audio policy part is closed) so I can't really offer
more insight on the issue. Just speculating, but you might be able to
accomplish something by hacking in some delays into the pulse bluetooth
modules (but again, I'm not really familiar with them so this might not
be a feasible approach).
Johan
next prev parent reply other threads:[~2010-10-27 22:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 20:03 HFP Pulseaudio Source destroyed "too quickly" at the end of a call Thomas Wälti
2010-10-27 22:26 ` Johan Hedberg [this message]
2010-10-28 8:57 ` Thomas Wälti
2010-10-29 16:19 ` Peter Dons Tychsen
2010-10-31 19:26 ` Luiz Augusto von Dentz
2010-11-01 8:11 ` Thomas Wälti
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=20101027222602.GB24756@jh-x301 \
--to=johan.hedberg@gmail.com \
--cc=Jyri.Sarha@nokia.com \
--cc=Krisztian.Litkey@nokia.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=twaelti@gmail.com \
/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