public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Chan-Yeol Park <chanyeol.park@samsung.com>
To: 'Luiz Augusto von Dentz' <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Is it possible that user change a stream path between Speaker and Bluetooth like normal phone?
Date: Wed, 15 Jul 2009 23:49:10 +0900	[thread overview]
Message-ID: <002301ca055b$69c4fa00$3d4eee00$%park@samsung.com> (raw)
In-Reply-To: <2d5a2c100901050453w403ee755u61549a52b6514b65@mail.gmail.com>

Hi,

If you know or possible,
Could you explain me how to change stream path between Speaker or Bluetooth
with BlueZ gstreamer plug-in like normal phone?

In my case, I could see it works well with a gstreamer output-selector
element except some case.

1. User listens to Bluetooth Stereo Audio.
2. Switch off the headset when stream position is about 5 second from the
start of the song.
3. Gstreamer Plug-in gst_avdtp_sink_render() we could see
g_io_channel_write()works well even though headset is already off.
4. When stream position is about 9 second, g_io_channel_write() function is
blocked....-.-;
5. When it is 14 second , g_io_chhanel_write() returns with timeout error.

It's problem that at 14 second , gstreamer could not do anything even if
they know the error...

Related to this scenario , Do you have a good idea?

As a matter of fact, I try to avoid blocking , I change g_io_channel_write()
as non-blocking call.
Because Non blocking call makes the situation to the gstreamer like normal
condition. So we can change it easily as usual.

But the side effects occurs that music stream is mixed..when wireless
communication doesn't work well-.-;



Regards.
Chanyeol





  reply	other threads:[~2009-07-15 14:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200812301246.25781.siarhei.siamashka@nokia.com>
2009-01-01 14:24 ` SBC encoder conformance test for version 4.25 passed! Christian Hoene
2009-01-05  8:27   ` Siarhei Siamashka
2009-01-05 11:43     ` [PATCH] SBC Encoder program Christian Hoene
2009-01-05 12:22       ` Luiz Augusto von Dentz
2009-01-05 12:28         ` Christian Hoene
2009-01-05 13:13           ` Luiz Augusto von Dentz
2009-01-05 14:42             ` Christian Hoene
2009-01-05 14:48               ` Siarhei Siamashka
2009-01-05 13:22           ` Siarhei Siamashka
2009-01-05 14:42             ` Christian Hoene
2009-01-05 15:18               ` Siarhei Siamashka
2009-01-05 15:24                 ` Siarhei Siamashka
2009-01-05 15:33                 ` Christian Hoene
2009-01-05 17:39                   ` Siarhei Siamashka
2009-01-05 19:45                 ` Marcin Tolysz
2009-01-05 21:11                 ` David Sainty
2009-01-05 20:36             ` Marcin Tolysz
2009-01-06  2:43           ` Marcel Holtmann
2009-01-05 12:53     ` SBC encoder conformance test for version 4.25 passed! Luiz Augusto von Dentz
2009-07-15 14:49       ` Chan-Yeol Park [this message]
2009-07-15 15:27         ` Is it possible that user change a stream path between Speaker and Bluetooth like normal phone? Bastien Nocera
2009-01-05 14:55     ` SBC encoder conformance test for version 4.25 passed! Christian Hoene
2009-01-05 15:32       ` Siarhei Siamashka
2009-01-06  0:40     ` Nick Pelly

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='002301ca055b$69c4fa00$3d4eee00$%park@samsung.com' \
    --to=chanyeol.park@samsung.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@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