On 11/05/2014 07:30 PM, Josh Hoff wrote: > Does anyone want to pair this weekend on squashing > https://bugzilla.mozilla.org/show_bug.cgi?id=1039639? I'm hoping to > start dogfooding my flame soon (there are a couple other issues I'd like > fixed/to fix beforehand, but this is the main one). Thanks,
Not to be a killjoy, but I rather doubt we'd accept a patch to enable FLAC in the music app at this point in time. I feel rather strongly that any FLAC support belongs in Gecko, not Gaia, and there has historically been quite a bit of resistance to implement additional media formats in Gecko. You're welcome to ask Gecko people about that, though. Just to be clear, I really don't think we can accept a Javascript-based FLAC decoder, since the existing one I found wasn't license-compatible (and was written in CoffeeScript anyway). I'm also not particularly enthusiastic about maintaining our own version of a FLAC decoder in Gaia, since we're not a very large team. Also, while our devices are certainly fast enough to decode FLAC in JS (even a first-gen iPod could do it, and that was just a pair of 90MHz ARM CPUs), I expect it would have serious consequences for battery life. This would only be made worse by the fact that using Web Audio - at all - is currently a great way to kill your battery[1]. While we can't really make battery life *great* unless we get hardware decoding of FLAC, implementing it in C++ would help a lot. I guess my advice, if you really want to do this, is 1) convince Gecko folks to add FLAC support to <audio> elements, and then 2) write a small patch to use our existing Vorbis comment parser for FLAC files. (Of course, this is all beside the point, since I have serious doubts that the DACs on the Flame are good enough that you'd even notice an improvement from FLAC files.) - Jim [1] Apparently this is being worked on. _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
