<div dir="ltr"><div><div><div>Hi all,<br></div> I have started working on vorbis again and this time We want to port vorbis's fixed point encoder implementation. Do we have any fixed point vorbis encoder? If no then I am going to work on it. Please suggests the steps to do that.<br><br></div>Thanks,<br></div>Karan<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 30, 2013 at 12:30 AM, <span dir="ltr"><<a href="mailto:tremor-request@xiph.org" target="_blank">tremor-request@xiph.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Tremor mailing list submissions to<br>
<a href="mailto:tremor@xiph.org">tremor@xiph.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.xiph.org/mailman/listinfo/tremor" rel="noreferrer" target="_blank">http://lists.xiph.org/mailman/listinfo/tremor</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:tremor-request@xiph.org">tremor-request@xiph.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:tremor-owner@xiph.org">tremor-owner@xiph.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Tremor digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. fixed_point_encoder (karan tandel)<br>
2. Re: fixed_point_encoder (Ralph Giles)<br>
3. Re: fixed_point_encoder (Timothy B. Terriberry)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 29 Oct 2013 18:58:35 +0530<br>
From: karan tandel <<a href="mailto:tandelkaran@gmail.com">tandelkaran@gmail.com</a>><br>
Subject: [Tremor] fixed_point_encoder<br>
To: "<a href="mailto:tremor@xiph.org">tremor@xiph.org</a>" <<a href="mailto:tremor@xiph.org">tremor@xiph.org</a>><br>
Message-ID:<br>
<<a href="mailto:CA%2B_q5_qcRdP3NZdC4OPGTcwanWXxWgs%2BKm7xE%2BcsepBgp0ynbA@mail.gmail.com">CA+_q5_qcRdP3NZdC4OPGTcwanWXxWgs+Km7xE+csepBgp0ynbA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Hi,<br>
I have to port libvorbis encoder on Android. But as it is floating point<br>
only Its not showing good timing performance. So for that I need to port<br>
fixed point encoder. I have done so much searching but I didnt find any<br>
fixed point vorbis encoder. So please provide some pointers regarding<br>
these issues.<br>
1. Is there any fixed point encoder available?<br>
2. If not then what should I do to make it fixed point implementation?<br>
<br>
Thanks in advance,<br>
Karan<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.xiph.org/pipermail/tremor/attachments/20131029/3b3308c5/attachment-0001.htm" rel="noreferrer" target="_blank">http://lists.xiph.org/pipermail/tremor/attachments/20131029/3b3308c5/attachment-0001.htm</a><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 29 Oct 2013 10:52:49 -0700<br>
From: Ralph Giles <<a href="mailto:giles@thaumas.net">giles@thaumas.net</a>><br>
Subject: Re: [Tremor] fixed_point_encoder<br>
To: <a href="mailto:tremor@xiph.org">tremor@xiph.org</a><br>
Message-ID: <<a href="mailto:526FF5F1.3070005@thaumas.net">526FF5F1.3070005@thaumas.net</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
On 2013-10-29 6:28 AM, karan tandel wrote:<br>
> Hi,<br>
> I have to port libvorbis encoder on Android. But as it is floating<br>
> point only Its not showing good timing performance. So for that I need<br>
> to port fixed point encoder. I have done so much searching but I didnt<br>
> find any fixed point vorbis encoder. So please provide some pointers<br>
> regarding these issues.<br>
> 1. Is there any fixed point encoder available?<br>
<br>
Not that I'm aware of, no. It's unfortunate.<br>
<br>
> 2. If not then what should I do to make it fixed point implementation?<br>
<br>
Write fixed point forward versions of the inverse coding functions in<br>
tremor, like the forward mdct, floor curve generation, etc. Then port<br>
over the analysis and mode choice code from libvorbisenc. The main issue<br>
is to ensure you maintain enough dynamic range during calculations.<br>
<br>
Then submit your code for review an incorporation upstream, of course.<br>
:-)<br>
<br>
See also <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=932390" rel="noreferrer" target="_blank">https://bugzilla.mozilla.org/show_bug.cgi?id=932390</a><br>
<br>
-r<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 29 Oct 2013 11:03:07 -0700<br>
From: "Timothy B. Terriberry" <<a href="mailto:tterribe@xiph.org">tterribe@xiph.org</a>><br>
Subject: Re: [Tremor] fixed_point_encoder<br>
To: <a href="mailto:tremor@xiph.org">tremor@xiph.org</a><br>
Message-ID: <<a href="mailto:526FF85B.6080507@xiph.org">526FF85B.6080507@xiph.org</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Ralph Giles wrote:<br>
> over the analysis and mode choice code from libvorbisenc. The main issue<br>
> is to ensure you maintain enough dynamic range during calculations.<br>
<br>
The good news is that because you're writing an encoder, not a decoder,<br>
you don't have to support everything (in particular, floor0, which is<br>
the hardest part to do with enough precision). So in that sense encoding<br>
is much easier than decoding.<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Tremor mailing list<br>
<a href="mailto:Tremor@xiph.org">Tremor@xiph.org</a><br>
<a href="http://lists.xiph.org/mailman/listinfo/tremor" rel="noreferrer" target="_blank">http://lists.xiph.org/mailman/listinfo/tremor</a><br>
<br>
<br>
End of Tremor Digest, Vol 67, Issue 2<br>
*************************************<br>
</blockquote></div><br></div>