Recherche avancée

Sur d’autres sites (10231)

• Changes to the WebM Open Source License

  5 juin 2010, par noreply@blogger.com (John Luther)

  You’ll see on the WebM license page and in our source code repositories that we’ve made a small change to our open source license. There were a couple of issues that popped up after we released WebM at Google I/O a couple weeks ago, specifically around how the patent clause was written.

  As it was originally written, if a patent action was brought against Google, the patent license terminated. This provision itself is not unusual in an OSS license, and similar provisions exist in the 2nd Apache License and in version 3 of the GPL. The twist was that ours terminated "any" rights and not just rights to the patents, which made our license GPLv3 and GPLv2 incompatible. Also, in doing this, we effectively created a potentially new open source copyright license, something we are loath to do.

  Using patent language borrowed from both the Apache and GPLv3 patent clauses, in this new iteration of the patent clause we’ve decoupled patents from copyright, thus preserving the pure BSD nature of the copyright license. This means we are no longer creating a new open source copyright license, and the patent grant can exist on its own. Additionally, we have updated the patent grant language to make it clearer that the grant includes the right to modify the code and give it to others. (We’ve updated the licensing FAQ to reflect these changes as well.)

  We’ve also added a definition for the "this implementation" language, to make that more clear.

  Thanks for your patience as we worked through this, and we hope you like, enjoy and (most importantly) use WebM and join with us in creating more freedom online. We had a lot of help on these changes, so thanks to our friends in open source and free software who traded many emails, often at odd hours, with us.

  Chris DiBona is the Open Source Programs Manager at Google.

  

• Changes to the WebM Open Source License

  4 juin 2010, par noreply@blogger.com (John Luther)

  You’ll see on the WebM license page and in our source code repositories that we’ve made a small change to our open source license. There were a couple of issues that popped up after we released WebM at Google I/O a couple weeks ago, specifically around how the patent clause was written.

  As it was originally written, if a patent action was brought against Google, the patent license terminated. This provision itself is not unusual in an OSS license, and similar provisions exist in the 2nd Apache License and in version 3 of the GPL. The twist was that ours terminated "any" rights and not just rights to the patents, which made our license GPLv3 and GPLv2 incompatible. Also, in doing this, we effectively created a potentially new open source copyright license, something we are loath to do.

  Using patent language borrowed from both the Apache and GPLv3 patent clauses, in this new iteration of the patent clause we’ve decoupled patents from copyright, thus preserving the pure BSD nature of the copyright license. This means we are no longer creating a new open source copyright license, and the patent grant can exist on its own. Additionally, we have updated the patent grant language to make it clearer that the grant includes the right to modify the code and give it to others. (We’ve updated the licensing FAQ to reflect these changes as well.)

  We’ve also added a definition for the "this implementation" language, to make that more clear.

  Thanks for your patience as we worked through this, and we hope you like, enjoy and (most importantly) use WebM and join with us in creating more freedom online. We had a lot of help on these changes, so thanks to our friends in open source and free software who traded many emails, often at odd hours, with us.

  Chris DiBona is the Open Source Programs Manager at Google.

  

• ffmpeg : minimum components for muxing m4a and raw video ?

  31 août 2014, par Guy

  I am trying to build a version of ffmpeg (for android) using the bare minimum number of components (encoders, decoders, parsers etc...), in order to minimize my binary space (don’t want to bloat the resulting APK).

  The task at hand is to mux an m4a audio with a raw video file into an mp4 file. (x264)

  When I compile ffmpeg with all components, it works fine, but I could not figure out which components to include to be able to read in m4a files.

  Here is the list of flag we currently use to successfully mux mp3 audio with raw video to create mp4 files.

  Which flags should be added to be able to mux-in m4a files ?

  --disable-everything \
  
  --enable-muxer=mp4 --enable-encoder=libx264 --enable-libx264 \
  
  --enable-encoder=h264 --enable-decoder=h264 --enable-demuxer=h264 --enable-muxer=h264 --enable-parser=h264 \
  
  --enable-decoder=rawvideo \
  
  --enable-protocol=file \
  
  --enable-hwaccels \
  
  --enable-decoder=mp3 --enable-demuxer=mp3 \
  
  --enable-demuxer=wav --enable-decoder=pcm_s16le --enable-decoder=pcm_s16be --enable-decoder=pcm_s16le_planar \
  
  --enable-encoder=aac --enable-parser=aac \
  
  --enable-decoder=mpeg4 --enable-encoder=mpeg4 --enable-parser=mpeg4video --enable-demuxer=m4v"