similar to: enidanism in the OggSquish logical bitstream framing format...

as per yesterday's discussion at #theora -- It has been suggested that we devise a method such that we will be able to add certain features to the bitstream (interlace, exotic color subsampling, clip length flag for download, etc), in such a way as to not obsolete streams encoded previously. Rillian's suggestion, which is pretty much standard practice, is to add a bitstream revision

Hi, I'm looking for more documentation on the Vorbis bitstream format. The goal for me is to write an optimized decoder using only integer or fixed point math for use on the Phatnoise Car Audio System (see http://www.phatnoise.com). I've already found the info on the Ogg framing system and I've already written my own thing for parsing through Ogg frames (easy). Also, is RTP

Dear experts, I am trying to understand the structure of the Speex .spx file, so I can packetize each frame in one packet for example, and in the receiving end, I can decode a file that has all the received frames (some of them may lost). I tried to figure out what is the delimiter used to separate the frames but I could not so far. I also tried to deleted some data from the .spx file or change

Hi! OGG specification said that: - It is possible for a stream to consist of a single page. - Page can consist of multiple packets. Could anyone tell me: - Will logical bitstream of _one page_ (b-o-s and e-o-s at the same time) with a _few packets_ be correct according to the ogg spec? - And, if such logical (multipacket singlepaged) bitstream is correct, how can I generate it by using

Hi everybody! I encountered a strange problem with ices-2.0.0. I use a icecast2/ices2 combo ti stream live audio and I use ices to record my stream. This worked well until last week. Since then the recording function produces somehow corrupt ogg-files. I cannot decode them to wav with oggdec, the program tells me "Only one logical bitstream currently supported". ogginfo prints out

This is the first draft of the audio/vorbis media registration form to be handled to the IANA. PLEASE comment extensively, even minor spelling mistakes etc are to be stamped out of this I hope. A media type for application/ogg (or should it be application/oggsquish?) will be created separately. I would be very happy if someone could supply the 4-letter filetype code used by MacIntosh .ogg files.

And this is what the application/ogg MIME descriptor is supposed to look like. Same request for comments here... Linus Walleij --------- MIME media type name: application MIME subtype name: ogg Required parameters: none Optional parameters: none Encoding Considerations: The OggSQUISH data is binary data, and must be encoded for non-binary transport; the Base64

On Sat, 2004-03-27 at 22:45, Andreas Grommek wrote: > I encountered a strange problem with ices-2.0.0. > I use a icecast2/ices2 combo ti stream live audio and I use ices to > record my stream. This worked well until last week. Since then the > recording function produces somehow corrupt ogg-files. > > I cannot decode them to wav with oggdec, the program tells me "Only

This release bundles up the last twelve years worth of build system improvements, including making the configure script more efficient. Alan Coopersmith (9): configure: Drop AM_MAINTAINER_MODE autogen.sh: Honor NOCONFIGURE=1 Update README for gitlab migration Update configure.ac bug URL for gitlab migration gitlab CI: add a basic build test Build xz tarballs

This release bundles up the last twelve years worth of build system improvements, including making the configure script more efficient and using the -n flag to gzip to improve build reproducibility. Alan Coopersmith (10): configure: Drop AM_MAINTAINER_MODE autogen.sh: Honor NOCONFIGURE=1 Update README for gitlab migration Update configure.ac bug URL for gitlab migration

Hello, I´m just curious: How far is Theora from a bitstream freeze? From TheoraTodo: "Derf has come up with a number of suggestions for improving the flexibility of the bitstream based on his experimental encoder work. These will be implemented, if not entirely supported by the reference decoder, before alpha 3 is released." Are those changes supposed to be the last adjustments?

Hi, Is it expected that an Ogg logical bitstream might logically serve as the physical bitstream from which other logical bitstreams might be demuxed? I am not sure that I really see the point of doing this, but it would certainly be possible within the current spec. The trouble is that there are any number of ways to do the low-level muxing of several streams into one logical stream, with

Hello, could somenone please describe me the vorbis specific physical bitstream structure, as I haven't found any documentation about it. Thank you ******************* Pierre-Henri Quelen phq@laposte.net "Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,13 €/mn) ; tél : 08 92 68 13 50 (0,34€/mn)" --- >8 ---- List archives:

I'm having trouble getting libvorbis to cut the beginning of a bitstream when I instruct it to do so with granulepos. I have constructed a file which I believe should have its beginning truncated. I have attached it to this mail. Here is a picture of what the bitstream looks like, as output by a python program that uses pyogg/pyvorbis to read the stream and print a representation:

Narrowband (8 kHz), wideband (16 kHz), and ultra-wideband (32 kHz) compression in the same bitstream What is the meaning of this? can i find more information about this somewhere? And what is packel loss concealment, an you enable this somewhere? thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL:

Jonny Daenen a ?crit : > Narrowband (8 kHz), wideband (16 kHz), and ultra-wideband (32 kHz) > compression in the same bitstream > > What is the meaning of this? can i find more information about this > somewhere? > > And what is packel loss concealment, an you enable this somewhere? What are you expecting exactly here? That I explain what's a Hertz and what's a

question for the crowd: In writing the bitstream spec, I need to decide how to name various fields. I can go with names equivalent or very similar to the existing C code, or I can go with a similar set of labels that are more intuitive. Many of the C variables are named in cryptic or confusing ways. Presently, I'm changing the names to be more descriptive whenever it seems to make sense,

Hi folks! Having trouble with re-encoding to 160Kbps. I have: Linux-Mandrake 8.2 Icecast 1.3.12 IceS 0.2.2 source Lame 3.92 Hardware is: Celeron 533 w/256MB RAM, 40GB Disk All seems to work at first but after a few songs it craps out and give me an ERROR WITH BITSTREAM (or something real close...sorry). ALL of my MP3s are encoded using the --r3mix flag (VBR) with LAME 3.91 or 3.89. All

Hi, I checked out the Theora source code for the first time as I figured that's the only way the Theora quirks will get documented (and subsequently re-implemented in libavcodec). I see that most of the code cribs the original VP3 source code, including the misspelled comments. Moving right along, I can't reconcile the way bits are packed in the stream. In VP3, the first byte of an

Hello all, I've been working a little inside the Theora decoder when I found that it seems that many videos had the very same huffman tables encoded into their bitstreams (at least the ones that I could take my time to dissecate). I found that the tables are listed as TH_VP31_HUFF_CODES in the file huffenc.c. I tried to investigate a little bit more to see who was setting the bitstream