3 ms·
Comparing it to uncompressed audio is a bit of a red herring. MP3s can easily do 32kbps - they sound like crap from a musical standpoint, but they do it just f
by Groxx 16y ago
Comparing it to uncompressed audio is a bit of a red herring. MP3s can easily do 32kbps - they sound like crap from a musical standpoint, but they do it just fine. Heck, mp3s at 8kbps still sound significantly better than my cell phone - you could run 7 audio streams at the same time on dial-up with that quality. Similarly, uncompressed video is huge, when a high-quality h.264 pass will look almost identical with massive size savings. From the several charts, it looks like CELT could be a very large improvement over the encoders they compared against (I'm assuming a relevant sampling), especially where speed is concerned, and I'll definitely poke at it and see what I think.
I very much liked the spectrograms, that looks to be a massive improvement. I've got to test it on my good pair of headphones to see just what it sounds like.
Nearly everything stimulates my intellectual curiosity; this is high-ish on my list, but that might mean years yet. Many thanks for the suggestions on info though, I'll most certainly keep that handy!
- nullc 16y agoExactly. CELT at 2.5kbit/sec: http://myrandomnode.dyndns.org:8080/~gmaxwell/celt/16k_60ms_20-2.wav http://myrandomnode.dyndns.org:8080/~gmaxwell/celt/16k_60ms_... So sure, CELT can be coerced to run at obnoxiously low rates— it's far more flexible than MP3 in this regard, every frame size which is an integer number of bytes greater than 8 or so should more or less work (and it should use every bit effectively). This doesn't mean that it'll actually be useful at very low rates. 32kbps is about the limit for 20ms frames where things really start to come apart and everything starts sounding pretty poor. The CELT _decoder_ is more computationally complex than you might guess. We started the design in 2007, and the decoder is pretty comparable to MP3 or Vorbis decoding (though requiring a _lot_ less memory). Using substantially less CPU than that, if there was quality to be gained would have been a sin. So although the overall design is nice and simple— we use a number of 'more optimal' techniques which are decent CPU sinks. E.g. Everything is range coded (so we're not constrained to coding things with probabilities of the 1/2^n form) and we use high dimensionality vector quantization. The encoder, however, doesn't need a psy-model at all nor does the current one have much of a psy-model (it has some simple hacks for a couple psycho-acoustic tweaks, but nothing too complex) Reasonable perceptual performance is implicit in the format. This means that a good CELT encoder can be much faster than, say, a good vorbis encoder. On the subject of DSP stimulating curiosity, checkout http://www.xiph.org/video/ http://www.xiph.org/video/
- anigbrowl 16y agoI kinda like the artifacts on that :-) You weren't kidding about the impact on pitch tracking; and yet it's remarkable how subtle nuances of timbre and intonation remain, particularly on the woman's voice. I'm still wrapping my head around the n-dimensional vector quantization - it seems to me like some of the techniques you have refined for this codec would have more general application for things like time stretching and noise fingerprinting. Thanks for sharing your insights with us, as well as all the fine work you guys have been doing for many years. You're very generous. PS: I can't recommend that video highly enough - there are things in there that took me years to pick up the hard way, and the presentation is great too. Looking forward to more!
- Groxx 16y agoNabbing the video right now, thanks for the link! I doubt I would've run across that one any time soon.
- charlesdm 16y agoWhere/when can I get a library for this?
- anigbrowl 16y agohttp://www.celt-codec.org/downloads/ http://www.celt-codec.org/downloads/