Recherche avancée

Sur d’autres sites (4791)

• avformat/hlsenc : better error log message for var_stream_map content

  22 juin 2019, par Bela Bodecs

  avformat/hlsenc : better error log message for var_stream_map content
  When multiple variant streams are specified by var_stream_map option,
  
  %v is expected either in the filename or in the last sub-directory name,
  
  but only in one of them. When both of them contains %v string, current
  
  error message only states half of the truth.
  
  And even %v may appears several times inside the last sub-directory name
  
  or in filename pattern.
  
  This patch clarifies this in the log message and in the doc also.
  Signed-off-by : Bela Bodecs <bodecsb@vivanet.hu>
  

  • [DH] doc/muxers.texi
  • [DH] libavformat/hlsenc.c

• Trying to use ffmpeg to create slideshow from ISO-8601 named pictures. Getting output with no playable streams

  19 juin 2019, par Robert Ellegate

  I’m trying to create a slideshow of images that are irregular in dimension/orientation but all named with the same ISO-8601 date format.

  I’ve normalized the filenames so they are all YYYYMMDD.jpg. I have tried using the globular pattern type for ffmpeg and various methods for inputting the files, including piping the concatenation of the files into ffmpeg.

  Here are the images I’m trying to use :

  $ ls *.jpg | xargs -n1 file
  
  20190411.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=upper-left, width=0], baseline, precision 8, 10128x3984, components 3
  
  20190417.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=lower-right, width=0], baseline, precision 8, 10176x3952, components 3
  
  20190424.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=upper-left, width=0], baseline, precision 8, 12128x3840, components 3
  
  20190429.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=upper-left, width=0], baseline, precision 8, 11104x3888, components 3
  
  20190430.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=lower-right, width=0], baseline, precision 8, 10992x3920, components 3
  
  20190501.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=lower-right, width=0], baseline, precision 8, 10528x3936, components 3
  
  20190502.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=lower-right, width=0], baseline, precision 8, 10992x3792, components 3
  
  20190508.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=lower-right, width=0], baseline, precision 8, 11008x3808, components 3
  
  20190515.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=lower-right, width=0], baseline, precision 8, 10416x3760, components 3
  
  20190516.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=lower-right, width=0], baseline, precision 8, 10928x3760, components 3
  
  20190517.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=lower-right, width=0], baseline, precision 8, 10720x3840, components 3
  
  20190522.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=[*0*], width=0], baseline, precision 8, 6552x1688, components 3
  
  20190523.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=[*0*], width=0], baseline, precision 8, 6572x1700, components 3
  
  20190524.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=[*0*], width=0], baseline, precision 8, 6468x1659, components 3
  
  20190528.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=[*0*], width=0], baseline, precision 8, 5424x1644, components 3
  
  20190529.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=7, model=Pixel 2 XL, height=0, manufacturer=Google, orientation=[*0*], datetime=2019:05:29 16:38:01, width=0]
  
  20190531.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=[*0*], width=0], baseline, precision 8, 6584x1693, components 3
  
  20190603.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=[*0*], width=0], baseline, precision 8, 6536x1690, components 3
  
  20190604.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=[*0*], width=0], baseline, precision 8, 5748x1618, components 3
  
  20190606.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=[*0*], width=0], baseline, precision 8, 6196x1690, components 3
  
  20190607.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=[*0*], width=0], baseline, precision 8, 6112x1674, components 3
  
  20190610.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=[*0*], width=0], baseline, precision 8, 6440x1670, components 3
  
  20190611.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=[*0*], width=0], baseline, precision 8, 6312x1694, components 3
  
  20190612.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=4, height=0, orientation=[*0*], width=0], baseline, precision 8, 6176x1689, components 3

  And these are the various ffmpeg commands I’ve tried using :

  cat *.jpg | ffmpeg -framerate 1/5 -c:v libx264 -r 30 -pix_fmt yuv420p out.mp4

  cat *.jpg | ffmpeg -f image2pipe -i - output.mkv

  ffmpeg -framerate 1/5 -pattern_type glob -i '*.jpg' out.mp4

  ffmpeg -framerate 1/5 -pattern_type glob -i '*.jpg' -c:v libx264 -vf fps=25 -pix_fmt yuv420p out.mp4

  I’m trying to create a video that shows each image for 5 seconds in order, but I’m getting a mp4 video file with no playable streams.

• av_format/hlsenc : fix %v handling by format_name function

  17 juin 2019, par Bodecs Bela

  av_format/hlsenc : fix %v handling by format_name function
  Hi All,
  When multiple variant streams are specified by var_stream_map option, %v
  
  placeholder in various names ensures that each variant has its unique
  
  names. Most of %v handlng is done in format_name function. Currently
  
  in this function the result buffer is the same as the
  
  input pattern buffer, so you must allocate it before calling format_name
  
  function. It also means, that it is silently assumed that the result
  
  string will NOT be
  
  longer that the pattern string. It is true most of the time, because %v
  
  may appear only once in the pattern string and number of variant streams
  
  is less than 100 in practical cases. But theoretically it will fail if
  
  specified number of variant streams is greater than 100 (i.e. longer
  
  than 2 digits).
  
  This patch fixes this behaviour by altering format_name function to
  
  allocate the
  
  result buffer and return it to the caller.
  Please, review this patch.
  best,
  Bela
  
  >From 6377ebee8a106a9684d41b270c7d6c8e57cd3e7b Mon Sep 17 00:00:00 2001
  
  From : Bela Bodecs <bodecsb@vivanet.hu>
  
  Date : Mon, 17 Jun 2019 14:31:36 +0200
  
  Subject : [PATCH] av_format/hlsenc : fix %v handling by format_name function
  When multiple variant streams are specified by var_stream_map option, %v
  
  placeholder in various names ensures that each variant has its unique
  
  names. Most of %v handlng is done in format_name function. Currently
  
  in this function the result buffer is the same as the input pattern
  
  buffer, so you must allocate it before calling format_name function. It
  
  also means, that it is silently assumed that the result string will NOT
  
  be longer that the pattern string. It is true most of the time, because
  
  %v may appear only once in the pattern string and number of variant
  
  streams is less than 100 in practical cases. But theoretically it will
  
  fail if specified number of variant streams is greater than 100. This
  
  patch fixes this behaviour by altering format_name function to allocate
  
  the result buffer and return it to the caller.
  Signed-off-by : Bela Bodecs <bodecsb@vivanet.hu>
  

  • [DH] libavformat/hlsenc.c