ffmpeg 2.0.2 vs. 2.1 extracting audio&video from mpls, problem

[Selur]

I normally use:

ffmpeg -y -threads 8 -playlist 2 -i  bluray:"H:/TestClips&Co/BluRay/BD_Demo/x264 BR-Demo" -vcodec copy  -map_metadata -1 -metadata handler_name="Hybrid 2013.11.1.1" -vbsf  h264_mp4toannexb -f h264 "H:\Output\Blu-ray_13_40_40_1410_02.264"  -acodec copy  -map_metadata -1 -metadata handler_name="Hybrid  2013.11.1.1" "H:\Output\iId_1_aid_4352_lang_eng_13_40_40_1410_01.dts"

to extract a dts-hd-ma and a mpeg-4 avc video stream.

With ffmpeg version <= 2.0.2 (32bit, 64bit) this works fine, problem is that if I use any newer ffmpeg version I get:
a. tons of warnings and error during the extraction
b. the output streams are broken

all newer versions output tons of:

[dca @ 04928ba0] Not a valid DCA frame
[h264 @ 049282e0] non-existing PPS referenced
[h264 @ 049282e0] non-existing PPS 0 referenced
[h264 @ 049282e0] decode_slice_header error
[h264 @ 049282e0] non-existing PPS 0 referenced
[h264 @ 049282e0] decode_slice_header error
[h264 @ 049282e0] non-existing PPS 0 referenced
[h264 @ 049282e0] decode_slice_header error
[h264 @ 049282e0] non-existing PPS 0 referenced
[h264 @ 049282e0] decode_slice_header error
[h264 @ 049282e0] no frame!

and

[NULL @ 05351020] Packet header is not contained in global extradata, corrupted stream or invalid MP4/AVCC bitstream
Failed to open bitstream filter h264_mp4toannexb for stream 0 with codec copy: Invalid argument

I also compiled latest ffmpeg with libbluray 0.2.3 to check if this is a libbluray issue -> it is not, same problem happens with older libbluray versions.

-> Did I miss something?
Do I have to use some special flags/option to extract the audio and video with latest ffmpeg builds from mpls input or is every ffmpeg version after 2.0.2 simply broken in this regard?

---

I really would like to switch to ffmpeg 2.1 and newer due to the HEVC decoding support, but loosing Blu-ray handling would be harsh.


Cu Selur

Ps.: also posted in zeranoes forum.

[microchip8]

I think you should report this on the ffmpeg bug tracker

[Selur]

I did after I posted here.

[manolito]

@Selur
I noticed that you did not get an answer in the ffmpeg forum. Did you test if the issue was fixed in stable version 2.1.1 ?


Cheers
manolito

[Selur]

Yes, should be fixed. (unless someone broke it again)