Responding to messages of last few though without quotes.  To Jean-Marc Valin
 
Saying that speex and opus is 'enough' is more for differeing uses.  There are people currently putting 1 terabyte hard drives into ipod Classics and people are working on hacks to possibly enable 2-4 terabytes.  It's not how much music you plan to listen to at one time that is the point but rather how much of your library you can take with you.  I for instance listen to alot of podcasted radio shows when I drive (and I travel extensively) when i'm not listening to audiobooks, of which I probably have a few hundred gigabytes even in low bitrate that I all hand-encoded from I don't even remember how many thousands of cassettes I got from the library in and after college since before mp3 even existed as a format.  I killed a bunch of tape decks wearing them out doing so.  But on top of that, my archives of one radio show alone is over 100gigs as its 3-4 hours a day and has gone on for years.
 
The purpose is not to listen to it all back to back the way one maybe listens to entertainment.  It's when you hear or read something like "Back in 2008 we interviewed so and so" and you want to go back and listen to that interview - you have it already on you.  Or i'm taking a coast to coast trip with a friend and I discover they've never listened to Alan Watt before - I didn't plan to relisten to it but since I can have it all with easily it's easy - especially the way that cell data dies outside most big cities and you cant stream alot of stuff even if you have those various audio services.  Long roadtrips through empty places = just playing what you already have with.  Plus i'd like to see how much of my library I can give to people on old supercheap players which might only have 8-32gigs possible.  Supporting 5x the content at 1.2kbps when I can never fit it all anyways and cant afford to give away a nicer player is 5x as useful.
 
 
As far as differing versions of playback and such, I think people would understand - you have to be kind of hardcore in the first place to worry about 6kbit vs 1.2kbit to begin with.  As long as there was some kind of a version header in the files and player (perhaps thats the first thing to standardize, a future ready header?) and instead of labeling it codec2, just labeling major versions codec2-alpha (.c2a), codec2-beta (.c2b later) if there's no alternative.  Just like it's ability to play things as obscure as Nintendo 8bit sound chip rips, Commodore 64 SID music, and similar which tend to be a bit glitchy or less than perfect i've heard, you take what you can get.  (you could say why not store them as mp3's either, do we really need a 64kb sound file for an hour of video game music from the SNES)  If it's not a part of the main builds and is clearly labeled experimental/development I don't see why it should have a negative.
 
The positive is just the already stated "more ears listening to the codec under various conditions, asked to provide feedback/ examples/ timecodes of challenging material" in response.
 
Whether that positive is worth the amount of effort it takes to program a fixed point decoder though I have no idea.  :-/  I just wanted to suggest why I thought the idea wasn't bonkers.  Open source means not assuming what the consumer wants, just giving them a recipe they can change however they desire.  How much of a priority it should be vs other things I don't know either - an Android player would probably be much more usable (and doesn't have to be fixed point) and much more futureproof..  plus it enables things like giving away old smartphones/even Tracfones has older Android versions you can find for nothing and load with data as a gift - some with as little as 1gig or less of space.  Mp3's fill that up a bit too fast.  Speex honestly sounded worse to me than codec2.
 
 
 
 
 
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Freetel-codec2 mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freetel-codec2

Reply via email to