Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Comments about the Logitech/HP stereo headphones
Date: Sun, 24 Apr 2005 20:15:03 +0200	[thread overview]
Message-ID: <1114366503.10706.123.camel@pegasus> (raw)
In-Reply-To: <20050424164810.GA12143@externe.net>

Hi Guylhem,

> > My 0.02EUR: There is a problem here. Mayank turned up a very valid point
> > in his "a2play code not according to the specifications" posting: Having
> > the SBC encoding decoupled from the AVDTP negotiation is not a good
> > thing. One of the primary problems of the current pipe approach (and
> > expecting applications to stream SBC into a socket/device/whatever is
> > not different in this regard) is that the format of the SBC stream
> > (sample rate, channel mode, etc.) will have to depend on the
> > capabilities of the receiver, but there is no feedback to the encoder
> > about that.
> 
> Maybe the supported encodings/frequencies/etc. could be advertised in
> a separate file? The player would open it first, then send the sbc
> in one of the supported format

the advertised endpoints, encodings etc. can change dynamically and so
you would always need a L2CAP link on PSM 25 first. So this can't be an
option.

> > And also coupling /dev/a2dpN tightly to SBC format would make it even
> > harder (or impossible) to support other audio formats as A2DP does.
> 
> That was just a suggestion on the system behaviour - I mean having a
> device supporting a format. You could as well have
> /dev/a2dp0_sbc_someformat /dev/a2dp0_sbc_someotherformat etc. and try
> to open them until once doesn't return an error.

This is an ugly interface and won't even work. Do you wanna create a
connection to the headphone for every device node that you are testing?

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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-04-24 18:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-24 12:18 [Bluez-devel] Comments about the Logitech/HP stereo headphones Marcel Holtmann
2005-04-24 13:47 ` Guylhem Aznar
2005-04-24 14:28   ` Brad Midgley
2005-04-24 15:23     ` Marcel Holtmann
2005-04-24 15:16   ` Marcel Holtmann
2005-04-24 17:11     ` Guylhem Aznar
2005-04-24 18:09       ` Marcel Holtmann
2005-04-24 20:28       ` Brad Midgley
2005-04-24 16:19   ` Henryk Plötz
2005-04-24 16:48     ` Guylhem Aznar
2005-04-24 18:15       ` Marcel Holtmann [this message]
2005-04-24 18:12     ` Marcel Holtmann
2005-04-24 14:04 ` Brad Midgley
2005-04-24 14:34   ` Brad Midgley
2005-04-24 15:30   ` Marcel Holtmann
2005-04-25 17:39     ` Brad Midgley
  -- strict thread matches above, loose matches on Subject: below --
2005-04-24 15:16 Mayank Batra
2005-04-24 15:35 ` Marcel Holtmann
2005-04-26 12:46 Mayank Batra
2005-04-26 13:28 ` Marcel Holtmann
2005-04-28 12:10 Mayank Batra
2005-04-29  9:51 ` Marcel Holtmann

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=1114366503.10706.123.camel@pegasus \
    --to=marcel@holtmann.org \
    --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