Recherche avancée

Sur d’autres sites (6910)

• Anomalie #4402 (Fermé) : Liste de notices

  12 février 2021, par cedric -

  je ferme ce ticket, car un ticket qui référence un wiki qui liste des patches, ça commence à ressembler à un jeu de pistes
  + depuis novembre 2019 ces notices ont été corrigée
  + maintenant proposer une PR pour chaque cas quand on tombe dessus ça sera beaucoup plus efficace

• 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

  


• FFmpeg segmentation and transcoding missing frames

  15 décembre 2022, par Davidec0018

  I code videos for hobbies and have a decent understanding of ffmpeg and mkvmerge. I prefer to encode video when my computer is on for other things as well, so I recently looked for a way that I could resume encoding after the computer was turned off.

  


  I tried a virtual machine, saving the whole state and it seems to work very well, but the performance is very slow and with the same settings the encoding time is much longer than normal.

  


  I then tried to divide the starting video into several segments, so as to resume from the appropriate segment after restarting the computer.

  


  I tried to do this with ffmpeg :

  


  ffmpeg -i input -map 0:v:0 -c copy -f segment -segment_time 300 -reset_timestamps 1 segment%03d.mkv


  


  But also with the mkvtoolnix gui.

  


  Both operations provide an excellent result.Trying to merge the segments into one video, with ffconcat or mkvtoolnix the result is perfect.

  


  The problem arises when segments are encoded. I use a simple script based on slow preset for every segment in loop (I use both windows and linux) :

  


  ffmpeg -i input.mkv -threads 0 -map 0 -c:a copy -c:s copy -preset slow -pix_fmt yuv420p10le -c:v libx265 -x265-params crf=18:bframes=8:aq-mode=2:aq-strength=1.0 output.mkv


  


  Putting them together in the same way, the video also looks quite good, and with the naked eye you don't notice the passage of the various segments, but analyzing them with ffmpeg I notice that the individual segments have slightly shorter durations and a different number of frames, even 2 or 3 less. When putting together very long videos, you notice even 2 seconds of difference with the original, which also causes the audio and subtitles to go into desynch.

  


  I know the problem has to do with keyframes, timestamps and stuff like that. But I don't understand why. FFmpeg, as well as mkvmerge should split the video exactly where the keyframes are, about 300 seconds apart, so as not to mess up the video structure and allow for good encoding and reassembling.

  


  The problem is just encoding with ffmpeg that removes some frames from the original segments. Sometimes I noticed during the encoding of some segments the following error code, or maybe warning, because the encoding worked anyway :

  


  [hevc @ 0x55758bf92dc0] First slice in a frame missing.
    Last message repeated 6 times
[hevc @ 0x55758c2000c0] First slice in a frame missing.


  


  I've read every discussion about it on the net, I've tried to segment both with mp4 and mkv format, with and without audio, but the problem remains. Where am I doing wrong ?