Recherche avancée

Sur d’autres sites (5938)

• Anomalie #3271 : tailles_en_octets : tenir compte des norme SI

  22 septembre 2014, par Maïeul Rouquette

  norme SI, pas ISO... désolé

• FFMPEG filter using named pipe for I/O to a forked program and legal consideration [closed]

  17 septembre 2021, par alexbuisson

  I would like to develop a ffmpeg filter to have an easier and better integration of the ffmpeg functionalities in case of complex command lines.

  



  Imagine an ffmpeg command line in which you can configure a filter that will use to configure a 3rd party executable to fork and use named pipe to pass video through that external tools.

  



  Technically I can write it, but the question is, is it legal from FFMPEG license point of view (FFMPEG can be GPL or LGPL depending of how it has been built). As far as I understand, if I have an executable called "my_video_transformation.exe" (no relationship with ffmpeg, it just read input pipe and write to output pipe)

  



  It's ok for a user to run the following :

  



  


  (FFMPEG GPL or LGPL).exe decoding_args | my_video_transformation.exe | (FFMPEG GPL or LGPL).exe encoding_args

  


  



  But it's not ok if a user can run something similar to :

  



  


  (FFMPEG GPL or LGPL).exe filter="my_video_transformation.exe" transcoding_args

  


  



  from my understanding of https://www.gnu.org/licenses/gpl-faq.html#GPLPlugins

  



  As soon as you write in a GPL or LGPL executable something that can fork and communicate with 3rd party and by the way maybe a commercial executable, it doesn't respect the license ?

  



  Maybe not the correct place to ask, but would like to have some feedback before starting that project. FFMPEG dev community will reject my code proposal if it's not legal or even border line.

  



  Regards

  


• Legal issues regarding proprietary_codecs in chromium (bundled with electron)

  4 juin 2021, par Manmohan Singh

  We're in the process of building and deploying a desktop based app on electron v 12.0.7. It'll be a (free) commercial software deployed to 2-3M users worldwide.
Recently our legal team enquired about the proprietary codecs bundled with chromium and I thought the best way to confirm this would be to reach out here.

  


  So, here're specific things that I need help with :

  


  


  1. Are we shipping chromium with proprietary codecs ? If yes, what are potentially contentious codecs that come by default in chromium bundled with electron v 12.0.7 ?

     


  


  2. Is there any documentation around how the electron team builds chromium (with what flags) ?

     


  


  3. Is the default libffmpeg.dylib/dll bundled with electron building ffmpeg with support for things like H.264 and MP3 codecs ?

     


  


  4. I noticed there are libffmpeg binaries available with each electron build, e.g. https://github.com/electron/electron/releases/download/v12.0.7/ffmpeg-v12.0.7-darwin-arm64.zip . What's the purpose of this binary ?

     


  


  


  Any help would be appreciated.