similar to: [oggonachip] Ogg-on-a-Chip project first phase finished (fwd)

Hi all, This is to say hello to all of you as we are starting the project Ogg on a Chip for our master thesis. More information can be found at http://oggonachip.sourceforge.net/. Cut from the homepage: "The Ogg Vorbis Player (http://www.xiph.org/ogg/vorbis/index.html) shall be implemented in form of a system-on-a-chip by using hardware/software co-design techniques. A prototyping board

Better late than never :) jack. --- Ogg Traffic for Tuesday, November 13, 2001 Jack Moffitt <[1]jack@xiph.org> _________________________________________________________________ Table of Contents 1. [2]Support The Ogg Project 2. [3]Status Updates 2.1. [4]Stan Seibert 2.2. [5]Chris Wolf 3. [6]New Developments 3.1. [7]Ogg On A Chip

Hi, in order to understand the Ogg Vorbis decoding algorithm, do you recommend any document/book/www? I have read those on the web page but look for something more detailed.. Thank you very much, Pattara The best things in life are free. - B.G. DeSilva (1927) ---------------------------------------------------------------------- Ott Pattara Kiatisevi T L W G M.Sc. INFOTECH Student,

Hi, as we are trying to implement MDCT in hardware, we are caring now about the "n" (size of input and output vectors to and from MDCT). As I have looked in the code, this "n" is chosen from the Ogg/Vorbis stream data in info.c:_vorbis_unpack_info() which means this "n" can vary aribitrarily (as the power of 2) depending only on the value got from song data? or is

Hi vorbis-dev! I'm working with Pattara in the oggonachip project, and wondering about the implementation of mdct.c as hardware. According your recomendations about using the floating point version, I would say, we have to implement the integerized version of mdct as a core, and use the fpu only to round the input values. By doing that, you think the result would be still acceptable? How

Hi, I wonder if there is specific requirement or restriction for the decoder in order to be consider "Vorbis" compliant (or let's say, to be a "correct" vorbis decoder). I am experimenting with integerized libvorbis and the decoder delivers the audio data as following, (and compare with the floating point version below). $ tail audioout-int.txt 0290670 025e 085c 02cf 0895

Hi vorbis-dev, I'm investigating the mdct* function in libvorbis and writing a small client program to test it. I found that I have to set ARRAYSIZE when mdct_init(lookup, ARRAYSIZE) to minimum value of 62 otherwise it will segfault with mdct_backward. Is there any lower limit or it is more likely that my code has bug? Thank you very much, Pattara -- Please avoid sending me Word or

Hi Vorbis, Now I get libvorbis-rc3 + integerized mdct_backward + integerized window running. The sound output is ok. Now we have to go further on possible optimization of the code in order to have the music played realtime on our chip (LEON-Sparc). There are 2 possible ways: 1.Make everything integer, remove all floating point usage. Then we can remove FPU and can run the chip at higher

Hi, Today I tried to run my player code with the CVS libvorbis (instead of RC3 as usual) and I found the infinite loop here (lines prefixed with >> are in the loop): tatic ogg_int64_t _get_prev_page(OggVorbis_File *vf,ogg_page *og){ ogg_int64_t begin=vf->offset; ogg_int64_t end=begin; ogg_int64_t ret; ogg_int64_t offset=-1; >> while(offset==-1){ >>

Hi, I have a question about compiling Ogg/Vorbis. As I plan to have the code run on the LEON/SPARC CPU so I have to use sparc-rtems-gcc, sparc-rtems-ld, sparc-rtems-ranlib. Now, in order to compile the libs, e.g., libogg, I have to create my own Makefile like this: PROG=bitwise framing CC=sparc-rtems-gcc AR=sparc-rtems-ar RANLIB=sparc-rtems-ranlib CFLAGS=-rtems -msoft-float -Wall -W -g

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've been wanting to try out Squat for full-text indexing for a while now, so I finally gave it a whirl. I did a fresh pull from hg. I have it enabled, but it's taking *forever* to do a query. (Using alpine, I issued a Select command for all messages with some word anywhere, which presumably caused the Squat indexer to run.) I think Dovecot is infinite looping. I thought something

Greetings -- Many of you have downloaded and tried out Astmanproxy, a multi-threaded C-based proxy for Asterisk's Manager Interface. It has been under development since April 2005 and was presented at the Madrid Astricon in June, and will also be presented at Astricon in Anaheim in October. There has been interest in setting up an Astmanproxy mailing list specifically devoted to

(Cross posted to speex-dev from iglance) Enzo -- I haven't tried the fixed point engine, though I've considered it for the WinCE port. For the desktop/laptop edition I'm assuming the slight short->float conversion cost will be made up by the improved performance of the floating point implementation. But I could be wrong: 1) Can anyone recommend whether Speex performs better

Here you go, Ian...... ---------- Forwarded message ---------- From: G3RIR <g3rir@yahoo.com> Date: 05-Apr-2006 20:54 Subject: [dmuars] Eh up - March 144 results altered To: dmuars@yahoogroups.com What's going on here. The results of the MArch 144 UKAC have been re-published and we have lost out considerably. Either I don't understand the rules or we have been robbed We scored

Paul, I also think that bridge may not be the right place for VEPA, but rather a simpler sw/hw mux Although the VEPA support may reside in multiple places (I.e. also in the bridge) As Arnd pointed out Or already added an extension to qemu that allow direct guest virtual NIC mapping to an interface device (vs using tap), this was done specifically to address VEPA, and result in much faster

Paul, I also think that bridge may not be the right place for VEPA, but rather a simpler sw/hw mux Although the VEPA support may reside in multiple places (I.e. also in the bridge) As Arnd pointed out Or already added an extension to qemu that allow direct guest virtual NIC mapping to an interface device (vs using tap), this was done specifically to address VEPA, and result in much faster

Paul, I also think that bridge may not be the right place for VEPA, but rather a simpler sw/hw mux Although the VEPA support may reside in multiple places (I.e. also in the bridge) As Arnd pointed out Or already added an extension to qemu that allow direct guest virtual NIC mapping to an interface device (vs using tap), this was done specifically to address VEPA, and result in much faster

ugh, some new evil spamming technique? send a group invite to mailing lists, hoping one of the members will join? Josh --- b3ta Moderator <b3ta-owner@yahoogroups.com> wrote: > > Welcome to B3ta > > It's a free weekly newsletter reporting on the coolest stuff on the > net. > > We work very hard to make best thing in your inbox this week. > > We also use

Hello listers, I and my class-mates intend to study the Ogg and Vorbis formats. Also we want to study and imprve upon or develop a wholly new, Ogg & Vorbis decoder for playing .ogg files. Kindly guide me into this. Please tell if there are any existing ogg decoders available for studying. The JOrbis team, has unfortunately been non-cooperative, with no replies despite a number of requests.