Recherche avancée

Sur d’autres sites (13667)

• Add Win32 GDI-based screen grabbing

  2 avril 2014, par Calvin Walton

  Add Win32 GDI-based screen grabbing
  Based on original code by Christophe Gisquet in 2010, updated to work
  
  with current ffmpeg APIs.
  Supports grabbing a single window or an area of the screen, including
  
  support for multiple monitors (Windows does funky stuff with negative
  
  coordinates here).
  I’ve moved most of the configuration to AVOptions ; the input file name
  
  is now only the string "desktop", or "title=<windowname>" to select a
  
  single window. The AVOptions are the same as x11grab where possible.
  Code has been added to support a "show_region" mode, like x11grab, which
  
  will draw a rectangle on the screen around the area being captured.
  Instead of duplicating code for paletted image handling, I make use of
  
  the GDI API’s ability to output DIB (BMP) images, which can be run
  
  through ffmpeg’s existing BMP decoder.
  Signed-off-by : Calvin Walton <calvin.walton@kepstin.ca>
  
  Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] Changelog
  • [DH] configure
  • [DH] doc/general.texi
  • [DH] doc/indevs.texi
  • [DH] libavdevice/Makefile
  • [DH] libavdevice/alldevices.c
  • [DH] libavdevice/gdigrab.c

• Revision adf4293e4e : Adapt strength of AQ2. Adapt the use of segmentation in AQ mode 2 based on the

  4 juin 2014, par Paul Wilkins

  Changed Paths :
   Modify /vp9/encoder/vp9_aq_complexity.c

  
   Modify /vp9/encoder/vp9_segmentation.c

  
  
  Adapt strength of AQ2.

  Adapt the use of segmentation in AQ mode 2 based on
  the ambient kf/arf/gf Q.

  Disable segmentation where the rate per SB is very
  low and overheads are likely to outweigh the benefits.

  This patch reduces the -ve average metrics impact
  of AQ mode 2 while allowing stronger 3 segment AQ
  in some cases. Average improvement 0.5-1.0%.

  Change-Id : I5892dfcc7507c5cc6444531cc7fe17554cf8d0c7

• Legal issues in shipping apps based on Electron framework (libffmpeg)

  21 juin 2021, par Manmohan Singh

  We're in the process of building and deploying a desktop based app on electron v 12.0.7. It'll be a (free) commercial software deployed to 2-3M users worldwide.
Recently our legal team enquired about the proprietary codecs bundled with chromium and I thought the best way to confirm this would be to reach out here.

  


  So, here're specific things that I need help with :

  


  


  1. Are we shipping chromium with proprietary codecs ? If yes, what are potentially contentious codecs that come by default in chromium bundled with electron v 12.0.7 ?

     


  


  2. Is there any documentation around how the electron team builds chromium (with what flags) ?

     


  


  3. Is the default libffmpeg.dylib/dll bundled with electron building ffmpeg with support for things like H.264 and MP3 codecs ?

     


  


  4. I noticed there are libffmpeg binaries available with each electron build, e.g. https://github.com/electron/electron/releases/download/v12.0.7/ffmpeg-v12.0.7-darwin-arm64.zip . What's the purpose of this binary ?

     


  


  


  Any help would be appreciated.