Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

nwjs + MP3 special build for Europe?

See original GitHub issue

Hello, I read about MP3 patent limits on new nwjs and as I read on wikipedia this codec is patent-free for Europe:

The basic MP3 decoding and encoding technology is patent-free in the European Union, all patents having expired there. https://en.wikipedia.org/wiki/MP3#Licensing.2C_ownership_and_legislation

Please, could you add to your builds another one special for Europe companies? (something like nwjs-eu) Thank you

<bountysource-plugin>

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>

Issue Analytics

State:
Created 8 years ago
Comments:15 (9 by maintainers)

Top GitHub Comments

4reactions

abhijeetkcommented, Feb 25, 2016

@rogerwang How about providing JS API to enable codec ?

Enable all codecs supported by ffmpeg(including proprietary codecs)
by default disable proprietary codecs in chromium layer.
Allow user to enable proprietary codec at chromium layer using JS API. (It is responsibility of developer to enable it)

JS -----> chromium(disabled) —> ffmpeg(enabled)

After enabling proprietary codec using JS API.(say, mp4)

windows.enableMimeType(‘video/mp4’) ----> chromium(enabled) —> ffmpeg(enabled)

Please let me know your opinion on this approach.

0reactions

rogerwangcommented, Nov 2, 2017

Mp3 decoder is in official NW binary since 0.22.1