FFe: Sync mediainfo 0.7.88-1 (universe) from Debian unstable (main)

[Chow Loong Jin]

Please sync mediainfo 0.7.88-1 (universe) from Debian unstable (main)

Explanation of FeatureFreeze exception:

Upstream wishes to deprecate versions before 0.7.88, as there were some bugs
fixed in between 0.7.85 and 0.7.88.

This should be done together with the libmediainfo sync at
https://bugs.launchpad.net/ubuntu/+source/libmediainfo/+bug/1619932

Changelog entries since current yakkety version 0.7.84-1:

mediainfo (0.7.88-1) unstable; urgency=medium

  * [9ea5e69] Imported Upstream version 0.7.88

 -- Chow Loong Jin <email address hidden> Thu, 01 Sep 2016 23:35:20 +0800

mediainfo (0.7.87-1) unstable; urgency=medium

  * [fe58c72] Imported Upstream version 0.7.87

 -- Chow Loong Jin <email address hidden> Mon, 29 Aug 2016 01:10:15 +0800

mediainfo (0.7.85-1) unstable; urgency=medium

  * [55e5772] Imported Upstream version 0.7.85

 -- Chow Loong Jin <email address hidden> Thu, 16 Jun 2016 17:25:04 +0800

Upstream changelog entries since the current yakkety version 0.7.84-1:

Version 0.7.88, 2016-08-31
--------------
+ MediaInfo distributed with HTTP/HTTPS support: support of Amazon S3 with Signature Version 4
+ FFV1: parsing speed slight improvement
x Duration: fixed regression in last release, sometimes duration was displayed with only count of minutes

Version 0.7.87, 2016-06-30
--------------
+ Spanish and catalan languages updated, thanks to Sergi Medina
+ Refactoring of the trace feature, for better performance and some bug fixes
- Visual C++ 2012 project files removed
x Review of symbols display, now using standard display (e.g. "k" instead of "K", " min" instead of "mn"...)
x XML output: revert to old versioning method (version is MediaInfo software version)
x I63, EBUCore/FIMS outputs: typo correction about WritingLibrary and WritingApplication
x Matroska: files with CodecPrivate element before CodecID element where not always correctly parsed
x OGG: crash/incoherent behavior with some buggy OGG streams having invalid chunk sizes

Version 0.7.86, 2016-05-31
--------------
+ Linux/Mac: more output formats (PBCore, EBUCore, FIMS)
+ FFV1 parsing optimization, avoiding by default a too verbose trace
+ Matroska: more elements support and typo fixes in the trace
+ #I172, Trace feature: provide the name of the main parser in the media element
+ Matroska: consider all values below 0x10 EBML names as 1-byte junk
x Matroska: better support (including speed improvement) of huge lossless frames (e.g. 20 MB FFV1 4K)
x #I144, Python binding: Python 2 on Linux does not automatically provide the locale to the shared object
x HTML output: don't escape carriage returns from the input file
x FFV1: some streams were rejected despite the fact they are valid
x Python binding: some errors during call of Get() API with Python3 on Linux/Mac

Version 0.7.85, 2016-04-29
--------------
+ FFV1: ScanType and ScanOrder
+ Detection of Omneon VBI and move of the VBI track from Video part to Others part
+ N19/STL: Support of etection of less standard frame rates (23.976 and 29.970)
+ Teletext in MPEG-TS: Teletext not subtitle moved to "Other" part
+ Teletext in MPEG-TS: display of CodecID and timestamp of first frame
x Teletext in MXF: some IDs were wrong (when there are more than one Teletext service)
x MPEG-4/MOV: default of raw audio to Signed in case of stsd atom version <2
x MPEG Video: some CEA-608/708 captions were not correctly detected due to some packets discarded by the parser with interlaced content
x MPEG-4/MOV: Dolby E with 2 or more audio services were not correctly reported

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[elatllat (elatllat)]

The version of mediainfo (0.7.82) in Ubuntu (16.04.1) can't read Matroska data which is a regression from the previous Ubuntu LTS.

[Jérôme Martinez (j1-jerome)]

What do you mean "can't read Matroska"?
I am not aware on any regression about Matroska with any recent version of MediaInfo library, and we ourselves analyze tons of Matroska files with MediaInfo on Ubuntu.
Please provide more details (with a sample file).
Jérôme, main developer of MediaInfo.

[Jérôme Martinez (j1-jerome)]

> The version of mediainfo (0.7.82) in Ubuntu (16.04.1) can't read Matroska

Just tested with mediainfo 0.7.82 in Ubuntu 16.04 amd64 with this command:
mediainfo http://mediaarea.net/temp/a.mkv
and I have a good result (starting with "Format: Matroska") with this (temporary) online Matroska file.

Same result with mediainfo 0.7.85 in Ubuntu 16.10 beta.

Anyway, even if we have a regression somewhere syncing with current 0.7.88 would not add a regression (it would be there before and after the sync) and we need to fix this issue at the upstream level.

[elatllat (elatllat)]

The mediainfo change log indicate there were some Matroska fixes in more recent versions so getting the most resent version in ubuntu might fix it.
I'd have to look up how to make a sample to send...
I can't find compile instructions to verify it's a mediainfo regression and not a packaging one.
For now I'm using ffprobe which has the following output to compare:

> mediainfo --Version
MediaInfo Command line,
MediaInfoLib - v0.7.82

