Recherche avancée

Sur d’autres sites (4160)

• On the server running Ubuntu 14.04 to make slideshow of images with different types of transitions ? [on hold]

  16 mars 2017, par user3593350

  Good day !

  You want to make a slideshow on the server from a set of images. I did it with ffmpeg, is it possible to make video from set of images, you can do fade in/out effect to fade in/out images. But what if you want to make several types of transitions. The Internet is full of sites that make slideshow with different transitions, some tool must be.

  Nothing normal I did not find who can faced similar problems and can suggest what tools to use ?
  While there is the idea to find the editor, where a terminal will be glued two pictures, like draw one picture over another in the scale of 50%, then 51%, etc. thereby creating frames for a transition, then using ffmpeg to combine them into a video and get video with the transition.

• FFMPEG - height not divisible by 2

  27 septembre 2019, par iSaBo

  i have an problem with ffmpeg. i would like to format a image sequence into a video. I use the followed command for this :

  ffmpeg -framerate 24 -i image%04d.jpeg Project.mp4 -vf "pad=ceil(iw/2)*2:ceil(ih/2)*2"

  i have 4 pictures :

  • image0001.jpeg
  • image0002.jpeg
  • image0003.jpeg
  • image0004.jpeg

  With this command, i get the following error :

  [libx264 @ 000001f12e7a0540] height not divisible by 2 (1200x1599) 
  
  Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe 
  
  incorrect parameters such as bit_rate, rate, width or height
  
  Conversion failed!

  Can someone tell me why this mistake comes and how can I fix it ?

  Thanks

• avcodec/h26[45]_metadata_bsf : Use separate contexts for reading/writing

  6 juillet 2020, par Andreas Rheinhardt

  avcodec/h26[45]_metadata_bsf : Use separate contexts for reading/writing
  Currently, both bsfs used the same CodedBitstreamContext for reading and
  
  writing ; as a consequence, the state of the writer's context at the
  
  beginning of writing a fragment is exactly the state of the reader after
  
  having read the fragment ; in particular, the writer might not have
  
  encountered one of its active parameter sets yet.
  This is not nice and may lead to invalid output even when the input
  
  is completely spec-compliant : Think of an access unit containing
  
  a primary coded picture referencing a PPS with id id (that is known from
  
  an earlier access unit/from extradata), then a new version of the PPS
  
  with id id and then a redundant coded picture that is also referencing
  
  the PPS with id id. This is spec-compliant, as the standard allows to
  
  overwrite a PPS with a different PPS in between coded pictures and not
  
  only at the beginning of an access unit. In this scenario, the reader
  
  would read the primary coded picture with the old PPS and the redundant
  
  coded picture with the new PPS (as it should) ; yet the writer would
  
  write both with the new PPS as extradata which might lead to errors or
  
  to invalid data being output without any error (e.g. if the two PPS
  
  differed in redundant_pic_cnt_present_flag).
  The above scenario does not directly translate to HEVC as long as one
  
  restricts oneself to input with nuh_layer_id == 0 only (as cbs_h265
  
  does : it currently strips away any NAL unit with nuh_layer_id > 0 when
  
  decomposing) ; if one doesn't the same issue as above can happen.
  If one also allowed input packets to contain more than one access unit,
  
  issues like the above can happen even without redundant coded
  
  pictures/multiple layers.
  Therefore this commit uses separate contexts for reader and writer.
  Reviewed-by : Mark Thompson <sw@jkqxz.net>
  
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  

  • [DH] libavcodec/h264_metadata_bsf.c
  • [DH] libavcodec/h265_metadata_bsf.c