Recherche avancée

Sur d’autres sites (11583)

• 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

• lavfi/vf_scale : use default swscale flags for scaler

  4 août 2021, par Linjie Fu

  lavfi/vf_scale : use default swscale flags for scaler
  Currently the default swscale flags for simple filter graph is bicubic,
  
  however for complex filter graph it uses bilinear as decleared in scale
  
  filter.
  $ffmpeg -v verbose -i input.mp4 -vf format=yuv420p,scale=800x600 -an -f null -
  
  [Parsed_scale_1 @ 0x7f86d2c160c0] w:1920 h:1080 fmt:yuv420p sar:0/1 -> w:800 h:600 fmt:yuv420p sar:0/1 flags:0x4
  $ffmpeg -v verbose -i input.mp4 -filter_complex format=yuv420p,scale=800x600 -an -f null -
  
  [Parsed_scale_1 @ 0x7f8779e046c0] w:1920 h:1080 fmt:yuv420p sar:0/1 -> w:800 h:600 fmt:yuv420p sar:0/1 flags:0x2
  Use default swscale flags (bicubic currently) for scale filter.
  
   Remove flags="bilinear" from vf_scale
  
   Update the FATE refs
  Signed-off-by : Linjie Fu <linjie.justin.fu@gmail.com>
  

  • [DH] libavfilter/vf_scale.c
  • [DH] tests/ref/fate/filter-scale2ref_keep_aspect

• lavc/avcodec : Add HEVC Screen Content Coding Extensions profile

  16 février 2023, par Linjie Fu

  lavc/avcodec : Add HEVC Screen Content Coding Extensions profile
  Described in HEVC spec A.3.7. Bump minor version and add APIchanges
  
  entry for new added profile.
  Signed-off-by : Linjie Fu <linjie.justin.fu@gmail.com>
  
  Signed-off-by : Fei Wang <fei.w.wang@intel.com>
  

  • [DH] doc/APIchanges
  • [DH] libavcodec/avcodec.h
  • [DH] libavcodec/hevc_ps.c
  • [DH] libavcodec/profiles.c
  • [DH] libavcodec/version.h