similar to: Bit peeling(?) used in MPEG-2/SVCD Nero plugin?

Does the spec allow a stream consisting only of headers, with 0 audio packates? -- Beni Cherniavsky <cben@tx.technion.ac.il> (also scben@t2 in Technion) MSVC in default mode doesn't define __STDC__ (correctly!). No comments. <p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this

Beni Cherniavksy (cben@techunix.technion.ac.il) wrote : [ big snip ] > Here are the dates as far as I know: > > > 20000508 (beta1/2) > 20001031 (beta3) > 20010225 (beta4) > 20010615 (RC1) > 20010813 (RC2) > 20010816 (gtune 1) (RC2 - Garf tuned v1) > 20011014 (GTune 2) (RC2 - Garf tuned v2) > 20011217 (RC3 - oggenc, oggdrop) > 20011231 (RC3 -

Hi all, last time I have seen discussions here about alternative encoders, or tuned versions of the encoder. Last year (sept/oct) there had been the discussion if existing streams will be peelable or if they have to be "modified" first to be peelable. Now for my question: Is it known allready if existing streams will be peelable or not ? Or, with other words: Is it known if the /can/

Just invented the above (subject) phrase. Maybe somebody would like it as a slogan or something... Not patented AFAIK ;) -- Beni Cherniavsky <cben@tx.technion.ac.il> (also scben@t2 in Technion) --- >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

Monty, could you please modify the archiving mechanism so that the current month messages are archived from the begining into the month-number directory where they will be afterwards? The current scheme makes people link to this month's articles with a URL that breaks afterwards. At least please provide a symbolic link or something from the directory that will later become correct (e.g.

After reading http://mp3.radified.com/mp3.htm I sent Rad an explanation of some things as I understand them. He liked it and posted it on his site (still unlinked, use the URL below). Can somebody with better understanding of psycho-acoustic terms and the vorbis model check it and comment on it? In particular I didn't know how vorbis handles quantization noise. If you reply with

first, congrats to monty and the whole crew for getting this close to 1.0. it's a monumental achievement reflecting a huge amount of hard work -- kudos! econd, i know the bitrate peeling feature has been pushed back until after 1.0 is out. but i'm wondering -- will oggs created with a 1.0 encoder be peelable with an as-yet-unreleased utility, or do "peelable oggs" have to be

Sorry for posting somewhat off-topic... Most my music files have names in hebrew (FAT32 partition). I dual-boot between a hebrew win98 (where these files are opened nicely by winamp, freeamp and any other program) and a hebrew win2000, where windows media player is the only program I've seen so far to open them. All others say "can't open file ???? ?? ???.ogg" (or .mp3) - both

I was up late last night, and i had a thought on peeling that would probably provide 100% accurate peeling data to a decoder, but take a maximum of 1101 times normal time to encode (taking into account the range from q-1 to q10 ). ay you want to encode a track at q10, but you want it to be peelable. the 1101 encoder would encode from the source at every quantifiable level (since there are 2

Hi: A friend asked me a question that I was unable to answer, so I'm posting it here. Can files created by the beta4 encoder be peeled down when that becomes available, or is the ability to encode peelable files also not implemented? My friend wants to know if they should switch over now or hold off until this becomes possible. Geoff. --- >8 ---- List archives:

Just found this one: http://camelot.kingarthur.com/phoco/ogg_vorbis/info.html It seems to have music dedicated to vorbis (by the names, don't have player here) and a link to an interview with Monty ("more information on the Ogg Vorbis format") and the artists seem very excited about it. The browser says the pages are quite old (Jul./Sep. 2001) but I don't remember it being

In advanced tag editting mode, the list of tags doesn't display unicode content of tags properly. A side suggestion: forcing english keyboard in tag name edit field would be helpful (when I edit many tags all in my language, currently I have to witch to english and back all the time). -- Beni Cherniavsky <cben@tx.technion.ac.il> (also scben@t2 in Technion) Common

The FAQ says (at its very end): > Does Vorbis support mid/side stereo modes? More than stereo? > > Vorbis has hooks for mid/side stereo and continuous balance stereo, > but the channel mappings for both are yet to be formally specified and > implemented. Currently, Vorbis channels are uncoupled. > This should be updated so that people know how good is Vorbis :) > Vorbis does

The spec seems to be unclear on this: should two comment haeders who only differ in the order of comments be considered equevalent? VCE shows comments in the order read and allows to store them in any order (it has move up/down buttons). Comment editors with a fixed layout (like the commmon TITLE/ARTIST/etc. fields in PP's winamp plugin) don't show the order and give no control of it.

I've tried to understand the codebook matter (but haven't yet had time to read the source). I want to understand how ibg is the flexibility resulting from packing the codebook in the header of every bitstream. Can we, for example, change the volume of the whole sound by scaling the vectors in the codebook? (My guess is that this wouldn't be enough, as we have to scale the floor of

I happily downloaded the official beta4 winamp plugin as well as Mattew's versions with VCE interated and with/without the dialog. When I installed it winamp (v2.72) didn't recognize it (no vorbis plugin listed in the config, doesn't play ogg files) - same for all of them. I recompiled it myself from Mattew's source with vce - same results. It does recognize the old plugin when

>> Is bit-peeling going to be real (or just a rumor forever)? > Apparently the RC3 streams are capable of being bit peeled, however the > tool to do so was looking likely to be quite complex. I believe the plan > was to have RC4 produce streams that left better hints for the peeling > tool, so as to make the tool simpler and faster, but I doubt we'll see it > until

I downloaded `file' for djgpp, and it verbosly identified my mp3 by bitrate, sample rate, mono/stereo, option bits, etc. WAVs are also uidentified well. Only vorbis was identified simply as "Ogg-Vorbis compressed sound file" without any info. So I decided I must fix this to replace my aliases that use `od' to read the bitrate and number of channels. Here is the result

> From: Beni Cherniavsky [mailto:cben@users.sf.net] > Sent: 26 September 2003 10:35 > To: vorbis@xiph.org > Subject: Re: [vorbis] streaming > > - Vorbis is designed to allow "peeling": if you truncate packets, you > still get a legal Vorbis stream but with lower quality. This should > allow very effecient streaming of multiple bitrates from the same >

Hi. Here are my patches and makefiles for compiling ogg, vorbis and vorbis-tools on DOS with DJGPP. They can build them from cvs snapshots and need minimal maintainance (even extract source lists from `makefile.am's). Everything seems to work, except one FP exception on encode at middle bitrates (lowest two and highest bitrates don't cause it) - I don't think it's my