From: Nils Faerber <nils.faerber@kernelconcepts.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] i.Tech Clip S38 - MP3 streaming?
Date: Fri, 09 Nov 2007 17:07:51 +0100 [thread overview]
Message-ID: <473485D7.8080101@kernelconcepts.de> (raw)
In-Reply-To: <d89ddf300711090727u3aa0b50bie97615df7c71d195@mail.gmail.com>
Brad Midgley schrieb:
> Nils
Hi Brad!
>> I have one of those "i.Tech Clip S38" laying quite uselessly on my desk...
> I have a similar r35. mp3 is a different codec that you choose when
> negotiating the connection. I made the old a2play detect the codec but
> never did try to use it.
Ah, cool, that's what I thought...
> The right approach is to work with the gstreamer plugins inside
> bluez-utils so the codec negotiation happens the gst way. This way an
> mp3 stream would naturally choose the mp3 decoder as the optimal
> selection.
Uh, OK ;)
Yeah, nothing comes for free, so I will have to look into this.
Many thanks for your hints/advice!
Cheers
nils faerber
--
kernel concepts GbR Tel: +49-271-771091-12
Sieghuetter Hauptweg 48 Fax: +49-271-771091-19
D-57072 Siegen Mob: +49-176-21024535
--
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-11-09 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 15:20 [Bluez-devel] i.Tech Clip S38 - MP3 streaming? Nils Faerber
2007-11-09 15:27 ` Brad Midgley
2007-11-09 16:07 ` Nils Faerber [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=473485D7.8080101@kernelconcepts.de \
--to=nils.faerber@kernelconcepts.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.