www.makemkv.com

I'm seeing very inconsistent behavior with this bug. In most cases, it remembers the folder it ripped to the previous time, but I'm pretty sure that I've seen it remember the parent folder of the folder that was ripped to the previous time, and just now, it went to the base folder that's in preferen...

Okay. I'm very confused now. I originally reported this with 1.7.4, and the log I provided does say 1.7.4, so it's not just that I wrote down the wrong version number. However, currently, if I use 1.7.4, it works with every disc that I've tried which had this problem, and it fails with 1.7.5, which ...

Ah, I can get 1.6.8 to work if I keep my current .MakeMKV directory around (I'd moved it on the theory that newer settings in it might screw up 1.6.8, but it seems to work if I leave it). And the Tenchi disc rips to mkv just fine with 1.6.8 in spite of failing miserably with 1.7.6 (though I have to ...

The Japanese Blu-ray release of Tenchi Muyo! seems to have the same problem (though the error messages aren't quite the same), and I could have sworn that I used makemkv to rip it previously, so I think that something broke at some point rather than this never working. Unfortunately, my attempt at u...

I just tried the second disc in the set, and it exhibits the same behavior, so clearly there's something about how these discs were authored which makemkv doesn't like.

I tried ripping the first Blu-ray disc of Read or Die, and it fails miserably. It's insanely slow, never completes, and spits out tons of DBG_ASSERT messages. Eventually, it seems to eat up 100% CPU and freeze. I have no idea if it ever finishes. Certainly it doesn't after several hours of trying. I...

Okay. I can confirm that if I symlink aacsv31-keys.txt into the current working directory before starting makemkv from the command line, makemkv is able to open all 6 of the discs in the file.

If you start MakeMKV, insert one of these discs, is there a line named "bus encryption flags" on the right pane, under disc information? No. The only fields that show up under disc information are Data capacity Disc type Number of layers Channel bit length It's the same for all of the dis...

Okay then. So, if the MakeMKV data directory were "/home/username/.MakeMKV", then aacsv31-keys.txt is supposed to be put in there such that it's "/home/username/.MakeMKV/aacsv31-keys.txt", correct? And then without doing anything else whatsoever, makemkv should be able to decrypt...

DVDFab has been able to decrypt the AACS v31 discs that I have, whereas makemkv hasn't been able to yet. So, you can use DVDFab to rip the whole disc to an .ISO, and then use makemkv on that. That worked for me. It's essentially what I have to do anyway whenever I need to split titles along chapter ...

makemkv 1.7.2 can decrypt these Sentai Filmworks release just fine: Samurai Girls (2011-08-23) has AACS v24 Ef a Tale of Memories (2012-01-31) has AACS v28 Broken Blade (2012-02-21) has AACS v28 But it fails with these: Ef a Tale of Melodies (2012-03-20) has AACS v31 Dream Eater Merry (2012-03-27) h...

Well, it looks like both mkvpropedit and makemkv are working correctly. Rather, it's mediainfo and mencoder which aren't. They're unable to deal with header info which gets put at the end of the file. I don't know why this wasn't a problem before (maybe makemkv changed how it dealt with some of the ...

I don't know if this a problem with mkvpropedit or makemkv, but if I use mkvpropedit 4.8.0 to edit tracks in an mkv generated by makemkv 1.6.10, then the track information is stripped from the file.So, either mkvpropedit is broken, or makemkv is creating mkv files which are faulty in some manner and...

I don't have a detailed speed comparison between 1.6.3 and 1.6.4, but I have noticed that discs frequently are ripping at only .1x or .2x. At other times, it's ripping over 5x IIRC. So, it's definitely inconsistent, but overall, I'd say that it's definitely worse. I'm use 64-bit Arch Linux with a Ph...

There is no cdrom group on my box - though there is an optical group (I assume that it's the same, just taking into account that the drive reads more than CDs). In either case, running as root has the same results.