similar to: integer decoder

Is anybody going to do something about the fact that vorbis decoder won't run on ARM processors (iPaq's, etc) or any (that I know of) car music players? How can vorbis expect to compete when one of the most popular uses of MP3 is in the car?? Though I would love to switch to vorbis, I am forced to stick with MP3 because of this. I emailed a previous poster here who appeared to be

Hi I have gone through the document available in the net regarding the Vorbis encoder /Decoder. Based on that i have prepared a understanding document on the encoder/decoder block. I would like to know whether my understanding of the coder is OK. If there are any other additional block /information pl. provide me with the same. Thanks and regards S.Padmashri <HR NOSHADE> <UL>

Hi Any help is appreciate! These days I studied ogg vorbis encoder with sample rate 44.1kbsp,and I thought the whole chart was as follows: 1. read the PCM data and store them in a buffer 2. do MDCT on those PCM data 3. do FFT on those PCM data 4. use both the FFT and MDCT coefficient to the psychoacustic modle and derive an maximum allowable noise curve, and during this curse ,do the

Hi! I've spent the last few nights digging into the Vorbis source and working to implement a vorbis_synthesis_pcmout_int() function that kicks out interleaved int16_t pcm data. I think its important to have this function available to make the job for people using the codec a little easier. This function abstracts out the conversion to int16_t and removes the extra overhead of moving the pcm

I've made a block diagram of the encoder because I tried to find out, how it works http://stoffke.freeshell.65535.net/ogg/block.html Although there are specifiation docs, that give very detailed information about single aspects of the encoding (or decoding) , I'm missing documenations that give a more general overview, about how the encoder works. (Vorbis Illuminated seems a bit

I'm considering creating an ogg vorbis decoder chip for my senior project in school. At this point, my idea is to have a program (such as XMMS, ogg123, WinAMP) send the encoded ogg bitstream through a USB port to my project, which is then decoded. My project then returns the raw PCM audio, which is then handled by the player program for final audio output. I'm planning on USB as it

I write a work over Vorbis. ? ?Now I have a few questions to the function. ? ?For what is the MDCT used? ? ?For what is the FFT used? ? ?How is the expiration with the encodieren? ?In the reference to the MDCT,FFT and the hearing model . ? ?Is there a volume fragmentation in Subband as MP3? ? ?If it is possible, the answers in the detail ?Thanks ? -------------- next

Great job! I'm considering converting all my mp3 files to Vorbis format. Only examples/encoder_example is a bit too simplistic (of course, being an example), and the cmdline tools aren't ready. I encode my mp3 files at 96 kbit/s, because that's enough for me. Will Vorbis do well at this rate? Any quick hacks I can make to examples/encoder_example.c? Perhaps Vorbis is of interest

Hi all, Does anyone have any experience porting libvorbis to platforms with small total memory sizes? Specifically, I'm trying to figure out if it's feasible to run Ogg Vorbis decoding on one of the PlayStation 3's SPU's -- secondary processors with only 256kb of local memory. It looks like out of the box the memory footprint of libvorbis is roughly: ~130k code ~60k static

Hello All, I extended the libNE10 optimizations for float towards mdct_backwards/opus_ifft. I am able to get about 14.26% improvement for Decode use case now on my Beaglebone Black. Please see [1] for measurements. Questions 1. Since this patch needs to go in after Encode [2] patch) should I submit this as patch series? 2. Since Jonathan Lennox posted intrinsics cleanup [3] patch, should

I tracked down the bug to an incorrect use of restrict. I would not consider this a compiler bug: we are lying to the optimizer by telling it that a pointer is restrict when in fact it isn't. This can be fixed like so: diff --git a/celt/mdct.c b/celt/mdct.c index 1634e8e..fa5098c 100644 --- a/celt/mdct.c +++ b/celt/mdct.c @@ -276,8 +276,8 @@ void clt_mdct_backward(const mdct_lookup *l,

Hello Vorbis folks, I'm one of the FFTW authors (www.fftw.org), and a few days ago I was playing with our codelet generator for fun and modified it to spit out hard-coded MDCTs of small sizes. The code (at jdj.mit.edu/~stevenj/mdct_128nr.c) for 256 samples (128 outputs) seems to be almost twice as fast as the Vorbis MDCT code for that size on my 2.2GHz P-IV (gcc 3.2.2 and flags "-O1

Thread-split from the vorbis-mailing list ("Vorbis determined to be as good as MPC at 128 kbps!") <p>On Sun, 30 May 2004, Segher Boessenkool wrote: [Steven So] SS>> If iTunes AAC can encode castanets with much less pre-echo at SS>> ABR 128 kbps, then hopefully there will be an imaginative SS>> (and non-patented) way of doing this in Vorbis without the SS>>

Dear all I'm working on the implementation of the MDCT for the processor ARM-Cortex-M4 I'm trying to replicate the behavior of the MDCT for several overlapped values however I realized that current implementation of the MDCT is very close to the theory only in case in which we have and overlap exactly equal to N/2 where N is the size of the input vector as is shown in the examples for

Here's a patch to fix some bugs in my code, plus a header file I probably forget to send in before. * Missing header file charset.h. It's not needed outside vorbis-tools/share, so I think it can live there. * There was a minor bug in the UTF-8 decoder utf8_mbtowc(). * I've added some more tests in charset_test.c in an attempt to convince myself that there aren't any more bugs.

After a few experiments, I found that both alternatives are very similar, and 2~5% slower compared to the following: diff --git a/celt/mdct.c b/celt/mdct.c index 1634e8e..e490c3b 100644 --- a/celt/mdct.c +++ b/celt/mdct.c @@ -277,7 +277,7 @@ void clt_mdct_backward(const mdct_lookup *l, kiss_fft_scalar *in, kiss_fft_scala it in-place. */ { kiss_fft_scalar * OPUS_RESTRICT yp0 =

In mdct.c there's some functions including some-point butterfly. In 32-point and 16-point there are calling of smaller-point function everytime twice on each half of data. When I looked on it I found that's just linear algebra. So it can be rewritten to matrix multiplication. Some one can say: there's optimization on in register working. But imagine there's one calling 32-point,

I am attempting to port CELT to the TI C5515 DSP. I am compiling/assembling/linking with Code Composer Studio 4. I have enabled the TI_55 specific optimizations in my config.h file per this <http://lists.xiph.org/pipermail/celt-dev/2008-December/000033.html> post. However, I am getting several "undefined symbol" linking errors that do not make sense to me. According to the error

My ogg library is located in /home/warren/local. So when I configure and compile the vorbis module on my linux box using configure --with-ogg-prefix=/home/warren/local make I get the following error during the make: gcc -DPACKAGE=\"libvorbis\" -DVERSION=\"1.0.0\" -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -I. -I. -I../include -O20 -ffast-math -mno-ieee-fp -D_REENTRANT

Hi, I'm currently working on a paper describing Ogg Vorbis. It is not finished yet. Mostly the decoder is being described. If you have any comments, please send them to me. See: http://www.turbocat.net/~hselasky/math/vorbis/files/ Then I have a question about the function "bark_noise_hybridmp()" which is used in the encoder. Can someone describe what the function does in