Recherche avancée

Sur d’autres sites (4829)

• avcodec/tiff : Enforce increasing offsets

  9 août 2019, par Michael Niedermayer

  avcodec/tiff : Enforce increasing offsets
  This may break some valid tiff files, it appears the specification does not require
  
  the offsets to be increasing. They increase in the 2 test files i have though except
  
  the last offset which is 0 (an end marker) and for which a special case is added to
  
  avoid asking for a sample for that end marker.
  See : [FFmpeg-devel] [PATCH 2/2] avcodec/tiff : Detect infinite retry loop
  
  for an alternative implementation
  Fixes : Timeout (Infinite -> Finite)
  
  Fixes : 15706/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_TIFF_fuzzer-5114674904825856
  This variant was requested by paul on IRC
  
  Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
  
  Reviewed-by : Paul B Mahol <onemda@gmail.com>
  
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavcodec/tiff.c

• How can I make windows "like" the mp4 files I create in Linux and sync with Rsync

  17 juillet 2019, par Geoff Fox

  I am a meteorologist on TV remotely from a studio I built. My control room uses a TriCaster, an amazing studio-in-a-box which runs on a Windows 7 variant. I make my weather maps myself on a Centos 7 machine — around 40,000/day.

  I don’t entirely understand the problem, but here’s a quote from someone helping me at NewTek (the TriCaster company)

  Rsync is built on a *nix based environment where all the file permissions and attributes are based on the Linux environment. There is no meaning for this in NTFS and Windows. The result is you get files that will most likely have the read-only flag set or no flag at all. Other attributes will be delivered as null. I’m sure from your own programming experience, programs don’t like null values and they generally have to be accounted for very specifically.

  And so the finely tuned TriCaster stumbles, meaning lost frames or other problems caused by my short weather animations.

  Here are some samples of the Rsync code I use

  rsync -r -t -s -v --no-p --chmod=ugo=rwX /var/www/html/output/loops/mp4/conus*.mp4 /mnt/tricaster/Clips/Import
rsync -r -t -s -v --no-p --chmod=ugo=rwX /var/www/html/output/loops/mp4/nebraska*.mp4 /mnt/tricaster/Clips/Import
rsync -r -t -s -v --no-p --chmod=ugo=rwX /var/www/html/output/loops/mp4/northernplains*.mp4 /mnt/tricaster/Clips/Import

  These are mp4 files. They are only used locally. I really don’t care what flags are checked and permissions filled as long as Windows 7 doesn’t care.

  At this point I always like to tell folks, though I do write some code my last computer class was in high school,’67-68 semester. Thanks in advance for your help.

• 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