public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: thiagoss <thiagossantos@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] patches fixing gstreamer plugins
Date: Wed, 26 Sep 2007 19:19:57 -0300	[thread overview]
Message-ID: <de4879e80709261519s68ca904i19f54905ece3594f@mail.gmail.com> (raw)
In-Reply-To: <1190844611.6484.33.camel@aeonflux.holtmann.net>


[-- Attachment #1.1: Type: text/plain, Size: 1613 bytes --]

Hi Marcel

I know, the thing is the capabilities negotiation wasn't properly
implemented, some functions should have been overrided, sbcdec and sbcenc
should be enough to decode/encode, but since sbcparse was missing the same
thing sbcenc was, I did the work too.

If a use:
filesrc ! audioconvert ! sbcenc ! fakesink

it works, but that doesn't mean the problem isn't there, it just hasn't
ocurred, (the reason is that fakesink accept any kind of buffers, thus
negotiation is "everything is ok"), when I put sbcparse (even if its not
useful, it's just for testing) the negotiation should succeed, both of them
work with sbc, and it isn't succeeding.

Both sbcenc and sbcparse had a problem, the example I gave was only a
demonstration of the problem.

Regards

Thiago

On 9/26/07, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi Thiago,
>
> > Patches for Bluez utils, modifying the sbcenc and sbcparse gstreamer
> > plugins on utils/audio
> >
> >
> > The problem:
> > The pipeline "filesrc ! audioconvert ! sbcenc ! sbcparse ! fakesink"
> > is not working
>
> actually the sbcparse is only there for annotating an SBC stream. For
> decoding the sbcdec should be used.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>

[-- Attachment #1.2: Type: text/html, Size: 2226 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2007-09-26 22:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-25 14:18 [Bluez-devel] patches fixing gstreamer plugins thiagoss
2007-09-25 15:51 ` thiagoss
2007-09-26 22:10 ` Marcel Holtmann
2007-09-26 22:19   ` thiagoss [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=de4879e80709261519s68ca904i19f54905ece3594f@mail.gmail.com \
    --to=thiagossantos@gmail.com \
    --cc=bluez-devel@lists.sourceforge.net \
    /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