Recherche avancée

Médias (91)

Autres articles (41)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

Sur d’autres sites (8196)

  • Call system package with Go on App Engine Standard

    8 novembre 2019, par reidreid46

    I’m trying to use FFmpeg in a Go application thats running on Google App Engine Standard. I can get this to run locally, when I point to a local instance of the FFmpeg binary using exec.Command()

    cmd := exec.Command(
    
    "/Users/justin/Desktop/conversion/ffmpeg", // this won't work on a remote server
    
    "-i", "pipe:0",
    
    "-ac", "1",
    
    "-codec:a", "libmp3lame",
    
    "-b:a", "48k",
    
    "-ar", "24000",
    
    "-f", "mp3",
    
    "pipe:1",
    
  )
    

    
  cmd.Stdin = bytes.NewReader(synthResp.AudioContent)
    

    
  var output bytes.Buffer
    
  cmd.Stdout = &output
    
  err = cmd.Run()

    Obviously, this won’t work when I deploy the application, so I need a way to point to a hosted version of the FFmpeg binary. It seems ffmpeg is a system package for the go1.11 App Engine Standard environment.

    What are "System packages" and how do I use them ?
    When I look for documentation, I find a lot of documentation on apt-get, and no documentation on how to use them, App Engine or otherwise. Do I need to install it, or should it already be part of the container(?) that App Engine is running ?

    Do I call it, like I’d call other executables ? If so, that I’d expect this to work, but it doesn’t

    cmd := exec.Command(
    
    "ffmpeg", // <------ what should this be?
    
    "-i", "pipe:0",
    
    "-ac", "1",
    
    "-codec:a", "libmp3lame",
    
    "-b:a", "48k",
    
    "-ar", "24000",
    
    "-f", "mp3",
    
    "pipe:1",
    
  )
    

    
  cmd.Stdin = bytes.NewReader(synthResp.AudioContent)
    

    
  var output bytes.Buffer
    
  cmd.Stdout = &output
    
  err = cmd.Run()

    Logging err, I see exec: "ffmpeg": executable file not found in $PATH

  • avformat/matroskadec : Do not leak queued packets on sync errors

    6 février 2019, par Michael Niedermayer
    avformat/matroskadec : Do not leak queued packets on sync errors

    Fixes : memleak
    
Fixes : clusterfuzz-testcase-minimized-audio_decoder_fuzzer-5649187601121280
    

    Reported-by : Chris Cunningham <chcunningham@google.com>
    
Tested-by : Chris Cunningham <chcunningham@google.com>
    
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libavformat/matroskadec.c

  • avformat/utils : Check cur_dts in update_initial_timestamps() more

    13 avril 2018, par Michael Niedermayer
    avformat/utils : Check cur_dts in update_initial_timestamps() more

    Fixes : runtime error : signed integer overflow : 18133149658382192 - -9223090561878065151 cannot be represented in type 'long long'
    
Fixes : crbug 831552
    

    Reported-by : Matt Wolenetz <wolenetz@google.com>
    
Reviewed-by : Matt Wolenetz <wolenetz@google.com>
    
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libavformat/utils.c

Navigation