> ffprobe -version
ffprobe version 2.8.6-1ubuntu2 Copyright (c) 2007-2016 the FFmpeg developers
built with gcc 5.3.1 (Ubuntu/Linaro 5.3.1-11ubuntu1) 20160311
configuration: --prefix=/usr --extra-version=1ubuntu2 --build-suffix=-ffmpeg --toolchain=hardened --libdir=/usr/lib/arm-linux-gnueabihf --incdir=/usr/include/arm-linux-gnueabihf --cc=cc --cxx=g++ --enable-gpl --enable-shared --disable-stripping --disable-decoder=libopenjpeg --disable-decoder=libschroedinger --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-librtmp --enable-libschroedinger --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxvid --enable-libzvbi --enable-openal --enable-opengl --enable-x11grab --enable-libdc1394 --enable-libiec61883 --enable-libzmq --enable-frei0r --enable-libx264 --enable-libopencv
libavutil 54. 31.100 / 54. 31.100
libavcodec 56. 60.100 / 56. 60.100
libavformat 56. 40.101 / 56. 40.101
libavdevice 56. 4.100 / 56. 4.100
libavfilter 5. 40.101 / 5. 40.101
libavresample 2. 1. 0 / 2. 1. 0
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 2.101 / 1. 2.101
libpostproc 53. 3.100 / 53. 3.100

> mediainfo $F

> ffprobe "$F" 2>&1 | perl -pe 's/from .*://g'
ffprobe version 2.8.6-1ubuntu2 Copyright (c) 2007-2016 the FFmpeg developers
  built with gcc 5.3.1 (Ubuntu/Linaro 5.3.1-11ubuntu1) 20160311
  configuration: --prefix=/usr --extra-version=1ubuntu2 --build-suffix=-ffmpeg --toolchain=hardened --libdir=/usr/lib/arm-linux-gnueabihf --incdir=/usr/include/arm-linux-gnueabihf --cc=cc --cxx=g++ --enable-gpl --enable-shared --disable-stripping --disable-decoder=libopenjpeg --disable-decoder=libschroedinger --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-librtmp --enable-libschroedinger --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --e...

[Jérôme Martinez (j1-jerome)]

@elatllat:

First you don't test with the command line you provided so it is not possible to know if your issue is related to Matroska; you also don't provide the content of $F; when the output is empty, this usually means that the file is not accessible by MediaInfo, not related to Matroska.

Second this issue is not related to this ticket (again: before or after this ticket is handled, it changes nothing), so it is complicated to manage it. If you want your issue, not related to this ticket, to be resolved, please open a new ticket dedicated to this issue on Launchpad or on the upstream tracker https://github.com/MediaArea/MediaInfoLib/issues because I think that it is not related to how it is packaged in Ubuntu (if you want to be sure that the issue is from upstream, you can test https://mediaarea.net/MediaInfo/Download/Ubuntu packages)
Here, you pollute a ticket with something not related to it and it prevents both issues (the reason of the ticket + your issue) to be resolved.

[Chow Loong Jin (hyperair)]

At the risk of polluting this bug report further:

On Sun, Sep 04, 2016 at 11:01:12PM -0000, elatllat wrote:
>
> > mediainfo $F

No quotes around $F

> > ffprobe "$F" 2>&1 | perl -pe 's/from .*://g'

Quotes around $F

I don't know if this is really the issue, but this is something I noticed after
Jerome said that mediainfo might not have been able to access the file.

--
Kind regards,
Loong Jin

[elatllat (elatllat)]

> First you don't test with the command line you provided...
As already mentioned there are no build instructions for mediainfo so I can't test properly (with git bisect)

> so it is not possible to know if your issue is related to Matroska; you also don't provide the content of $F; when the output is empty, this usually means that the file is not accessible by MediaInfo, not related to Matroska.
As already shown with the ffprobe example, every other application thinks the file is a valid matroska.

> Second this issue is not related to this ticket (again: before or after this ticket is handled, it changes nothing)
As already stated the mediainfo change log leads me to believe otherwise; upstream might fix it.

>, so it is complicated to manage it. If you want your issue, not related to this ticket, to be resolved, please open a new ticket dedicated to this issue on Launchpad or on the upstream tracker https://github.com/MediaArea/MediaInfoLib/issues because I think that it is not related to how it is packaged in Ubuntu (if you want to be sure that the issue is from upstream, you can test https://mediaarea.net/MediaInfo/Download/Ubuntu packages)
That link dose not have builds for the architecture I'm using.

>No quotes around $F
That is not the issue though it brings up 2 mediainfo shortcomings: the exit code is 1 if it's given a bad path or a file it can't decode when it should be using more than one exit code. And all non-zero exits should really have a text error message on stderr.

> Here, you pollute a ticket with something not related to it and it prevents both issues (the reason of the ticket + your issue) to be resolved.
Sorry I thought I was adding reasons for Ubutnu to sync with upstream. I'll stop polluting your ticket.

[Iain Lane (laney)]

Feel free to sync.

[Chow Loong Jin (hyperair)]

This bug was fixed in the package mediainfo - 0.7.88-1

---------------
mediainfo (0.7.88-1) unstable; urgency=medium

  * [9ea5e69] Imported Upstream version 0.7.88

 -- Chow Loong Jin <email address hidden> Thu, 01 Sep 2016 23:35:20 +0800

mediainfo (0.7.87-1) unstable; urgency=medium

  * [fe58c72] Imported Upstream version 0.7.87

 -- Chow Loong Jin <email address hidden> Mon, 29 Aug 2016 01:10:15 +0800

mediainfo (0.7.85-1) unstable; urgency=medium

  * [55e5772] Imported Upstream version 0.7.85

 -- Chow Loong Jin <email address hidden> Thu, 16 Jun 2016 17:25:04 +0800