From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Cc: bmidgley@xmission.com
Subject: Re: [Bluez-devel] more encoder stuff
Date: Thu, 25 Nov 2004 07:02:19 +0100 [thread overview]
Message-ID: <1101362539.7538.61.camel@pegasus> (raw)
In-Reply-To: <41A56774.1000308@xmission.com>
Hi Brad,
> It was fantastic listening to my headset on the bus today. I didn't have
> to deal with the bluetake dongle at all... very nice.
I updated the a2play program to detect my buggy Aiptek headphone and
activate the non specification conform use of SBC audio. Actually I did
changes at many places in the code, because the parameter sets of some
functions had to be changed. And I also cleaned up some mess that was
generated by Lindent.
> What should I be using if I want to encode live from the computer's
> line-in? (I want to see if encoding on the computer results in shorter
> latency than the bluetake dongle. Watching TV with the headset is
> currently not all that fun because of the delay.)
Maybe something like this might work:
arecord -f cd -t au /dev/stdout | sbcenc - | a2play <bdaddr> -
> We should get Sonorix to send us a headset for testing. Have you had
> much luck with vendor cooperation, Marcel? Right now in a2play we sort
> of assume the headset will only report one codec and I suspect they
> support mp3 natively. (It's possible they are pulling tricks like
> transcoding into SBC before uploading mp3's to the headset's flash
> memory I guess.)
In the past I only talked to Aiptek and they won't send me a headphone
for free and so I finally bought one by myself. Right now I think that I
also need the Bluetake headphone, but I don't like to buy another one by
myself. The Sonorix and also the Logitech (sold as HP model for iPAQs at
the moment) are two other interesting headphones. In general it is no
problem for the companies to donate a bunch of their devices, but you
need to talk to right people. As you might have seen on the BlueZ page
there are some friendly companies. They have no problems in giving away
their hardware to developers for free.
http://www.bluez.org/sponsors.html
May you simply try to contact Sonorix and put me on CC. If they care
about Linux and Bluetooth they should really know my name. And I think
we need actually three of these headphones. One for each of us.
Another way is if people like our work they may donate some money or buy
one of these devices and send it to us. Anyone feel free to contact me
by private email about this.
To answer your MP3 question, I don't know. At the moment I don't expect
any headphones with more than one codec or even with more than one SEID.
The biggest problem might be that the MP3 codec is not license free, but
SBC is. The total cost calculations for software and hardware (including
the firmware) are different.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-11-25 6:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 5:02 [Bluez-devel] more encoder stuff Brad Midgley
2004-11-25 6:02 ` Marcel Holtmann [this message]
2004-11-25 6:14 ` Henryk Plötz
2004-11-25 6:51 ` Marcel Holtmann
2004-11-25 14:35 ` Lars Grunewaldt
2004-11-25 23:06 ` Henryk Plötz
2004-11-25 23:23 ` Marcel Holtmann
2004-11-26 0:14 ` Lars Grunewaldt
2004-11-26 0:44 ` Marcel Holtmann
2004-11-26 0:57 ` Lars Grunewaldt
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=1101362539.7538.61.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bmidgley@xmission.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