From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] sbc and fixed-point progress
Date: Mon, 22 Aug 2005 01:22:07 -0600 [thread overview]
Message-ID: <43097D1F.6050107@xmission.com> (raw)
In-Reply-To: <43096D8C.2020805@xmission.com>
Victor
>> I do not have HW to test arm specific version real time, hope no
>> suprises there, but I could have missed something when integrating it
>> into sbc code (it decodes well, but how fast, I will try only monday
>> evening).
>
>
> Ok, I'll load it on gumstix now and give it a try.
This is almost perfect. On a 400mhz gumstix (pxa255), I'm able to send a
5-minute audio stream with only about three breaks in the audio (about 5
seconds each).
I think it will work flawlessly in 4 subbands or if we can shorten a few
of the ops from 64 to 32 bit.
I committed what's there and used __arm__ for the conditional asm code.
>> Using a2play needs to tweak 87 magic number, otherwise it drops samples?
>
>
> yes, this is disappointing. We may need to find another way to get
> reliable timing than setitimer.
>
> I did change the first usleep(10) to usleep(1000) and that *may* help
> with this problem by ensuring that we always interrupt the usleep
> syscall consistently. I don't have my hp headphones (the set that's very
> sensitive to timing) handy to test.
fwiw, I had to use the -n flag to a2play so it wouldn't use itimer at
all. This flag tells a2play to just send the audio as fast as it can
encode it.
Brad
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-08-22 7:22 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 13:14 [Bluez-devel] sbc and fixed-point progress Victor Shcherbatyuk
2005-07-28 14:59 ` Brad Midgley
2005-07-28 18:41 ` Victor Shcherbatyuk
2005-07-28 19:21 ` Victor Shcherbatyuk
2005-07-28 21:09 ` Brad Midgley
2005-08-21 18:47 ` Victor Shcherbatyuk
2005-08-21 21:56 ` Roberto
2005-08-21 22:24 ` Victor Shcherbatyuk
2005-08-22 6:15 ` Brad Midgley
2005-08-22 7:22 ` Brad Midgley [this message]
2005-09-03 15:33 ` Victor Shcherbatyuk
2005-09-03 16:05 ` Brad Midgley
2005-09-06 21:53 ` Victor Shcherbatyuk
2005-09-07 3:24 ` Brad Midgley
2005-09-03 19:36 ` [Bluez-devel] bcm2035 Oliver Ruiz Dorantes
2005-09-04 12:09 ` Paul Webster
2005-09-04 14:02 ` Oliver Ruiz Dorantes
2005-09-05 4:03 ` Paul Webster
-- strict thread matches above, loose matches on Subject: below --
2005-09-07 7:14 [Bluez-devel] sbc and fixed-point progress Victor Shcherbatyuk
2005-09-07 21:18 ` Victor Shcherbatyuk
2005-08-26 8:07 Victor Shcherbatyuk
2005-08-26 8:02 Victor Shcherbatyuk
2005-08-27 3:01 ` Brad Midgley
2005-08-24 12:18 Victor Shcherbatyuk
2005-08-24 16:40 ` Brad Midgley
2005-08-24 21:06 ` Victor Shcherbatyuk
2005-08-26 5:10 ` Brad Midgley
2005-08-27 22:54 ` Victor Shcherbatyuk
2005-08-28 5:44 ` Brad Midgley
2005-08-28 22:26 ` Victor Shcherbatyuk
2005-08-23 20:42 ` Roberto
2005-08-29 17:08 ` Brad Midgley
2005-08-23 21:10 ` Roberto
2005-08-29 20:18 ` Brad Midgley
2005-08-29 21:04 ` Roberto
2005-08-23 15:00 Victor Shcherbatyuk
2005-08-01 8:20 Victor Shcherbatyuk
2005-08-01 8:41 ` Brad Midgley
2005-07-04 4:03 Brad Midgley
2005-07-04 11:11 ` 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=43097D1F.6050107@xmission.com \
--to=bmidgley@xmission.com \
--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.