From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] yes, a2dp timing is whacked
Date: Sat, 07 May 2005 03:26:41 +0200 [thread overview]
Message-ID: <1115429201.9031.5.camel@pegasus> (raw)
In-Reply-To: <20050507031314.548afb03.henryk@ploetzli.ch>
Hi Henryk,
> > 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.
the time that is eaten up by encoding or decoding could be measured with
gettimeofday() and then you can subtract this from the whole time.
Since it is a linear operation we can make the SBC library do it all for
us. Let sbc_encode() and sbc_decode() calculate the processing time and
then store a sleep value for us inside sbc_t.
And the value should be really unsigned long and not int.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-05-07 1:26 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
2005-05-07 1:26 ` Marcel Holtmann [this message]
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=1115429201.9031.5.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