similar to: Re: [no subject]

We've implemented a vorbis decoder based on Tremor and as part of the documentation we're also writing about psycho acoustic models and encoding. We're quite up to date with the decoding process and psycho acoustics in general but unfortunately not on the psycho acoustic encoding used in Vorbis. We have a few questions that would we would be very thankful to have answer to: Which

Hi Tom Thanks, just at the feasibility phase right now, so this sort of info is really useful. Memory/MHz values for the Tremor/Vorbis code seem to vary wildly - at least I could not find a consistent set of numbers after trawling through the discussion groups... Thanks John -----Original Message----- From: tom abcd [mailto:tom.abcd@gmail.com] Sent: 28 March 2006 16:34 To: Anderton, John

Hiya, Here is the sources to my "rehuff" program. ./rehuff in.ogg out.ogg does a lossless recoding of a vorbis stream. (It generates optimal huffman codes for the particular stream). This code is meant for developers only, until someone is kind enough to provide good build and configure support for it. I won't. And no installation help questions please. There is a little patch

Can anybody point me at any resources that would explain how to optimize mdct_backward for a cpu with a fused multiply-accumute unit? >From what I understand from responses to my older postings, Tremor's mdct_backward could be rewritten to take advantage of a muladd. My target machine can do either two-wide 32x32 + Accum(64) -> Accum(64) integer muladd or eight-wide 16x16 + Accum(32)

Hi Everybody: Below is this week's Ogg Traffic in plain text. The HTML version is available at http://www.vorbis.com/ot/20030331.html Enjoy! Ogg Traffic for Monday, March 31, 2003 [1]Carsten "Purple" Haese March 31, 2003 _________________________________________________________________ Table of Contents 1. Status Updates 1.1. Monty 1.2. Michael

Reinventing the wheel is fun. I've just got working a (sort of) complete implementation of vorbis using (very nearly) only the documentation. This was quite easy overall as the documentation is very comprehensive and clear. Nice job, whoever put it together! The one spot I had some trouble with was the low level residue decode. The pseudo code at

Áô©~ªº ¦Ñ¤H wrote: > Dear Segher > > Thanks for your information. Besides, the mechanism of the huffman > decoding seems can not work in a 24-bit processor if the code length > exceeds 24, though I have checked several vorbis file from network and > they are all below 24 bit True; but you can special case the >24 bit codebook to use a more "traditional" decoding

Hi All, Currently I am investigating how interesting OGG is for me. The most important requirements are: - Decoding on embedded hardware, ARM7 or ARM9. - Mixing multiple audio streams/files on embedded hardware First of all how difficult is it to decode OGG on an ARM7/9 processor? I read that OGG decoding needs floating point support? Secondly I would like to know how many MIPS are needed to

Hello Joost, I would like to say since you seem to understand what Vorbis is since you are in the appropriate list that you should not refer to it as "OGG". First, because Ogg is not Vorbis -- it's a container. Second, because Ogg is not an acronym. Vorbis decoding help is what you are looking for. With that said, let's see if I can help you. On 11/6/07, Joost Meijles

Hi everybody: Here is this week's Ogg Traffic with all new updates on recent activities in the world of Xiph.org. The HTML version is up at http://www.vorbis.com/ot/20030415.html. Enjoy! -Carsten <p>Ogg Traffic for Tuesday, April 15, 2003 [1]Carsten "Purple" Haese April 15, 2003 _________________________________________________________________ Table of

Hello, I was wondering if it is possible to change the huffman stuff? A different mapping maybe, or maybe it is not too late to change? Decoding is much more efficient if: -- the huffman tree is left-aligned (i.e., longer codes more to the left) -- and we get the bits msb, not lsb Oh, and I need some clarification about the lsp: the purpose of the lsp is to find a low-bitcount approximation of

Dear All, As i have understood it , the Huffman codebook uses a huffman code present in the bitstream ( lets us say it is decoding a floor 1 Y value using the specifed codebook number ) to walk through the huffman code book tree till it hits a leaf node which is nothing but the entry number. If we consider our floor 1 Y value example , this entry number is directly being used as the Y value.

Hi, I am trying to understand the building of Huffman codes from the code lengths. In the Tremor code first I see that the codewords are being generated by the function _make_words() and then sorted. After this I see some magic code and something related to unused entries. Does the code generate code words for unused entries too? Are these unused entry code words used during the decode

Hi, Debian Project News drew my attention to an RFH http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698378 for a crash in libvorbisidec (tremor) on ARM systems. I have been in contact with Daniel Kahn Gillmor proposing to try to help solve this crash on armel. Unfortunately Daniel hasn't been able to reproduce it recently. Can anyone shed any light on this crash or on how to reproduce

I wrote to the list earlier about optimizations of the tremor. Specially replacing the IMDCT with a N/4 FFT. The report is available here: http://www.sandvall.nu/thesis.pdf Short summary: Optimization of the Tremor code under 50kB for a "split" decoder version. ~44 MIPS. Huffman highly unoptimized. IMDCT ~ 8 MIPS. Quick overview of the

Hi Segher, On Sun, Dec 2, 2018 at 3:48 PM Segher Boessenkool <segher at kernel.crashing.org> wrote: > > On Fri, Nov 30, 2018 at 10:06:02AM +0100, Boris Petkov wrote: > > On November 29, 2018 1:25:02 PM GMT+01:00, Segher Boessenkool <segher at kernel.crashing.org> wrote: > > >This will only be fixed from GCC 9 on, if the compiler adopts it. The > >

Well, here you are. 24k; sorry if I'm not supposed to put this size things in your mailbox, didn't know where else to put it. And you all are subscribed to vorbis-dev, after all. I'm not that good at breaking patches apart, so it's one big patch. Sorry. Overview: configure.in make profiling easier & more useful decoder-example.c (#if 0'ed) dither output;

* Segher Boessenkool <segher at kernel.crashing.org> wrote: > On Mon, Oct 08, 2018 at 11:07:46AM +0200, Richard Biener wrote: > > On Mon, 8 Oct 2018, Segher Boessenkool wrote: > > > On Sun, Oct 07, 2018 at 03:53:26PM +0000, Michael Matz wrote: > > > > On Sun, 7 Oct 2018, Segher Boessenkool wrote: > > > > > On Sun, Oct 07, 2018 at 11:18:06AM

Hi. On Wed, Oct 10, 2018 at 1:14 AM Segher Boessenkool <segher at kernel.crashing.org> wrote: > > On Mon, Oct 08, 2018 at 11:07:46AM +0200, Richard Biener wrote: > > On Mon, 8 Oct 2018, Segher Boessenkool wrote: > > > On Sun, Oct 07, 2018 at 03:53:26PM +0000, Michael Matz wrote: > > > > On Sun, 7 Oct 2018, Segher Boessenkool wrote: > > > > >

Hi. On Wed, Oct 10, 2018 at 1:14 AM Segher Boessenkool <segher at kernel.crashing.org> wrote: > > On Mon, Oct 08, 2018 at 11:07:46AM +0200, Richard Biener wrote: > > On Mon, 8 Oct 2018, Segher Boessenkool wrote: > > > On Sun, Oct 07, 2018 at 03:53:26PM +0000, Michael Matz wrote: > > > > On Sun, 7 Oct 2018, Segher Boessenkool wrote: > > > > >