Recherche avancée

Sur d’autres sites (9840)

• How to use the function expr in drawtext ffmpeg to add a text to video ?

  18 décembre 2013, par nhanpt

  I'm try to add a text to my video using FFmpeg.
  Sources : http://www.ffmpeg.org/ffmpeg-all.html#drawtext-1

  ffmpeg -i 1385363109.avi -vf "drawtext=fontfile=/usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf : text = %{localtime}: \x=(w-tw)/2: y=h-(2*lh): fontcolor=white: box=1: boxcolor=0x00000000@1" -an -y out11.avi

  I am trying to figure out how to add a timestamp in a formatable manner (specifically, I'd like to show mm:ss). I think this should be possible using a command like

  Code : Select all
  ffmpeg -i input.avi -vf "drawtext=fontfile=/usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-Bold.ttf:expansion=normal:text='%expr=floor(t/60)~:%expr=floor(t)' : fontcolor=white " output.avi

  But I just get a lot of

  Code : Select all
  [Parsed_drawtext_0 @ 0x1a68a80] %expr=floor(t/60) is not known

  and no text is displayed.

  If I try

  Code : Select all
  ffmpeg -i input.avi -vf "drawtext=fontfile=/usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-Bold.ttf:expansion=normal:text='%expr' : fontcolor=white " output.avi

  I get instead

  Code : Select all
  [Parsed_drawtext_0 @ 0x2d22be0] %expr requires at least 1 arguments

  so the version of drawtext I have definitely recognizes the expr function, but I can't figure out the syntax for giving it an argument. Does anyone know what the synatax is for the expr (or e) function ?

  Alternately, if there is another way to display the timecode as mm:ss that would be great too. I know that using the 'timecode' argument of drawtext you can get hh:mm:ss:ff, or using text='%pts' gives me decimal seconds to the microsecond, but I am sure that my advisor (who is very picky) will not accept either of these. Thanks in advance for any assistance !

• FFMPEG filter complex concat video with slide transition between image

  9 août 2018, par Karate_Dog

  I’ve been working on video to create slideshow with slide transition, the input receives multiple images. The input will be scaled first before drawtext is drawn on each video, then apply transition effects by using overlay and finally concat the result into one video.

  I am having trouble getting the result of the drawtext to make a overlay slide transition

  ffmpeg 
  
   -i, image1.png,
  
   -i, image2.png,
  
   -filter_complex,
  
   nullsrc=size=720x720[background]; 
  
   [0:v]scale=720:720, setsar=1[scl1]; [1:v]scale=720:720,
  
    setsar=1[scl2];
  
  
  
   [scl1]zoompan=z=if(lte(zoom,1.0),1.5,max(1.001,zoom -
  
    0.0025)):fps=45:s=720x720:d=360[v0];
  
  
  
   [scl2]zoompan=z=if(lte(zoom,1.0),1.5,max(1.001,zoom - 
  
    0.0025)):fps=45:s=720x720:d=360[v1] 
  
  
  
   [v0]drawtext=fontfile=Lato-Bold.ttf: text='Example 1'
  
   :x=10:y=h-220:fontsize=80:fontcolor=white[text1];
  
  
  
   [v1]drawtext=fontfile=Lato-Bold.ttf: text='Example 2'
  
   :x=10:y=h-220:fontsize=80:fontcolor=white[text2];
  
  
  
   [background][text1]overlay=x=min(-w+(t*w/0.5),0):shortest=1[ovr1];
  
   [ovr1][text2]overlay=x=min(-w+(t*w/0.5),0):shortest=1[ovr2]; 
  
  
  
   [ovr1][ovr2]concat=n=2:v=1:a=0 
  
   format=yuv420p[video] 
  
   -map [video] outputvideo.mp4

  I got error saying that my label was invalid

  [png_pipe @ 0xf3fc2000] Invalid stream specifier: ovr1.
  
      Last message repeated 1 times
  
  Stream specifier 'ovr1' in filtergraph description

• rtmpproto : Avoid rare crashes in the fail : codepath in rtmp_open

  23 janvier, par Martin Storsjö

  rtmpproto : Avoid rare crashes in the fail : codepath in rtmp_open
  When running the cleanup in rtmp_close on failures in rtmp_open,
  
  we can in rare cases end up using rt->playpath, assuming that it
  
  is still set.
  The crash could happen if we hit the fail codepath in rtmp_open
  
  while publishing (rt->is_input == 0) with rt->state set to
  
  a value > STATE_FCPUBLISH.
  This would normally not happen while publishing ; either we have
  
  an error (and rt->state <= STATE_FCPUBLISH) or we reach
  
  rt->state = STATE_PUBLISHING, and then we also return successfully
  
  from rtmp_open.
  The unexpected combination of states could happen if the server
  
  responds with e.g. "NetStream.Play.Stop" while expecting
  
  "NetStream.Publish.Start" ; this sets rt->state to STATE_STOPPED,
  
  which also fulfills the condition "> STATE_FCPUBLISH".
  We don't need to free the rt->playpath/tcurl/flashver strings here ;
  
  they're handled via AVOption, and thus are freed automatically when
  
  the protocol instance is freed (that's why they aren't freed
  
  manually within the rtmp_close function either).
  We also don't need to free the AVDictionary with options ; it's
  
  owned by the caller.
  A smaller fix would be to just call rtmp_close before freeing
  
  the strings and dictionary, but as we don't need to free them
  
  at all, let's remove that redundant code.
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] libavformat/rtmpproto.c