Recherche avancée

Sur d’autres sites (8464)

• ffmpeg with a python wrapper— need help avoiding multiple passes on a file

  19 octobre 2018, par Dean D D

  I would like some help refactoring this code to reduce the amount of passes ffmpeg must make on the file. I figure creating a single compounded ffmpeg command would do the trick, but I am kind of lost.

  def processVideo(videoFile, venueWatermarkFile, companyWatermarkFile, mp3File=None, m4vFile=None, cropH, cropW, resizeH, resizeW):
  
      if mp3File != "" :
  
          subprocess.call('ffmpeg -y -i ' + videoFile + ' -i ' + audio + ' -filter_complex "[0:v]scale=480:ih*480/iw, crop=480:480, loop=loop=3:size=210, trim=duration=15[video]" -shortest -map "[video]" -map "1:a?" -c:a aac new1.mp4', shell=True)
  
      else :
  
          subprocess.call('ffmpeg -y -i ' + videoFile + ' -i ' + audio + ' -vf "scale=480:ih*480/iw, crop=480:480" new1.mp4', shell=True)
  
  
  
      if m4vFile != "":   
  
          subprocess.call('ffmpeg -i ' + videoFile + ' -i ' + m4v + ' -filter_complex " [0:v] scale=480:ih*480/iw, crop=480:480 [bg]; [1:v] chromakey=00FF00:similarity=0.2:blend=0.3 [fg]; [bg][fg] overlay=shortest=1 [v] " -map "[v]" -map "0:a?" -f mp4 new1.mp4', shell=True)
  
  
  
      subprocess.call('ffmpeg -y -i new1.mp4 -i ' + venueWatermarkFile + ' -filter_complex "overlay=0:0" -codec:a copy new2.mp4', shell=True)
  
      subprocess.call('ffmpeg -y -i new2.mp4 -i ' + companyWatermarkFile + ' -filter_complex "overlay=0:0" -codec:a copy new.mp4', shell=True)
  
  
  
      subprocess.call('ffmpeg -y -i new.mp4 new.gif -hide_banner', shell=True)
  
      subprocess.call('ffmpeg -y -i new.mp4 -ss 00:00:00.000 -vframes 1 new.jpg', shell=True)
  
  
  
      os.remove("new1.mp4")
  
      os.remove("new2.mp4")
  
  
  
  
  
  processVideo("video-standard.mp4", "venue-standard.png", "company-standard.png", "clip.mp3", "animation.m4v")

• Electron, Chromium and ffmpeg licencing confusion, how to build electron with licence compatible ffmpeg [migrated]

  12 mars 2021, par Iamisti

  Intro :
Recently I'm working on an electron based application that is free to use but also has subscription based services.
It came to my attention that ffmpeg is shipped with electron, which has GPL/LGPL licence.

  


  My quetion is :

  


  

  • Am I legally able to still distribute the application and be licence-compliant with ffmpeg without owning any proper licence to it ? I thought chromium dealt with the licencing on this topic since so many applications nowadays are shipped with using electron and chromium under the hood.

  


  • How do I compile/build electron to make it licence compatible (in case its not ?)

  


  


  I did a lot of reseearch and I found out the followings :

  


  


  • ffmpeg is shipped with chromium, they built their own version of ffmpeg and it seems they also have licence for it. Although that might be that they just push the responsibility down on the software developer/company who distributes their application with chromium.
Chromium licence for ffmpeg : https://chromium.googlesource.com/chromium/third_party/ffmpeg/+/703e920bb75053bf6b87d41d198cbbfbce3fb7ad/LICENSE

    


  


  • Apparently ffmpeg has a checklist of how to be licence compliant. Does that mean if I do all these steps, I can still distribute the application and can legally use it ? Licence checklist for ffmpeg : http://ffmpeg.org/legal.html

    


  


  • checking out some popular electron applications like Discord, Figma, Slack, etc... they ALL have ffmpeg included cause of electron when you install them. I wonder how they made it legal ? I don't see any of these checklists done on any of these popular applications.

    


  


  


  I'm know very little regarding licences, so any help would be incredibly huge help for me.

  


• Matomo 2 reaches end of life soon (December 2017), update now !

  7 décembre 2017, par Matomo Core Team — Community

  In less than three weeks, Matomo (Piwik) 2 will be no longer supported. This means that no further (security) updates will be released for this version. As per our Long Term Support announcement, Matomo 2.X is supported for 12 months after the initial release of Matomo 3.0.0 which was on December 18th 2016. Therefore, Matomo 2 will no longer receive any updates after December 18th 2017.

  It has been almost a year since we released Matomo (Piwik) 3 and we highly recommend updating to Matomo 3 ASAP. The major new release came with a new UI, performance and security improvements. If you are still on Matomo 2, the security improvements alone should be worth updating your Matomo to Matomo 3 now. We cannot recommend this enough.

  The update to Matomo (Piwik) 3 should be smooth, but may take a while depending on the amount of data you have.

  • If you have any problem with the update, feel free to get in touch with us, or ask in the forums.
  • If you are currently using Matomo (Piwik) self-hosted and would like to be upgraded, plus your Matomo managed in the official Cloud-hosted service, contact InnoCraft Cloud and they will migrate your database.

  At Matomo (Piwik) and InnoCraft, the company of the makers of Matomo, we have seen many thousands of Matomo installations upgraded over the past year and look forward to an exciting future for Matomo 3 and beyond !