Recherche avancée

Sur d’autres sites (6661)

• avcodec : Refactor common nvdec hwaccel logic

  19 novembre 2017, par Philip Langdale

  avcodec : Refactor common nvdec hwaccel logic
  The 'simple' hwaccels (not h.264 and hevc) all use the same bitstream
  
  management and reference lookup logic so let's refactor all that into
  
  common functions.
  I verified that casting a signed int -1 to unsigned char produces 255
  
  according to the C language specification.
  

  • [DH] libavcodec/nvdec.c
  • [DH] libavcodec/nvdec.h
  • [DH] libavcodec/nvdec_mpeg12.c
  • [DH] libavcodec/nvdec_vc1.c
  • [DH] libavcodec/nvdec_vp9.c

• avcodec/ac3enc : Use common encode_frame function

  7 avril 2024, par Andreas Rheinhardt

  avcodec/ac3enc : Use common encode_frame function
  This is in preparation for sharing even more stuff
  
  common to the fixed and floating-point encoders.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] libavcodec/ac3enc.c
  • [DH] libavcodec/ac3enc.h
  • [DH] libavcodec/ac3enc_fixed.c
  • [DH] libavcodec/ac3enc_float.c
  • [DH] libavcodec/ac3enc_template.c
  • [DH] libavcodec/eac3enc.c

• How to Add PulseAudio Server to quay.io/browser/google-chrome-stable Docker Image for Audio Support with Screen Recording ?

  17 avril, par Ahmed Seddik Bouchiba

  I’m trying to set up an environment for recording the screen of a Chrome browser running in a Docker container, and I need to enable audio support. I’m using the quay.io/browser/google-chrome-stable:133.0.6943.98-6 image for the browser and quay.io/aerokube/xvfb:21.1 for the virtual framebuffer to capture the screen.

  


  However, I’m facing an issue where audio is not supported in the Chrome Docker image, which I need for recording. The setup involves using FFmpeg in a separate container to stream the recorded video, but without audio from the browser, this setup isn’t complete.

  


  I’m looking for guidance on how to add a PulseAudio server to the Chrome image to enable audio support. Specifically :

  


  How can I configure the Docker image quay.io/browser/google-chrome-stable:133.0.6943.98-6 to support PulseAudio?

Are there any considerations or best practices when adding PulseAudio to a headless browser Docker container?

Is it possible to run the PulseAudio server in a separate container and link it to the Chrome container, or should it be included directly in the Chrome container?


  


  Any help on adding PulseAudio support to this Chrome Docker image would be greatly appreciated !

  


  Additional Context :

  


  The goal is to run a headless Chrome browser with audio support to record the browser’s activities (both video and audio) and stream it using FFmpeg.

I’m using Docker Compose to orchestrate the containers but haven’t figured out how to integrate PulseAudio into the setup effectively.


  


  Thanks in advance !