Recherche avancée

Sur d’autres sites (10725)

• avformat/matroskaenc : Redo handling of FlagDefault

  18 janvier 2020, par Andreas Rheinhardt

  avformat/matroskaenc : Redo handling of FlagDefault
  Up until now, the Matroska muxer would mark a track as default if it had
  
  the disposition AV_DISPOSITION_DEFAULT or if there was no track with
  
  AV_DISPOSITION_DEFAULT set ; in the latter case even more than one track
  
  of a kind (audio, video, subtitles) was marked as default which is not
  
  sensible.
  This commit changes the logic used to mark tracks as default. There are
  
  now three modes for this :
  
  a) In the "infer" mode the first track of every type (audio, video,
  
  subtitles) with default disposition set will be marked as default ; if
  
  there is no such track (for a given type), then the first track of this
  
  type (if existing) will be marked as default. This behaviour is inspired
  
  by mkvmerge. It ensures that the default flags will be set in a sensible
  
  way even if the input comes from containers that lack the concept of
  
  default flags. This mode is the default mode.
  
  b) The "infer_no_subs" mode is similar to the "infer" mode ; the
  
  difference is that if no subtitle track with default disposition exists,
  
  no subtitle track will be marked as default at all.
  
  c) The "passthrough" mode : Here the track will be marked as default if
  
  and only the corresponding input stream had disposition default.
  This fixes ticket #8173 (the passthrough mode is ideal for this) as
  
  well as ticket #8416 (the "infer_no_subs" mode leads to the desired
  
  output).
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  

  • [DH] doc/muxers.texi
  • [DH] libavformat/matroskaenc.c
  • [DH] tests/ref/fate/matroska-flac-extradata-update

• avformat/av1dec : Redo flushing of bsf

  14 novembre 2019, par Andreas Rheinhardt

  avformat/av1dec : Redo flushing of bsf
  The current approach has two different calls to av_bsf_send_packet() :
  
  A normal one, sending a packet ; and an extraordinary one just for
  
  flushing. These can be unified into one by making use of the newly
  
  documented fact that av_bsf_send_packet() allows to signal flushing via
  
  empty packets (i.e. packets without data and side-data).
  This also fixes CID 1455685 which resulted from the fact that the call
  
  for flushing was not checked given that it couldn't fail.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  
  Signed-off-by : James Almer <jamrial@gmail.com>
  

  • [DH] libavformat/av1dec.c

• avformat/matroskadec : Redo level handling

  24 juin 2019, par Andreas Rheinhardt

  avformat/matroskadec : Redo level handling
  This commit changes how levels are handled : If the level used for
  
  ebml_parse ends directly after an element that has been consumed, then
  
  ebml_parse ends the level itself (and any known-length levels that end
  
  there as well) and informs the caller via the return value ; if the
  
  current level is of unknown-length, then the level is ended as soon as
  
  an element that is not valid on the current level, but on a higher
  
  level is encountered (or if EOF has been encountered).
  This is designed for situations where one wants to parse master elements
  
  incrementally, i.e. not in one go via ebml_parse_nest.
  The (incremental) parsing of clusters still mixes levels by using a
  
  syntax list that contains elements from different levels and the level
  
  is still ended manually via a call to ebml_level_end if the last cluster
  
  was an unknown-length cluster (known-length clusters are already ended
  
  when their last element is read), but only if the next element is a
  
  cluster, too. A  different level 1 element following an unknown-length
  
  cluster will currently simply be presumed to be part of the earlier
  
  cluster. Fixing this will be done in a future patch. The modifications
  
  to matroska_parse_cluster contained in this patch are only intended not
  
  to cause regressions.
  Nevertheless, the fact that known-length levels are automatically ended
  
  in ebml_parse when their last element has been read already fixes a bogus
  
  error message introduced in 9326117b that was emitted when a known-length
  
  cluster is followed by another level 1 element other than a cluster in
  
  which case the cluster's level was not ended (which only happened when
  
  a new cluster has been encountered) so that the length check (introduced
  
  in 9326117b) failed for the level 1 element as it is of course not
  
  contained in the previous cluster. Most Matroska files were affected by
  
  this.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  

  • [DH] libavformat/matroskadec.c