I was going back over this thread and realizing that, despite resembling
a Not Invented Here solution, a full on container format might be
overkill. Seeking, as Tomas suggested, would be nice, but for the most
part we're just trying to play short streams.
So, to the original poster's request, I humbly suggest ".c2" as the
extension. I don't think there are any issues with a two character
extension as opposed to a three or four.
That said, the notion of managing the different bitrates does present a
challenge. I therefore suggest any such encoded file have some "magic"
bytes at the beginning, even if this is something as simple as 0x43 0x32
("C2"). I then propose the next byte be the mode ID as defined in
codec2.h. This would allow c2enc/c2dec to be retrofitted or separate
tools to be constructed to Do The Right Thing™ based on these.
If we can agree on these bytes, I'm happy to take a stab at coding this
up. It doesn't look like it should be too difficult (famous last words!)
73 de Kevin N8VNR
On 05/22/2017 04:35 PM, Kevin Otte wrote:
> Or Matroska (.mka):
> https://matroska.org/technical/specs/index.html
>
> On 05/22/2017 02:28 PM, Bruce Perens wrote:
>> See https://www.xiph.org/ogg/doc/rfc3533.txt . Make it work with the
>> Ogg Encapsulation Format.
>
>
> ------------------------------------------------------------------------------
> 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
>
------------------------------------------------------------------------------
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
