similar to: bitrate peeling

Hi So far when I have streamed Vorbis, the headers (the 3 first frames/packets) was not included in the stream, but communicated out of band typically in an SDP file as unparsed A-lines. Rethinking that concept, I'm wondering if it is really necessary to do it that way. Isn't it possible in a platform independent way to regenerate useable headers on the client side using just the

Hi I have created a small website trying to document my Ogg/Vorbis support for MPEG4IP. You can find it here. http://www.maersk-moller.net/mpeg4ip/index.html Kind regards Peter Maersk-Moller --- >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-request@xiph.org' containing

Hi I'm trying push for companies and government institutions to start using Vorbis as an alternative to MP3 and to some extend AAC so they as a benefit can ignore rigid license schemes and expensive royalty payments. In principle it ought to be a downhill job, but it has turned out to be a lot more difficult than expected. The biggest obstacle for government institutions and to some extend

No offense, Segher, but the output quality of this thing is awful. =) I'll disregard the fact that, at least with *my* compiler, the source tarball I downloaded reduces every packet to zero bytes, which isn't terribly interesting. I decided to set the byte reduction to something constant: I started by dividing each packet's size by 2 just to see what would happen. The resulting ogg

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,

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

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

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

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/

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

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

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

Hi all, I'm looking into congestion control for Vorbis RTP and I'm wondering if it's not too early to define a mechanism which would help bitrate peeling. The client can send a standard receiver report stating the interarrival jitter and packets loss. Once a certain jitter/loss point is reached the server peels off a pre-determined bitrate fraction from the stream, eg 128k would

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello vorbis, Is bitrate peeling implemented into RC3? (i'm guessing not due to the fact that none of the tools seem to have any information about that) Still, looking forward to checking out the quality improvments (once the Debian packages become available... (i've compiled it already on one of my potato boxes, but the newer

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

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

Yesterday I asked for help about read.table with a CSV file. I received the following help. As always many thanks for the prompt responses. Now I load my csv file in a text editor ( pfe) and delete all spaces. My original mail is at the end. From: Peter Dalgaard BSA <p.dalgaard at biostat.ku.dk> Do you have spaces before the commas in your file? > Yes, number , space,

Yesterday I asked for help about read.table with a CSV file. I received the following help. As always many thanks for the prompt responses. Now I load my csv file in a text editor ( pfe) and delete all spaces. My original mail is at the end. From: Peter Dalgaard BSA <p.dalgaard at biostat.ku.dk> Do you have spaces before the commas in your file? > Yes, number , space,

I just read some of the discussion on the list about 'bitrate peeling' and remembered an interview of Monty that I have read recently. In it he says that Vorbis uses MCDTs <sp> and that these are theoretically reversable. And now, I learn that theoretically we can use bitrate peeling to make smaller files from larger ones, and that leads to my question. Could I theoretically