[Vorbis-dev] ogg ACM codec

Didier Dambrin didid at skynet.be
Tue Jul 19 19:05:43 PDT 2005

> On Tue, Jul 19, 2005 at 04:49:17PM +0200, Didier Dambrin wrote:
>> All I know is that we're currently using that japanese codec made by
>> 'freddie fish'. The decoding works perfectly for us, it's the encoding 
>> that
>> sometimes crashes, and doesn't work in some editors.
> Well, we basically said "You can't actually make a fully working Ogg
> Vorbis ACM codec" and you said "But were're using one, it's great it
> just doesn't always work".  So we're in full agreement.
> (The Japanese one is a hack and isn't fully compliant.  So no, it
> won't always work).

i'm fine with a CBR one that wouldn't sometimes crash when encoding

I'm also fine with a codec working in 1-pass (as opposed to buffered) 
decoding, if that's where the problem is(?)

In fact, I'm fine with anything non-compliant as long as it can compress as 
well as ogg (& mp3 isn't an option). I'm only looking for a great 
compression scheme that doesn't fuck up audio data like mp3 does so much.

>> Problem is that I want to keep working with wav files: they're
>> standard, and we use a lot of the info they may contain. While I
>> know that you could store anything you want in an ogg file, it'd
>> still lack of support from audio editors. That's the problem with a
>> new format: it's new.
> Ogg isn't that new; what editor are you using that still doesn't
> support Ogg?  Most do these days.

but which editor will store these:

-cue points (+type +length +names +assigned keys)
-full wav-compliant info text
-tempo & beat info
-loop points & other sampler-specific info (root note, etc) (and yes, ogged 
stuff usually keeps looping well, although sometimes not, vs never with mp3)

in ogg files?

More information about the Vorbis-dev mailing list