> Or Matroska (.mka): ... >> See https://www.xiph.org/ogg/doc/rfc3533.txt . Make it work with the >> Ogg Encapsulation Format.
Either way, it still needs a file suffix. The idea that "ogg" would work for arbitrary audio/video data has been a disaster. Apps claim the file extension, but can't decode all possible ways of encoding the data. You may have 5 apps that handle a format, covering all possible encodings in total, but no app handles everything. This is why TIFF never caught on, but JFIF and PNG and GIF were fine. You can toss JPEG2000 or JBIG2 or Wang vector markup in a TIFF, and even 2 different JPEG storage styles. Good luck with reliable reading. For the most part, users gave up. They reject it. Web browsers don't try. In actual usage, the "ogg" suffix is Vorbis audio. That is all. You can't even safely use the container format unless you can mark the header at a fixed offset with a clear indicator that will ensure that file magic never just claims "ogg", because that would imply Vorbis. You'll get files saved as "ogg" and served up with a MIME type that doesn't make it clear that codec2 is in use. Files won't play right. This should work properly: Matroska: filename.mk2 (Mac type MAT2) Ogg: filename.og2 (Mac type OGG2) Headerless: filename.codec2 (Mac type DEC2) MIME type: prefix the file extension with "audio/", w/o "x-" That said, Matroska and Ogg are only suitable if file magic is trivial. There must not be any chance of misdirecting the data to a Vorbis-only player or similar. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Freetel-codec2 mailing list Freetel-codec2@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freetel-codec2
