Recherche avancée

Sur d’autres sites (7522)

• record Linux Wayland/DRM screen using ffmpeg's kmsgrab device with superimposed webcam

  7 février 2020, par nrdxp

  Setup is Linux, ffmpeg using kabylake iGPU.

  I am capturing a running sway instance using the kmsgrab device, which requires the use of a hardware backend to coherently process the image on my hardware. Only VA API fits this bill. I want to overlay the webcam in the bottom right corner during encoding. However, attempts at manipulating the filter graph to accomplish this have been unsuccessful. This is ultimately for Twitch/Tube stream.

  Right now, I am actually capturing the webcam to an sdl window, and simply recording the screen using separate instances of ffmpeg. This doesn’t actually solve my problem since the window is easily disguised by workspace switching or other windows.

  This is the workaround :

  #!/usr/bin/env zsh
  
  
  
  # record webcam and open it in sdl window
  
  ffmpeg -v quiet -hide_banner \
  
    -re -video_size 640X480 -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -i /dev/video0 \
  
    -vf 'format=nv12,hwupload' -c:v hevc_vaapi -f hevc - \
  
    | ffmpeg -v quiet -i - -f sdl2 - &
  
  
  
  # wait for webcam window to open
  
  until swaymsg -t get_tree | grep 'pipe:' &>/dev/null; do
  
    sleep 0.5
  
  done
  
  
  
  # position webcam in the bottom right corner of screen using sway
  
  swaymsg floating enable
  
  swaymsg resize set width 320 height 240
  
  swaymsg move position 1580 795
  
  swaymsg focus tiling
  
  
  
  #screencast
  
  ffmpeg -format bgra -framerate 60 -f kmsgrab -thread_queue_size 1024 -i - \
  
    -f alsa -ac 2 -thread_queue_size 1024 -i hw:0 \
  
    -vf 'hwmap=derive_device=vaapi,scale_vaapi=w=1920:h=1080:format=nv12' \
  
    -c:v h264_vaapi -g 120 -b:v 3M -maxrate 3M -pix_fmt vaapi_vld -c:a aac -ab 96k -threads $(nproc) \
  
    output.mkv
  
  
  
  kill %1

