www.makemkv.com

Integration in VLC seems to be broken now. Every time I try to play a Blu-ray, as soon as I hit "Play" on the "Open Disc..." dialog, VLC simply closes itself. I get a message next time I start it saying it crashed on its last run. If I disable integration and use AnyDVD, the disc...

Just tried it again and it worked fine, so...no idea?

This is the first disc I've tried in a while, but I wasn't having any issues previously.

Does anyone know what's going on here?

I was under the impression it did both, but I keep getting "region mismatch" messages in VLC.

I think you've put in the Special Features disc, not the Movie disc.

The default selection rules for audio are to extract the "highest quality" audio first. Often, that is NOT the film audio. Many disks are authored with stereo for the main audio, but 5.1 audio for supplemental streams, including commentary and descriptive audio. I have never seen a 5.1 co...

Tried ripping one and I just get "DEBUG: Code 1 at /_9g.,hTu)"3p;YDd3Xnw:121262371" constantly and nothing happens.

Three at 20.6 GB, one at 20.8 GB. Only one has chapters, but they all have completely different segment mappings. Anyone have any insight?

982C here.

I'm familiar with it, but I'd never studied that section before so I didn't realise it had that info.

Unfortunately I've obviously remuxed a couple of my 3D films because it lists mkvmerge there instead of MakeMKV. But that narrows it down at least.

So how do I know which of my files are affected? I have a lot of 3D movies, a few of which were likely ripped with 1.15.2, but also a few which probably weren't. Is there a way to tell which is which?

When trying to do anything in FFMPEG with my MKV rips, it gives me the error "Timestamps are unset in stream 0", followed by "pts has no value" repeatedly. I don't think I've ever seen this before so I'm guessing it's only an issue with the most recent version, because I've tried...

So I've tried the BD3D2MK3D thing, but it throws an error saying it's unable to open the qpfile when it tries to do the encoding.

Has this been resolved in 1.15.3? No mention of it in the update notes.