Short of a full specification, you could publish a paper on observations of
David's codec, going from the source code, his blog posts, and his Ph.D.
thesis. Any number of technical publications would take that, and it's a
sure thing that the TAPR/ARRL DCC journal would take that paper if some
other journal doesn't. Since the codec itself is a moving target, explain
the concepts and algorithms first. That would equip more people to read
and/or write a spec and keep it up to date.
Bruce
On Mon, Mar 20, 2017, 07:59 Sebastien F4GRX <[email protected]> wrote:
> Hello all,
>
> I am happy that my question triggered interest from such an interesting
> group of
> people.
>
> The BSD was just a thought experiment, please do not worry. I am very well
> aware
> of the importance of keeping this code open and ensure it *stays* open.
>
> My real goal is to understand this codec as best as possible, so a
> specification
> would have helped.
>
> Code, well, is only one possible implementation and has some added
> complexities.
>
> After all, the important thing about codec2 is that we are able to
> understand it
> from A to Z...
>
> I think that writing a specification myself is the best possible action to
> achieve this goal.
>
> Several code bases are available: the reference C code, the java test code
> previously published by Steve, and the Octave scripts.
>
> I am not interested in a rewrite for the sake of changing the licence. This
> makes no sense! I am interested in the embedded side of things, so a fixed
> point
> version is exactly what I think is interesting. This fits in my wider
> personal
> plans. And if I ever write something like this, it will be GPL licenced.
>
> Thank you to everyone.
>
> 73's de F4GRX Sebastien
>
> Le 20/03/2017 à 15:25, Bruce Perens a écrit :
> >
> > The codec is LGPL, not GPL. You have a right to read it and do not have
> to
> > reverse-engineer it, but do not cut and paste the code or its
> _structure_ if
> > you want to avoid David's copyright. If you want to do something useful
> rather
> > than just a BSD version of LGPL code, make it fixed-point instead of
> float.
> >
> > Bruce
> >
> >
> > On Mon, Mar 20, 2017, 06:00 Ricardo Andere de Mello <
> [email protected]
> > <mailto:[email protected]>> wrote:
> >
> > hum...
> >
> > I understand the value of the source code, but for me at least, that
> would
> > like to mantain a java and a as3 version of the codec, the lack of
> > specification was also the reason to not trying to do it at all.
> > I saw maybe two attempts of java versions, but I did not bother to
> look at
> > them because:
> > 1 - There was no way to see if it was correct without I reading the
> > original C source code
> > 2 - They would be deprecated in minutes, because the code is always
> > evolving and there is not a "version" number with specifics
> implementation
> > details.
> > See, if it is trouble for you, that own the code, and made it, to
> mantain
> > the specification of a "moving target", imagine for five or six
> > implementers, that are more interested in using your code, than
> > understanding it.
> > Without a specification we cant even say, at all, if it is hard or
> easy to
> > implement it in any other language.
> >
> > I know it is fun to keep the development forever, but codec2 maybe
> coulda
> > be codec2.1, codec2.2, codec2.3, etc...:)
> >
> > []s, Ricardo Mello
> >
> > On Fri, Mar 17, 2017 at 4:51 PM, David Rowe <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> > > Is there somewhere a detailed specification of codec2 that
> would allow
> > > implementation from scratch without looking at the current
> code?
> >
> > No.
> >
> > Thinking about it, my preference is to express the Codec in
> source code.
> > I've implemented speech codecs in the past from written
> specifications
> > and it's a messy business. Plus a maintenance nightmare to keep
> the
> > specification and code aligned.
> >
> > - David
> >
> >
> > -----------------------------------------------------------
> -------------------
> > 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
> > [email protected]
> > <mailto:[email protected]>
> > 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
> > [email protected]
> > <mailto:[email protected]>
> > 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
> > [email protected]
> > 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
> [email protected]
> 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/freetel-codec2
