Linux bluetooth development
 help / color / mirror / Atom feed
From: Peter Dons Tychsen <donpedro@tdcadsl.dk>
To: "Thomas Wälti" <twaelti@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: HFP Pulseaudio Source destroyed "too quickly" at the end of a call
Date: Fri, 29 Oct 2010 18:19:29 +0200	[thread overview]
Message-ID: <1288369169.4351.8.camel@donpedro> (raw)
In-Reply-To: <AANLkTikQqPqJdFgLpUrKiqyAC0HNUFnj+8NtbPxazY18@mail.gmail.com>

On Wed, 2010-10-27 at 22:03 +0200, Thomas Wälti wrote:

> 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.

There are many reasons (especially for wireless device) that the source
or sink could disappear at any time. Audio disappearing before or after
the accompanying signaling furthermore a classic scenario which apps
should be built to handle. So fixing the race (which i am not sure is
really a race) does not seem like the correct solution. Trying to fix
such "races" can lead to inefficiency by using unneeded timers and
spin-locks, and will not provide robustness, as the audio streams can
disappear for other reasons anyway.

Maybe the crash is more interesting. What actually crashes when this
happens, and why?

Thanks,

/pedro



  parent reply	other threads:[~2010-10-29 16:19 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
2010-10-28  8:57   ` Thomas Wälti
2010-10-29 16:19 ` Peter Dons Tychsen [this message]
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=1288369169.4351.8.camel@donpedro \
    --to=donpedro@tdcadsl.dk \
    --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