Recherche avancée

Sur d’autres sites (2420)

• FFMPEG [SHELL CMD] cutting last x frames [SHELL CMD] combining videos

  25 avril 2014, par user1708604

  .mp4 videos in 1920 x 1080, 25 frames / second
  different length

  Two commands needed :

  0) One command should delete x frames from the end of the video and create a new video without the last x frames as .mp4, save it in folder y
  1) One command should combine x amount of videos to one new video

  Just for info : I am using Python to call ffmpeg.
  Platform : Windows or CentOS.

  Many thanks in advance. :)

• subprocess.Popen can't find the file when shell=False and doesn't know ffmpeg when shell=True [duplicate]

  26 novembre 2023, par Waschbrettwade

  I am trying to get an offline speech-to-text library called "vosk" running following this tutorial : https://medium.com/@johnidouglasmarangon/automatic-speech-recognition-with-vosk-828569219f2b

  


  In this, subprocess.Popen is being used like this :

  


  ffmpeg_command = [
            "ffmpeg",
            "-nostdin",
            "-loglevel",
            "quiet",
            "-i",
            filename,
            "-ar",
            str(SAMPLE_RATE),
            "-ac",
            "1",
            "-f",
            "s16le",
            "-",
        ]

    with subprocess.Popen(ffmpeg_command, stdout=subprocess.PIPE) as process:


  


  When running this in Jupyter Notebook, no problem at all. But whenever I run this in VSCode, it produces the error :

  


  FileNotFoundError: [WinError 2] The system couldn't find the specified file (translated to English by me)


  


  When using shell=True as in

  


  with subprocess.Popen(ffmpeg_command, stdout=subprocess.PIPE, shell=True) as process:


  


  it tells me in the terminal (translated) :

  


  The command "ffmpeg" ist either written wrong or couldn't be found. 


  


  Do you have any idea what's causing these issues and how to fix them ?

  


• Our release signature has changed

  8 mars 2022, par justin — Security

  We have been cryptographically signing Matomo releases since 2014, so you can verify the signature of the release you downloaded. Up until Matomo 4.8.0 releases were signed with Matthieu Aubry’s personal signature. In Matomo 4.8.0 we made some improvements to our release systems including automating the release builds. As part of these improvements it makes sense to now use a Matomo signature, which means a few changes are required for verifying releases. There is no security issue around the previous key, which can still be used to verify older release builds.

  There is a new signature here : builds.matomo.org/signature.asc. You can use this signature according to our updated instructions to verify releases for Matomo version 4.8.0 and newer. You will need to import this signature to verify new releases.

  If you want to verify the signature of a release prior to Matomo 4.8.0 you can now find Matthieu’s signature here : builds.matomo.org/signature-pre-4.8.0.asc, and the same instructions apply. If you already imported Matthieu’s signature, you won’t need to do this again.