Recherche avancée

Sur d’autres sites (9309)

• rtsp : Interpret the text media type as AVMEDIA_TYPE_DATA

  23 février 2015, par Martin Storsjö

  rtsp : Interpret the text media type as AVMEDIA_TYPE_DATA
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DBH] libavformat/rtsp.c

• cuvid : Implement flush to support seeking in media players

  4 septembre 2016, par Philip Langdale

  cuvid : Implement flush to support seeking in media players
  Right now, if we attempt to use cuvid in a media player and then
  
  try to seek, the decoder will happily pass out whatever frames were
  
  already in flight before the seek.
  There is both the output queue in our code and some number of frames
  
  within the cuvid decoder that need to be accounted for.
  cuvid doesn’t support flush, so our only choice is to do a brute-force
  
  re-creation of the decoder, which also implies re-creating the parser,
  
  but this is fine.
  The only subtlty is that there is sanity check code in decoder
  
  initialisation that wants to make sure the HWContextFrame hasn’t already
  
  been initialised. This is a fair check to do at the beginning but not
  
  after a flush, so it has to be made conditional.
  Signed-off-by : Philip Langdale <philipl@overt.org>
  
  Signed-off-by : Timo Rothenpieler <timo@rothenpieler.org>
  

  • [DH] libavcodec/cuvid.c
  • [DH] libavcodec/version.h

• 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 !