Linux bluetooth development
 help / color / mirror / Atom feed
From: "Henryk Plötz" <henryk@ploetzli.ch>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] yes, a2dp timing is whacked
Date: Sat, 7 May 2005 03:13:14 +0200	[thread overview]
Message-ID: <20050507031314.548afb03.henryk@ploetzli.ch> (raw)
In-Reply-To: <42792979.90109@xmission.com>

[-- Attachment #1: Type: text/plain, Size: 833 bytes --]

Moin,

Am Wed, 04 May 2005 13:58:49 -0600 schrieb Brad Midgley:

> Maybe for convenience, libsbc should compute the timeslice for the
> frame.

It does now. I added a function sbc_time(sbc_t *sbc) which computes the
microseconds for one frame. I then replaced the fixed value in a2play's
usleep() call with the time the whole packet should take to play (time
for one frame times number of frames in the packet) multiplied by
(arbitrarily chosen) 0.8 to make up for the time lost with computing and
sending.

> I will start by looking at the rtc interface and trying to find hooks
> in alsa for timing.

That would be really cool.

-- 
Henryk Plötz
Grüße aus Berlin
~~~~~~~ Un-CDs, nein danke! http://www.heise.de/ct/cd-register/ ~~~~~~~
~ Help Microsoft fight software piracy: Give Linux to a friend today! ~

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-05-07  1:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-04 19:58 [Bluez-devel] yes, a2dp timing is whacked Brad Midgley
2005-05-07  1:13 ` Henryk Plötz [this message]
2005-05-07  1:26   ` Marcel Holtmann
2005-05-07 19:27     ` Marcel Holtmann
2005-05-07 20:20       ` Henryk Plötz
2005-05-07 20:45         ` Marcel Holtmann
2005-05-09  6:34           ` Brad Midgley
2005-05-09  7:21             ` Brad Midgley
2005-05-09 21:27               ` Brad Midgley

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=20050507031314.548afb03.henryk@ploetzli.ch \
    --to=henryk@ploetzli.ch \
    --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