Recherche avancée

Sur d’autres sites (4401)

• avcodec/videotoolbox : specify color range for hw frame ctx

  29 décembre 2023, par Zhao Zhili

  avcodec/videotoolbox : specify color range for hw frame ctx
  Signed-off-by : Zhao Zhili <zhilizhao@tencent.com>
  

  • [DH] libavcodec/videotoolbox.c

• Making a ffmpeg screen capture on Mac OS X using YUV 4:2:0 Planar color model

  30 mai 2019, par Bass

  I make screen recordings with ffmpeg, using avfoundation on Mac OS X, x11grab on Linux and gdigrab on Windows.

  The resulting files should be compatible with modern web browsers (<video></video>), so I use H.264 codec and request YUV 4:2:0 Planar pixel format.

  On Mac OS X, however (unlike Linux and Windows), I receive the following logging :

  /usr/local/bin/ffmpeg -y -v error -f avfoundation -threads 0 -hide_banner -i 1:none -f mp4 -vcodec h264 -pix_fmt yuv420p -r 25/1 -qscale:v 1 -vf scale=-1:1080 target.mp4
  
  [avfoundation @ 0x7fdba2003a00] Selected pixel format (yuv420p) is not supported by the input device.
  
  [avfoundation @ 0x7fdba2003a00] Supported pixel formats:
  
  [avfoundation @ 0x7fdba2003a00]   uyvy422
  
  [avfoundation @ 0x7fdba2003a00]   yuyv422
  
  [avfoundation @ 0x7fdba2003a00]   nv12
  
  [avfoundation @ 0x7fdba2003a00]   0rgb
  
  [avfoundation @ 0x7fdba2003a00]   bgr0

  Still, according to mplayer, the resulting MP4 file seems to have YUV 4:2:0 Planar color model :

  [h264 @ 0x1048a8ac0]Format yuv420p chosen by get_format().
  
  [h264 @ 0x1048a8ac0]Reinit context to 1728x1088, pix_fmt: yuv420p
  
  [h264 @ 0x1048a8ac0]Format yuv420p chosen by get_format().
  
  [h264 @ 0x1048a8ac0]Reinit context to 1728x1088, pix_fmt: yuv420p
  
  [swscaler @ 0x1048c3cc0]bicubic scaler, from yuv420p to yuyv422 using MMXEXT
  
  *** [scale] Exporting mp_image_t, 1728x1080x12bpp YUV planar, 2799360 bytes
  
  *** [vo] Allocating mp_image_t, 1728x1080x16bpp YUV packed, 3732480 bytes

  the same confirmed by ffmpeg :

  $ ffmpeg -i target.mp4 -hide_banner
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'target.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.20.100
  
    Duration: 00:00:04.72, start: 0.000000, bitrate: 201 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1728x1080, 197 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler

  Questions :

  1. Can someone explain the above ffmpeg logging ?
  2. If I still need to convert the avfoundation video stream to yuv420p, how do I make it on the fly (in a single ffmpeg pass) ?

• Installing "ffmpeg" package from setup.py in Apache Beam pipeline running on Google Cloud Dataflow

  17 avril 2019, par John Allard

  I’m trying to run an Apache Beam pipeline on Google Cloud Dataflow that utilizes FFmpeg to perform transcoding operations. As I understand it, since ffmpeg is not a python package (available through PIP), I need to install it from setup.py using the following lines

  # The output of custom commands (including failures) will be logged in the
  
  # worker-startup log.
  
  CUSTOM_COMMANDS = [
  
      ['apt-get', 'update'],
  
      ['apt-get', 'install', '-y', 'ffmpeg']]

  Unfortunately, this is not working. My pipeline is stalling and when I go to examine the logs I’m seeing this

  

  RuntimeError: Command ['apt-get', 'install', '-y', 'ffmpeg'] failed: exit code: 100

  It appears to be unable to find the package ’ffmpeg’. I’m curious as to why this is - ffmpeg is a standard package that should be available under apt-get.