Recherche avancée

Sur d’autres sites (12179)

• headless chrome capture screen video or animation

  14 septembre 2019, par t_io

  I try to capture some animations from a website and stitch them together using ffmpeg.
  As far as I understand the docs startScreencast is the way to go.

  If I understand that right I can start the screencast with

  await Page.startScreencast({format: 'png', everyNthFrame: 1});

  and listen to every incoming frame with

  Page.screencastFrame(image =>{
  
    const {data, metadata} = image;
  
    console.log(metadata);
  
  });

  But it’s never prints out something. So I assume it’s not called.

  I archived my goal with something like this :

  let counter = 0;
  
  while(counter < 500){
  
    await Page.startScreencast({format: 'png', everyNthFrame: 1});
  
    const {data, metadata} = await Page.screencastFrame();
  
    console.log(metadata);
  
    counter += 1;
  
  }

  Which feels like a non-performant hack.
  So any suggestions on how to use startScreencast and screencastFrame properly ?

• FFmpeg Image to Video command consuming 100% CPU

  23 décembre 2023, par Dishan Verma

  I am working on a project where I need to first extract all the frames of videos and after extracting the frames I need to stitch the frames back again showing 1 frame for exactly 1 seconds i.e I need to create a 1 FPS video from extracted frames.

  


  I am successfully able to extract frames of video using ffmpeg without any issues.

  


  But my FFmpeg command which I am using to convert frames to 1 FPS video is consuming 100% CPU, for example a 40 mb video input is consuming 8 GB of CPU. Below is how my FFmpeg command looks like.

  


  final String ffmpegCommandFormat = "%s -framerate 1 -i %s -c:v libx264 -pix_fmt yuv420p -crf 18 -y %s";
final String ffmpegCommand = String.format(ffmpegCommandFormat, FFMPEG_EXEC_PATH, framesPathRegex, pathToStoreProcessedVideo);


  


  I am creating a service which needs to support around 2 GB sized videos and with the current behaiviour it cannot even support 100 MB of video.

  


  Can anyone please help me here to understand why FFmpeg is consuming too high CPU and how can i resolve this issue ?
Is there any alternate/better/fast/efficient command which I can use to created 1 FPS video wither from extracted frames or directly from input video ?

  


  I am new to ffmpeg so not sure what else to explore.

  


• The proper way to limit framerate when recording screen on macOS

  5 juillet 2024, par jsx

  macOS 14.5, FFmpeg 7.0.1. To record the screen, if I use the code from Wiki, that is,

  


  ffmpeg -f avfoundation -i 1 output.mp4


  


  the frame rate seems to be so high that when I press q to stop recording, the following message persists until my MacBook Pro starts to noise by its cooler : "[q] command received. Exiting."

  


  My current solution is to add -r after -i :

  


  ffmpeg -f avfoundation -i 1 -r 24 output.mp4


  


  But I heard that a more correct solution is to replace -r with -framerate and to put it before instead of after -i :

  


  


  ffmpeg -f avfoundation -framerate 24 -i 1 output.mp4


  


  Note that I used -framerate as an input option instead of -r 24 as an output option, so I'm telling avfoundation to record at 24fps instead of recording at the default fps and then forcing FFmpeg to drop or duplicate frames to give you the desired 24.

  


  


  This doesn't work for me currently, and appears to be the same as I don't use -r at all.

  


  And so, what is the proper way to fix the "too high framerate" issue when recording the screen on macOS ? Do we need -r or instead -framerate, and where to put it, before or after -i ?

  


  Just in case, here is the log of ffmpeg -f avfoundation -i 1 output.mp4 -v verbose :

  


  https://github.com/jsx97/test/blob/main/ffmpeg.log