Page MenuHomeSolus

Update libmediainfo to 0.7.97
ClosedPublic

Authored by kyrios123 on Jun 30 2017, 9:26 PM.
Referenced Files
F11046907: D534.diff
Thu, Aug 10, 2:26 PM
F10986680: D534.diff
Mon, Jul 24, 2:18 AM
F10926170: D534.id1152.diff
Jul 10 2023, 11:04 AM
F10875787: D534.id1230.diff
Jun 20 2023, 7:29 AM
F10875784: D534.diff
Jun 20 2023, 7:28 AM
F10816841: D534.id1152.diff
Jun 1 2023, 4:10 AM
F10805547: D534.diff
May 29 2023, 8:55 PM
F10692368: D534.id.diff
Apr 24 2023, 9:47 AM
Subscribers

Details

Summary

Features:

  • HEVC: support of stream having VPS hrd_parameters
  • FLV: support of FLV files with an ID3v2 header
  • FLV: detect some incoherent frame rates in buggy files
  • TIFF: support of more tags
  • I518, AAC: consider 4 back channels as 2 side + 2 back channels
  • Matroska: integrate all elements from Matroska specs in MediaTrace
  • WAV: parsing of MPEG Audio extension "mext" chunk and displayed in MediaTrace
  • MPC: channels count
  • AAC: ADTS/ADIF duration in case of full parsing and/or "risky bitrate estimation" option

Bugfixes:

  • MXF: less false-positive detection of some files as MXF
  • B1053, WAV: metadata coherency, ignore "fact" chunk more often in order to avoid bad information when this chunk is buggy
  • B1029, DPX: DPX endianess not considered with some fields in MediaTrace
  • Custom template: can check "Other" part as any other parts
  • Matroska: fix parsing issue with small byte blocks are taken from the file e.g. when reading from HTTP link
  • Matroska: files with unknown block size were flagged as truncated
  • MediaTrace: values with a \n were breaking the text report lines
  • Some typos (RefFrames, SPF)

Depends on D533

Signed-off-by: Pierre-Yves <pyu@riseup.net>

Diff Detail

Repository
R1772 libmediainfo
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Looks like many things are gone in the abi_symbols. Should I worry about it ?

This revision is now accepted and ready to land.Jul 9 2017, 8:49 AM
This revision was automatically updated to reflect the committed changes.

Looks like many things are gone in the abi_symbols. Should I worry about it ?

This means it break the ABI with libraries it's built against. i.e. anything that is using those symbols will no longer function. Negatives in abi_symbols usually mean rebuilding all packages it's built against for safety, as they may no longer function (if they didn't use those symbols however, they would work fine).