v0.10.x: Multiple angles and wrong chapter marks

[nick24]

I already posted and described this a year ago: 'v10.2: Multiple angles and wrong chapter marks'
It seems that this problem has not been addressed yet, thus I raise it again.

I run HB (0.10.5) on Windows 10 64 bit now. Same problem as on Win 8.1 64 bit.
No change with current nightly build.

The activity log (with obvious wrong chapters) of current nightly build is here:
http://pastebin.com/LtHqSswZ

Due to this problem I'm still using HB 0.9.9 which handles multiple angles perfectly.

I like HB very much. Thanks in advance for your support.

[JohnAStebbins]

Can you be more specific about how they are wrong? Too many chapters? Too few? Wrong time? I'll dig out a multi-angle BD to try myself, but it might help to understand what it is that you are seeing.

[nick24]

Thanks for the quick reply.

The number of chapters is correct. But the order is somehow mixed up, e.g. in the log:
Chapter 1, Chapter 2, Chapter 1, Chapter 4, ...

The multi-angle part is at the beginning of the movie in this example.
With HB 0.9.9 the order is correct in the log.

[JohnAStebbins]

Well, that's unexpected Glad I asked what the symptoms were. I would have never looked for that particular behavior.

[JohnAStebbins]

I believe I've found the problem. The problem actually has nothing to do with mulit-angle. It is just more likely when the disc is multi-angle because multi-angle requires that the title also be multi-clip. It's the multiple clips that actually triggers the problem. 0.9.9 just happened to work because the libbluray chapter events were only triggered exactly on chapter boundaries. For some reason, they updated libbluray to trigger duplicate chapter events whenever a "mark" is reached. A mark is a more general object that includes chapter marks.

Anyway, I've sent a patch upstream to libbluray and will add a temporary patch to HandBrake until libbluray creates a new release with the fix.

[nick24]

Thank you very much for the investigation and for addressing the issue. I will check the Trac Timeline. Once I see a related fix I will check the nightly build.