public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Christian Hoene <hoene@uni-tuebingen.de>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Questions on connecting BlueZ/SBC with Ekiga
Date: Sun, 18 Jan 2009 16:05:06 +0100	[thread overview]
Message-ID: <1232291106.5095.6.camel@californication> (raw)
In-Reply-To: <016701c97976$e75578d0$b6006a70$@de>

Hi Christian,

> I have a question on how to use A2DP and SBC for streaming of audio over the
> Internet.
> 
> How would you implement an interface between Ekiga and BlueZ? The
> requirements are
> 1 SBC frames from Ekiga
> 1.1 Shall be played via an A2DP device.
> 1.2 Shall be played via the sound card of the PC.

can you use GStreamer here since that includes the SBC encoder and
decoder as elements. You can construct the pipeline as you like.

Meaning that Ekiga would be a GStreamer source. Of course you would have
to write that specific source element.

> 2. SBC frame going to Ekiga
> 2.1 Recorded from an A2DP device
> 2.2 recorded by the PC's sound card.

Having Ekiga as a GStreamer sink sounds like a good idea.

> Due to legal reason we must use the BlueZ and are not allowed to include SBC
> into Ekiga.

What kind of legal reasons are you talking about here. The SBC
implementation is released under LGPL. Worst case issue here is that you
actually build an independent library out of it and just link it
dynamically. We were planning to do so anyway, but currently that is not
really sufficient for us. It would just create a maintenance overhead.

Regards

Marcel



  reply	other threads:[~2009-01-18 15:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18 14:12 Questions on connecting BlueZ/SBC with Ekiga Christian Hoene
2009-01-18 15:05 ` Marcel Holtmann [this message]
2009-01-18 15:19   ` Christian Hoene
2009-01-18 16:01     ` Marcel Holtmann
2009-01-19  1:35       ` Brad Midgley
2009-01-19  5:17         ` Christian Hoene

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=1232291106.5095.6.camel@californication \
    --to=marcel@holtmann.org \
    --cc=hoene@uni-tuebingen.de \
    --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