Hello Jerome,
I'm not sure what version of MELP was used on the Codec 2 demo page, the
samples were encoded by someone else and sent for me.
Nice to know there is a non-radio application for Codec 2 - but I guess
an application will need to wait until some one steps up to write it.
- David
Hello codec2 listpeople, I originally wrote the author who suggested I
repost my question/comments to the mailing list even though i'm not 100%
sure why, but that's the main reason i'm here. :)
I mostly wrote curious whether anyone was working on a realtime player
for codec2 files, in particular for android, even though things are
pretty early in the process.
I realize most might think there's important things to focus on with the
basic core functionality first, but I wanted to offer a small sales
pitch in favor of why I think it might be worth whipping up something
quick even if it's glitchy or not stable or ready for prime time. (as
long as the program can re-load to where it might be in a long hourlong
file or playlist it's okay) Namely that certain audiobook/ podcasting
nuts like me almost make a game out of compressing things down as far as
possible sometimes or putting too much of the library on a portable
device just to have it. I know i'm not the only one whose made posts on
this subject, i've seen people post on hydrogenaudio forums wanting to
use MELPe and such for this very purpose.
As to why that might benefit the codec, if people are listening to the
codec regularily, especially at lower more challenging bitrates, they
will start spotting the 'harder to encode' places where voices get
distorted or become unintelligible and hopefully start providing
original source/encoded timecodes with commentary. For instance myself
i'm trying to learn chinese language. Certain errors not in english may
be more noticible or problematic at times even if english works well...
or certain kinds of background noise may be pernicious or difficult to
filter like whats on radio podcasts at times whether it's background
music or an on-site interview at a noisy location or whatever. This
could be valuable data mining, just suggest everyone listen at 1200bps
or less, and send in samples when you can't make out what's going on for
better analysis of original and encoded material.
PS one question I had that i'm wondering if anyone knows if the codec2
samples were compared against MELPe or MELPe++ - the samples at
compandent http://www.compandent.com/products_melpe.htm
<https://deref-mail.com/mail/client/dereferrer/?redirectUrl=http%3A%2F%2Fwww.compandent.com%2Fproducts_melpe.htm>
seem to imply it's some upgraded version of the codec "even better" than
what was originally NATO standard, I am not sure whether this was the
originally tested 2400bps MELP codec, the authorized 1200bps MELPe
upgrade, or if compandent has taken MELPe beyond (which is implied as
they call it MELPe++). Since MELPe++ seems to be the state of the art
codec that perhaps is what should be compared against whenever possible.
I wish I could help more in other ways (money/coding) but i'm a student
with neither right now. My only contribution for awhile might be
listening to material I encoded myself on my cheap single core phone and
saying "this file times 6:01 to 6:08 and 7:03 to 7:22 are examples of
your codec really struggling" for analysis, hoping it eventually learns
to even better tuning...
Hope this is useful to someone...
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Freetel-codec2 mailing list
https://lists.sourceforge.net/lists/listinfo/freetel-codec2