www.makemkv.com

Hi,

All of a sudden, I have started getting the dreaded 'Can't read AACS VID from disc - most likely current AACS host certificate is revoked by your drive' errors. This has never happened before - I have probably ripped over 150 BD disks with MakeMKV on the same system/drive prior to today.

I just installed DASPI v1.2 to see if it makes any difference, and it didn't. This happened with the 2 BD disks I just tried - Social Network and Fish Tank.

I am attached the entire debug file from 'Social Network' rip attempt. I have the latest MakeMKV v1.6.5, MacOS 10.6.6, and my drive is HP external BD/DVD model CA21N.

Help!!!

hitekalex wrote:Hi,

All of a sudden, I have started getting the dreaded 'Can't read AACS VID from disc - most likely current AACS host certificate is revoked by your drive' errors. This has never happened before - I have probably ripped over 150 BD disks with MakeMKV on the same system/drive prior to today.

I just installed DASPI v1.2 to see if it makes any difference, and it didn't. This happened with the 2 BD disks I just tried - Social Network and Fish Tank.

I am attached the entire debug file from 'Social Network' rip attempt. I have the latest MakeMKV v1.6.5, MacOS 10.6.6, and my drive is HP external BD/DVD model CA21N.

Help!!!

External USB drive on JMicron chipset? A workaround will be added in a next version.

mike admin wrote: External USB drive on JMicron chipset? A workaround will be added in a next version.

Yep, it is an external USB drive, and System Profiler shows JMicron chipset. I am hoping the fixed version is out soon. I wish I could go back to 1.6.4, where everything worked.. but downgrades seem to be impossible with the key licensing..

hitekalex wrote:

mike admin wrote: External USB drive on JMicron chipset? A workaround will be added in a next version.

Yep, it is an external USB drive, and System Profiler shows JMicron chipset. I am hoping the fixed version is out soon. I wish I could go back to 1.6.4, where everything worked.. but downgrades seem to be impossible with the key licensing..

You can always install multiple MakeMKV versions side by side - just rename MakeMKV.app to MakeMKV-1-6-4.app or something similar. However that's probably not what you want - JMicron chipset randomly corrupts data . It's just this time corruption was obvious. It took a great deal of effort to figure out what was the problem and to develop a workaround for MakeMKV. The next version should be available very soon.

mike admin wrote:You can always install multiple MakeMKV versions side by side - just rename MakeMKV.app to MakeMKV-1-6-4.app or something similar. However that's probably not what you want - JMicron chipset randomly corrupts data . It's just this time corruption was obvious. It took a great deal of effort to figure out what was the problem and to develop a workaround for MakeMKV. The next version should be available very soon.

Just tried v1.6.4 - same error.. at least with the same 2 BD disks I have tried

I am just trying to understand what is causing this to happen all of a sudden.. As I mentioned - I have been happily ripping BD disks for ages, using the same drive w/ JMicron chipset. Did my drive suddenly "go bad", or is this attributable to the way recent MakeMKV version interact with JMicron-based drives?

In any case, looking forward to a fix.

Did it work after 1.6.6 ?

mike admin wrote:Did it work after 1.6.6 ?

I no longer have the two BD disks that were having the original problem.. But trying 1.6.6 with 4 other BD titles - everything seems to be fine.

I will post here if I run into this issue again.

Thanks!

I just got this error for the first time. I bought a second drive since I have a LOT to rip. Both drives are LG, but this second drive is throwing this same error. "AACS host certificate is revoked by your drive"

Drive model number is UH12LS28 by LG

I remember makemkv suggesting a website that has alternate firmware downloads for drives. Anti DRM, etc. Does anybody have that link? I want to check and see if by chance they have firmware for this drive.

EDIT:
I'm sorry I didnt realize this was the OSX forum. My drive is installed on a windows 7 box.

This dreaded error is back, since I upgraded to Lion. At least on one of my disks - "Rubber" BD-DVD. The other disk I just tried ("Inside Job) ripped fine.

I have attached the debug log. Any ideas? Is this the same issue as I before?

Bump... Any advice on this? Do I really need to sell my drive and get a different one?

hitekalex wrote:Bump... Any advice on this? Do I really need to sell my drive and get a different one?

Since the problem originated when you upgraded to lion, have you tried downgrading? Perhaps create a VM in VMWare Fusion with 10.6.8 installed and see if it still works. If it does, you'll have to decide if upgrading to lion is really all that worth it (in my opinion it isn't... I go by the "if it aint broke dont fix it" line of thinking).

However, if you do decide to stick it out with Lion, trust me the developers are constantly working on the code, so you'll just have to stick it out and wait for a new patch (could be months... maybe longer, maybe less).

chianti wrote:

hitekalex wrote:Bump... Any advice on this? Do I really need to sell my drive and get a different one?

Since the problem originated when you upgraded to lion, have you tried downgrading? Perhaps create a VM in VMWare Fusion with 10.6.8 installed and see if it still works. If it does, you'll have to decide if upgrading to lion is really all that worth it (in my opinion it isn't... I go by the "if it aint broke dont fix it" line of thinking).

However, if you do decide to stick it out with Lion, trust me the developers are constantly working on the code, so you'll just have to stick it out and wait for a new patch (could be months... maybe longer, maybe less).

The problem did NOT originate with Lion. If you read this entire thread - I (and many others) have been having this issue long before Lion. In fact, I am 100% certain this is NOT Lion related. The reason for my certainty is that I just tried ripping the same BD disk using latest MakeMKV and the same drive on my Windows laptop, and I am getting exactly the same error. After that, I have tried ripping this very BD disk on my Lion machine, but this time using different BD drive (Panasonic UJ-240, borrowed from a friend) - the disk rips fine!

So, the issue is clearly with MakeMKV and certain types of BD drives PLUS certain BD disks. I am having this issue with only 25% of the BD disks, the rest rip fine.

I would really like to hear from the MakeMKV developers on this issue.

hitekalex wrote:

chianti wrote:

hitekalex wrote:Bump... Any advice on this? Do I really need to sell my drive and get a different one?

Since the problem originated when you upgraded to lion, have you tried downgrading? Perhaps create a VM in VMWare Fusion with 10.6.8 installed and see if it still works. If it does, you'll have to decide if upgrading to lion is really all that worth it (in my opinion it isn't... I go by the "if it aint broke dont fix it" line of thinking).

However, if you do decide to stick it out with Lion, trust me the developers are constantly working on the code, so you'll just have to stick it out and wait for a new patch (could be months... maybe longer, maybe less).

The problem did NOT originate with Lion. If you read this entire thread - I (and many others) have been having this issue long before Lion. In fact, I am 100% certain this is NOT Lion related. The reason for my certainty is that I just tried ripping the same BD disk using latest MakeMKV and the same drive on my Windows laptop, and I am getting exactly the same error. After that, I have tried ripping this very BD disk on my Lion machine, but this time using different BD drive (Panasonic UJ-240, borrowed from a friend) - the disk rips fine!

So, the issue is clearly with MakeMKV and certain types of BD drives PLUS certain BD disks. I am having this issue with only 25% of the BD disks, the rest rip fine.

I would really like to hear from the MakeMKV developers on this issue.

In that case I misread your post. I can assure you the developers are very aware of the issue. They sent me and another individual a proprietary program in order to give them very detailed diagnostic information they need to make any attempt to work around the issue. Obviously they haven't found a solution yet

Were you ever able to get this working? I'm having this exact issue and running Lion, but it was happening on SnowLeopard as well, so it doesn't sound like that is the issue. I have yet to be able to get makemkv to work with my drive.

This should be fixed in 1.6.13