Recherche avancée

Sur d’autres sites (7902)

• FFMPEG : output scene change times in frames

  29 mai 2019, par Mark Raishbrook

  I’m successfully using the -vf select='gte(scene,0.4)',metadata=print:file=shotcuts.txt command to get FFMPEG to detect scene changes and output the results to file. Is it possible to force the pts field to be in frames rather than the default, which seems to vary depending on the video format (e.g. frames for AVI files, nanosecs for MOV/MP4) ?

  Processing an AVI file, for example, outputs time stamps in frames :

  frame 0 pts 151
  frame 1 pts 206

  Whereas an MP4 file outputs as media time :

  frame 0 pts 540000
  frame 1 pts 738000

• FFmpeg 5 C api codec : how many times will EOF be returned by the receiving end ?

  3 février 2024, par Guanyuming He

  Edit : I may have written my questions unclearly at first, so I rewrote them. Sorry if you had found my questions confusing.

  


  I'm new to FFmpeg api programming (I'm using version 5.1) and am learning from the documentation and official examples.

  


  In the documentation page about send/receive encoding and decoding API overview, end of stream situation is discussed briefly :

  


  


  End of stream situations. These require "flushing" (aka draining) the codec, as the codec might buffer multiple frames or packets internally for performance or out of necessity (consider B-frames). This is handled as follows :

  


  


  


  Instead of valid input, send NULL to the avcodec_send_packet() (decoding) or avcodec_send_frame() (encoding) functions. This will enter draining mode.
Call avcodec_receive_frame() (decoding)
or avcodec_receive_packet() (encoding) in a loop until AVERROR_EOF is returned. The functions will not return AVERROR(EAGAIN), unless you forgot to enter draining mode.
Before decoding can be resumed again, the codec has to be reset with avcodec_flush_buffers().

  


  


  As I understand it, when I get AVERROR_EOF, I have reached a special point where I need to drain buffered data from the codec and finally reset the codec with avcodec_flush_buffers(). Without doing it, I cannot continue decoding/encoding.

  


  Is my understanding correct ?

  


  If so, then I have some questions :

  


  

  1. How many times at most can EOF be returned by the receiving end during one complete process, for example, decoding ?

  


  2. If the answer to the first question is infinity, then : If I received an EOF from the receiving end when I already finished sending data (e.g. when after EOF is returned by av_read_frame()), how should I tell if it's really finished ? Here there is no return code only for indicating if the receiving is finished.

  


  3. The data returned from the receive_... functions during draining, should I take them as valid ?

  


  


  I might have found answers to those in the official examples, but I'm not sure if the answer is universally true. I noticed that in some official examples, like in transcode_aac.c, draining is only done for the first EOF reached, and then after the second one is received, it is regarded that there are really nothing left. Any data received during draining is also written to the final output.

  


  Am I correct on interpreting the example ? If so, can I say that the answer to question 1 is once, and the answer to question 3 is yes ?

  


  I appreciate your response and time in advance. :)

  


• movenc : Add a unit test for signaling of the track start times

  10 novembre 2015, par Martin Storsjö

  movenc : Add a unit test for signaling of the track start times
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DBH] libavformat/movenc-test.c
  • [DBH] tests/ref/fate/movenc