3 ms·

how are you able to get around ffmpeg licensing since it is client app which requires you to open your code if you use ffmpeg GPL?

anshrathodfr 2y ago
it uses homebrew to install the FFmpeg on the user's device. the app doesn't bundle any libs to comply with their license limitations.
globalnode 2y ago
O_o, well that was a short lived app.
- odo1242 2y ago
  FFmpeg is LGPL, not GPL. This means that you can link it in non open source apps and only have to open source modifications to FFmpeg itself.
levkk 2y ago
It does not require that you do that. It only requires you to open source any modifications you've made to ffmpeg.
- newusertoday 2y ago
  it is slightly more nuanced, if you do static linking it is considered derivative work and does requires you to open it. Since the app is based on ffmpeg which is GPL(core is LGPL) i am curious to know how it is getting used.
  - anshrathodfr 2y ago
    i didn't bundle the ffmpeg in the app. It uses homebrew to install ffmpeg on the user's device. this is the acceptable way since ffmpeg confirms it on twitter/X. https://x.com/FFmpeg/status/1766649563891339510 https://x.com/FFmpeg/status/1766649563891339510
    - p4bl0 2y ago
      This tweet also explicitly says "But still would be nice to have some credit.". Why isn't FFmpeg mentioned on your app's website? The same goes for ImageMagick by the way.
      - anshrathodfr 2y ago
        there is a dedicated page for credits: https://pimosa.app/credits https://pimosa.app/credits
  - kiritanpo 2y ago
    Static linking of LGPL content (thus making it derivative work) only requires that it must allow "modification of the work for the customer's own use and reverse engineering for debugging such modifications". Making your own code public is not the only way to achieve this. You can also make available to customer object files and build instructions to recreate your software with the (modified) statically linked LGPL content. (if it's LGPL > 2.1 you have extra requirements: you need to provide all toolchains/dependencies and it must be actually possible to install a modified version on the hardware) Granted, this is not commonly used but I've used this on some projects where dynamic linking was not available/desired by client.
fourthark 2y ago
FFmpeg is mostly LGPL and has very clear and helpful instructions about how to incorporate and distribute it in compliance.
rane 2y ago
It doesn't if you use it as a bundled binary. https://opensource.stackexchange.com/questions/4008/can-i-use-distribute-lgpl-command-line-software-in-mine-that-isnt-lgpl?rq=1 https://opensource.stackexchange.com/questions/4008/can-i-us... https://opensource.stackexchange.com/questions/5188/software-if-i-bundle-built-compiled-gpl-2-licensed-software-with-commercial-s?noredirect=1&lq=1 https://opensource.stackexchange.com/questions/5188/software...

anshrathodfr 2y ago

it uses homebrew to install the FFmpeg on the user's device. the app doesn't bundle any libs to comply with their license limitations.

globalnode 2y ago

O_o, well that was a short lived app.

odo1242 2y ago
FFmpeg is LGPL, not GPL. This means that you can link it in non open source apps and only have to open source modifications to FFmpeg itself.

levkk 2y ago

It does not require that you do that. It only requires you to open source any modifications you've made to ffmpeg.

newusertoday 2y ago
it is slightly more nuanced, if you do static linking it is considered derivative work and does requires you to open it. Since the app is based on ffmpeg which is GPL(core is LGPL) i am curious to know how it is getting used.
- anshrathodfr 2y ago
  i didn't bundle the ffmpeg in the app. It uses homebrew to install ffmpeg on the user's device. this is the acceptable way since ffmpeg confirms it on twitter/X. https://x.com/FFmpeg/status/1766649563891339510 https://x.com/FFmpeg/status/1766649563891339510
  - p4bl0 2y ago
    This tweet also explicitly says "But still would be nice to have some credit.". Why isn't FFmpeg mentioned on your app's website? The same goes for ImageMagick by the way.
    - anshrathodfr 2y ago
      there is a dedicated page for credits: https://pimosa.app/credits https://pimosa.app/credits
- kiritanpo 2y ago
  Static linking of LGPL content (thus making it derivative work) only requires that it must allow "modification of the work for the customer's own use and reverse engineering for debugging such modifications". Making your own code public is not the only way to achieve this. You can also make available to customer object files and build instructions to recreate your software with the (modified) statically linked LGPL content. (if it's LGPL > 2.1 you have extra requirements: you need to provide all toolchains/dependencies and it must be actually possible to install a modified version on the hardware) Granted, this is not commonly used but I've used this on some projects where dynamic linking was not available/desired by client.

fourthark 2y ago

FFmpeg is mostly LGPL and has very clear and helpful instructions about how to incorporate and distribute it in compliance.

rane 2y ago

It doesn't if you use it as a bundled binary. https://opensource.stackexchange.com/questions/4008/can-i-use-distribute-lgpl-command-line-software-in-mine-that-isnt-lgpl?rq=1 https://opensource.stackexchange.com/questions/4008/can-i-us... https://opensource.stackexchange.com/questions/5188/software-if-i-bundle-built-compiled-gpl-2-licensed-software-with-commercial-s?noredirect=1&lq=1 https://opensource.stackexchange.com/questions/5188/software...