• FFMPEG command works on Mac but not on Windows [duplicate]

  24 décembre 2019, par Arthur

  This question is an exact duplicate of :

  • Creating video from images produces black screen video for certain image formats [duplicate]
    
    1 answer
    

  Hi I’m working on a project which needs to create animations by playing 2000 charts in 50 fps using FFMPEG, the command is :

  ffmpeg -y -framerate 50 -i img-%04d.png -vb 40M -vcodec h264 esez.mp4

  charts are located in the same folder with name as img-0001.png img-2000.png

  It worked well on my Mac. On Windows, the command can run and generate a mp4 file. But the animation is just black screen on Windows media player. I also tried open with VLC, it has some image, but not proper at all.

  log from Windows CMD :

  ffmpeg version git-2019-12-11-4110029 Copyright (c) 2000-2019 the FFmpeg developers
  
    built with gcc 9.2.1 (GCC) 20191125
  
    configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt --enable-amf
  
    libavutil      56. 36.101 / 56. 36.101
  
    libavcodec     58. 64.101 / 58. 64.101
  
    libavformat    58. 35.101 / 58. 35.101
  
    libavdevice    58.  9.101 / 58.  9.101
  
    libavfilter     7. 68.100 /  7. 68.100
  
    libswscale      5.  6.100 /  5.  6.100
  
    libswresample   3.  6.100 /  3.  6.100
  
    libpostproc    55.  6.100 / 55.  6.100
  
  Input #0, image2, from 'img-%04d.png':
  
    Duration: 00:00:40.18, start: 0.000000, bitrate: N/A
  
      Stream #0:0: Video: png, rgba(pc), 1000x800, 50 fps, 50 tbr, 50 tbn, 50 tbc
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (png (native) -> h264 (libx264))
  
  Press [q] to stop, [?] for help
  
  [libx264 @ 00000242aaacc6c0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
  
  [libx264 @ 00000242aaacc6c0] profile High 4:4:4 Predictive, level 3.2, 4:4:4, 8-bit
  
  [libx264 @ 00000242aaacc6c0] 264 - core 158 - H.264/MPEG-4 AVC codec - Copyleft 2003-2019 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=4 threads=6 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=abr mbtree=1 bitrate=40000 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
  Output #0, mp4, to 'esez.mp4':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
      Stream #0:0: Video: h264 (libx264) (avc1 / 0x31637661), yuv444p, 1000x800, q=-1--1, 40000 kb/s, 50 fps, 12800 tbn, 50 tbc
  
      Metadata:
  
        encoder         : Lavc58.64.101 libx264
  
      Side data:
  
        cpb: bitrate max/min/avg: 0/0/40000000 buffer size: 0 vbv_delay: N/A
  
  frame= 2009 fps= 90 q=-1.0 Lsize=    7569kB time=00:00:40.12 bitrate=1545.6kbits/s speed= 1.8x
  
  video:7545kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.322921%
  
  [libx264 @ 00000242aaacc6c0] frame I:9     Avg QP: 0.35  size: 60878
  
  [libx264 @ 00000242aaacc6c0] frame P:511   Avg QP: 0.74  size:  5275
  
  [libx264 @ 00000242aaacc6c0] frame B:1489  Avg QP: 4.35  size:  3010
  
  [libx264 @ 00000242aaacc6c0] consecutive B-frames:  0.7%  0.7%  2.2% 96.4%
  
  [libx264 @ 00000242aaacc6c0] mb I  I16..4: 85.1%  1.6% 13.3%
  
  [libx264 @ 00000242aaacc6c0] mb P  I16..4:  0.7%  0.0%  0.2%  P16..4:  1.3%  0.8%  0.4%  0.0%  0.0%    skip:96.7%
  
  [libx264 @ 00000242aaacc6c0] mb B  I16..4:  0.0%  0.0%  0.0%  B16..8:  1.6%  0.7%  0.2%  direct: 0.1%  skip:97.2%  L0:48.2% L1:39.0% BI:12.8%
  
  [libx264 @ 00000242aaacc6c0] final ratefactor: -35.51
  
  [libx264 @ 00000242aaacc6c0] 8x8 transform intra:2.6% inter:5.9%
  
  [libx264 @ 00000242aaacc6c0] coded y,u,v intra: 12.9% 2.5% 2.6% inter: 0.9% 0.5% 0.6%
  
  [libx264 @ 00000242aaacc6c0] i16 v,h,dc,p: 84% 14%  2%  0%
  
  [libx264 @ 00000242aaacc6c0] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 18%  2% 77%  0%  1%  1%  0%  0%  0%
  
  [libx264 @ 00000242aaacc6c0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 36% 22% 19%  4%  4%  4%  4%  6%  2%
  
  [libx264 @ 00000242aaacc6c0] Weighted P-Frames: Y:0.0% UV:0.0%
  
  [libx264 @ 00000242aaacc6c0] ref P L0: 60.2%  0.7% 21.4% 17.7%
  
  [libx264 @ 00000242aaacc6c0] ref B L0: 72.6% 20.2%  7.3%
  
  [libx264 @ 00000242aaacc6c0] ref B L1: 88.4% 11.6%
  
  [libx264 @ 00000242aaacc6c0] kb/s:1538.15

  Could anybody please help me with this problem ?

  Happy Holiday to all !

• Anomalie #4430 (En cours) : image_reduire gère mal les arrondis

  4 février 2020, par jluc -

  image_reduire200,200 produit parfois des images de 201px de haut ce qui semble bien peu de différence mais fait riper certaines mises en page.

  Ça semble venir de 2 phénomènes :
  - les calculs aboutissent à des images légèrement différentes de 200px
  - les arrondis pour les dimensions width et height de la balise IMG forcent le passage à 201px pour la hauteur

  Sur le document badto200.jpg uploadé, voici 1 code qui manifeste le pb :
  -

  [(#FICHIER|image_proportions1,1,focus|image_reduire200,200)]

  In situ, c’est dans un portfolio avec bootstrap 3 :
  

  ...

  
  et ça produit des résultats avec de gros blancs comme sur l’image screenshot.jpg

  Je résoud le problème en doublant l’appel à |image_reduire(200,200). J’espère que le filtre est optimisé quand ya rien à faire... Mais il devrait être possible de mieux viser les (200,200).