From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] more encoder stuff
Date: Thu, 25 Nov 2004 07:51:24 +0100 [thread overview]
Message-ID: <1101365484.7538.74.camel@pegasus> (raw)
In-Reply-To: <20041125071423.10e449c3.henryk@ploetzli.ch>
Hi Henryk,
> > you were saying the reference encoder runs faster. Is there
> > any chance they are using vector processing like sse/sse2? Do projects
> > like xine and mplayer detect and use a vector processor through a
> > library?
>
> Nope, that was an error on my side. My file output was awfully slow. I
> didn't test with large files since then, though. However, I_did_ profile
> it and know that most of the encoding time is spent in sbc_analyze_audio
> (no surprise there) in the matrixing, windowing and partial calculation
> stages.
>
> I just tested it again with a -O3 compiled sbcenc:
>
> | time wine sbc_encoder.exe -o Uninvited.sbc Uninvited.wav
> gives
> | real 0m30.095s
> | user 0m18.766s
> | sys 0m0.686s
>
> | time ./sbcenc Uninvited.au > Uninvited.sbc
> gives
> | real 0m36.539s
> | user 0m27.200s
> | sys 0m1.500s
>
> That's not _too_ bad, especially since they are using dual channel while
> we are using stereo (the latter gives smaller file size in this case).
there exists a switch to sbc_encoder.exe to tell them to use stereo or
joint stereo.
> By using CC=icc CFLAGS="-O3 -tpp7 -march=pentium4" I can easily get it
> down to
> | real 0m19.122s
> | user 0m11.272s
> | sys 0m1.474s
The MAD library (www.underbit.com/products/mad/) is using fixed-point
integer computation. Do you think it is possible to do the same thing
for SBC? Will it give us some extra performance?
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:51 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
2004-11-25 6:14 ` Henryk Plötz
2004-11-25 6:51 ` Marcel Holtmann [this message]
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=1101365484.7538.74.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