similar to: high frequencies response

Hi, I am trying to implement a Vorbis decoder in Java, and I have some problems understanding the file-format specification included with libvorbis. In the header description, there are a few obvious mistakes, which I believe to have solved, but when I try to decode the audio packets, the decoded floor and residue data doesn't seem to make sense at all, and after a few packets, my decoder

Hello, I would like to know how to find out the specifications (flow chart, transforms, tables, windowing operations, bitstream formatting) used to encode/decode audio in OggVorbis format. I mean something similar to the ISO/IEC 11172-3 document for MPEG-I and the like. Regards, ---------------------------------------------------- Jaime Andrés Aranguren Cardona SanJaaC Electronics

Hi, it seems to me as if all vorbis-files only contain floors of type 1 and residues of type 2. Is it possible to "force" the encoder to somehow create a vorbis-file with the other floor and residue types? Tor <p><p><p>=================================================================== EASY and FREE access to your email anywhere: http://Mailreader.com/

Fredag, 11 oktober 2002, skrev du: >Rubbish. Been there, done that (multiple times). Look at rehuff, for >example; written without looking at libvorbis (nor at the spec). And you wrote that without any knowledge about the file format? Tor <p><p>=================================================================== EASY and FREE access to your email anywhere:

Hello, I would like to "piggy-back" other data in an Ogg/Vorbis I physical stream (i.e. file) in a manner that does not conflict with specifications and existing decoders/players/editors etc. As far as I can see, I have some possible choices: 1 - Chaining a logical bistream at the end. If this is the way to go, two questions arise to begin with: q1a - How to identify this stream in a

Hello again! As promised, here's a completed package of OggSplit. It's configured with autoconf and automake (use autogen.sh) and there are debian build rules. In it's current state it's quite useable, although there are certain internal things which could be improved (nothing critical however). There are of course bugs, so I encourage everyone to try breaking the tool with

Salve, Imagine ogg vorbis is used to produce radio with free software. A journalist would produce a report end send it with 24kBit/s out from a cricis place somewhere in the world. DRM is going to use MP4 - so his report has to be reconverted with loosing quality :-( Can you imagine to have an free codec someday that would work in embedded radio-reciver like MP4? If yes, should DRM not be open

Hi, as Conrad suggested, I've made a complete list of all points in the specification, which I beleive are errors, or where the explanation is unclear, contains unneccessary steps and so on. I hope someone has time to look through the points and if and when accepting or rejecting them be so very kind and inform me about it. I will also once again try to work through the residue

Hi! I created a Delphi class that allows reading of information about an OggVorbis file and modification of the comment header. It works like this: When the file is read, the class saves information about how many pages the comment header uses, and where in the last page the setup header starts. When the file is written, the ID header is copied. The comment and the remainder of the setup header

Hi! What happened to this document? Was it just left dying in the IETF system? Tor --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the

Hi, I've found some more errors in the file format specification (or at least points, where the specification and actual libvorbis implementation mismatch): - Floor 1 / curve computation / step 1: amplitude value synthesis 21) vector [floor1_final_Y] element [i] = [predicted] - (([val] - 1) divided by 2 using integer division) hould be: 21) vector [floor1_final_Y] element [i] =

Mandag, 2 juni 2003, skrev du: >On Mon, 02 Jun 2003 21:22, Vitaly Nechyos wrote: >This is what people usually want when they say 'normalization'. AFAIK, you >can't easily tinker with the vorbis frames to add a scale factor in the same >way you can with MP3, but I could be wrong. I could be wrong too, but if I haven't overseen anything, it should be possible to

Torsdag, 23 januar 2003, skrev Miroslav Lichvar <lichvarm@phoenix. inf.upol.cz>: >If input is 16 bit, side channel will be 17 bit (16bit - 16bit is >17bit number). And warmup samples will be (17 - wasted_bits) bit. Voila, this was the source of all my frustration, sync problems and who knows what. My decoder now works correctly for files encoded with the default settings. Are

Hi Folks, FWIW I figured out the /etc/magic file entries for both native and Ogg wrappered Speex, Vorbis and FLAC (attached). YMMV because the fields aren't necessarily in fixed positions in the files, but it works fine for me. Feel free to include it in the Xiph archives or forward it to the /etc/magic file maintainer once you're satisfied with it. John -------------- next part

Fredag, 31 januar 2003, skrev du: <p>>Next thing is, that I would like to clarify the difference between a codec's >latency (which I would die to know in exact figures for the vorbis codec one >day - as well as block sizes, but that's another story) and the (bandwidth) >"smoothing window" latency - call it buffering or whatever. One thing is the codec

The IETF passed the application/ogg MIME type some days ago. I couldn't bring you the news earlier because of the MS SQL worm that has been wreaking havoc all over my local networks. The IETF wants some clarifications in Silivias draft for the Ogg stream format, but apart from that I think it will also be passed soon. The RFC and IANA registration of this mimetype will probably be published

Hi, There is something I don't understand about the page_segment and segment_table values in the documentation. As I understand it, the segment table consist of as many bytes as specified in page_segment, PLUS one trailing byte with a value between 0 and 254. I've looked at some files that has a Comment tag so large, that it is spread over two pages. Here, the first Page Header (not the

Hi all, Below is the Vorbis RTP Internet Draft as sent to the AVT working group of the IETF. Comments and feedback is still welcomed from the Vorbis community. Cheers Phil ---------------------------8<-----------------8<------------------------ Network Working Group Phil Kerr Internet-Draft The Ogg Vorbis January 07, 2003 Community / OpenDrama

Torsdag, 23 januar 2003, skrev Tor-Einar Jarnbjo <Tor-Einar_Jarnbjo@grosch- link.de>: >According to the format description, the coding method has to be 0. > >I've been using libFLAC 1.0.4 to encode the stream. I've checked my interpretation against "flac -a" and it seems to read 17 bits for each warmup sample. Here is its output: frame=168 blocksize=4608

In my efforts to convince people to hear how good Vorbis is when compared to MP3, I'm gonna be encoding tracks from my CD collection to both formats, then writing them to audio CD, so people don't have to install extra software to hear the difference. Has anyone got some suggested specs for the options for MP3 encoding when using CDex or Chun-Yu's MP3 writer for winamp (preferably in