similar to: Peeling vs Coupling

Given all this talk of peeling lately, I thought I'd try out a method I've been thinking about for a while now. It goes something like this: * Peeling is achieved by dropping some of the residue. * The encoder indicates how much of the residue to retain (e.g a number of stages, 3 bits in the stream per packet, non-standard!). * The decoder (peeler) copies the contents of packets except

>> 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

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:

> But such thinking is invalid for nonlinear mechanisms. > [...] I may fit it with a set of 5 Lorentzians > or, for more accuracy, with 10 Lorentzians. Doing so, the > resulting 10 Lorentzians _wont_ include the less accurate > 5 Lorentzians as a subset! Since 'bitrate peeling' is already supported, I believe it would be possible to transmit the 'peeled' stream and

Monty, You helped me out quite a bit the other day, but I just wanted to make sure I understand something. The "ideal" way to do bit rate peeling is to have the encoder set the file up to be conducive to the peeling process, and the streamer would be the device that actually does the peeling. Am I correct in assuming, then, that the decoder would think that the file it is

Hi All, Let me ask this question of the group: When bit rate peeling becomes available, how will the quality of the peeled Vorbis file compare to a file encoded at the target quality directly from the original? So, for: a.wav --> b.ogg (at q6) --> c.ogg (at q2) a.wav --------------------> d.ogg (at q2) how are c.ogg and d.ogg likely to compare in terms of audio

The VQ codebook generation utilities are more or less ready to go. Minor things are left to do, but those will have to be handled as I to them :-) The next thing to do is complete the interface to get compression modes and codebooks to the library for encoding (minor stuff), and then arrange how exactly the MDCT residue is filtered through the codebooks. VQ codebook util instructions:

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

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

> 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 >

I have run an ogg analisis using EAQUAL from -q 0 till -q 10 evaluating bitrate and quality. The results are shown in a nice graph, and can be seen here: http://audio.sinderman.com/ One thing I have found is a bug, as it is cleary shown by the blue lines. Other discoveries are written in that page, and others are still evolving in my mind :) The goals of this analisis is to help the developers

Hi all, I recently started to study the Ogg Vorbis codec and found an interesting feature called bitrate peeling [1]. Do you know where I can find more information on this topic? E.g., how is the actual peeling being implemented, what are the performance results in terms of resulting quality, what are the requirements for bitrate peeling (can it be applied to any ogg vorbis stream), ...? Also,

During the interesting interview that binaryfreedom has made with Monty and Jack, Monty mentions cascading, a feature that will be added, quote: "Cascading is the ability to make multiple passes through the frequency spectrum, iteratively filling in more detail, like a progressive jpeg". What are the advantages of something like this - does this generally improves quality or is it used

Hey, Maybe you guys remember us, I'm from the Neuros forums. I've got to say, having a player that supports Ogg Vorbis has really turned things around for everybody. We're still struggling with higher bitrate Vorbis streams, but that is only because of our terribly underpowered DSP. Anyway, to the point of my email. Recently the discussion of bitrate peeling has been floating

After reading the recent thread [http://www.xiph.org/archives/vorbis/200211/0057.html] on the vorbis list about bitrate peeling, I was wondering if it would be possible for xiph.org to post a specification, outline, flowchart, or a drawing on a napkin of what the basic operations of bit peeling would entail. If there was some sort of starting point, then it may be a little more inviting for

Hi all, First up, this is not a proposal on how to do it, but rather on how to get it done. In the latest thread it was mentioned that it was most likely that either Monty or Segher would be the most likely people to implement this code. It was also stated that this is not their priority at the moment. I can only see two solutions to this problem: 1. Find someone else with the knowledge and

rc3 is out and now that the dust has settled I'd like to know, whats coming around the corner for rc4? what new tricks or quality improvements are planned? I think I saw somewhere that bit-rate peeling (or was it cascading codebooks) was one of them, also btw I've heard that wavelets was one of the next big things (i think it was usefull because of pre-echo correction) but that it would

Hi everybody: Here is this week's Ogg Traffic with all new updates on recent activities in the world of Xiph.org. The HTML version is up at http://www.vorbis.com/ot/20030415.html. Enjoy! -Carsten <p>Ogg Traffic for Tuesday, April 15, 2003 [1]Carsten "Purple" Haese April 15, 2003 _________________________________________________________________ Table of

Hello all, Just a quick note to let you all know that I have placed a bounty on Lauchpad to get bitrate peeling added to Vorbis. It is a feature that I think we would all like to have, and would probably pay something to get, but it hasn't been done. My request to you is to add to the bounty. I have seeded it with US$20, which is not enough to motivate a developer to get it done, but I am a

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello vorbis, Wasn't really answered in my first post about this subject (although people did convince me to do a debian/rules binary, which i've done and am VERY impressed with RC3 (played a -q3 file to a mp3 dude secretly, and he says "whoa! 112kbits! give me your new mp3 encoder" (winamp3 doesn't show the changing