www.makemkv.com

Sounds like the famous Chemical Haze Issue™ again, then.

So far I've never really needed to use soap or anything like Dawn to clean a disc, but I did come across discs with such a bad haze that they needed around 4 or so cleaning attempts with a wet microfiber cloth before they could be read.

Probably the same problem as seen in https://forum.makemkv.com/forum/viewtopic.php?t=42238

TL;DR patch it yourself or wait until there's an update (hopefully there will still be one...)


And now there are more detailed instructions for using the patch inside that topic, too (for those who are ...

I have not yet attempted to rip a disc from my Arch distrobox after patching, but I have to thank you for this. After updating to ffmpeg 9 and using your patch, I was able to launch MakeMKV with no issues.

For anyone who's wondering, this is what I did on my Arch distrobox on my Ubuntu LTS-based ...

BTW, the biggest challenge I faced trying to restore stock firmware was actually finding the download pack, as it's hosted on the nonfunctioning makemkv.com. I eventually found it in the Wayback Machine

An MK firmware pack download link has been added to this topic : https://forum.makemkv.com ...

Added MK firmware pack download link. Thanks to goestoeleven for pointing out that this firmware pack is normally hosted on the main website, and was therefore inaccessible with normal means.

I don't think LG ever released a flasher tool for BP55EB40 SVC NB52.

Despite combing the web for it, I was never able to find one.

Also, here's the BU40N CB05 firmware I posted in another thread (official LG Updater exe) :

https://mega.nz/file/W7QUTYrA#O1kfVyabL ... jC9ULfSWl4

PM sent.

Your issue is also a known issue for some people who try to rip some UHD discs : https://forum.makemkv.com/forum/viewtopic.php?f=12&t=20853

I agree with tomty89's advice about the amount of power, it can get rid of the issue most of the time, but some discs are just nasty enough that you may also ...

Looks like it, from the number of supported firmwares. The original dates for the posts (2020 for the list I linked to VS 2019 for the list you linked to) were what threw me off track. Thanks.

Also, since the website appears to be down, where can I look on the forums to make sure that my version stays up to date?


Here : https://forum.makemkv.com/forum/viewtopic.php?t=42158

And if you just want the link to the latest version for your operating system : https://mega.nz/file/ziggWLhY ...

GET CONFIGURATION with RT=00 succeeds. GET CONFIGURATION with RT=02 fails, which is the command MakeMKV issues during drive probing.


Actually, if you are aware of that, do you also have access to the exact command that gets sent, perchance ? The Command Descriptor Block should be 10 bytes long ...

2009 date on bottom of both

Some drafts of MMC-2 go all the way back to the year 1999 and MMC-2 had already implemented GET CONFIGURATION and that particular RT value. I would be very surprised if this drive wasn't supposed to be MMC-2 compliant, not to mention that as long as the drive ...

Hmm, apparently this RT value was implemented a very long time ago, it was already there in MMC-2. So no idea why it's failing.

GET CONFIGURATION with RT=02 fails, which is the command MakeMKV issues during drive probing.

So basically, "The Feature Header and the Feature Descriptor identified by the Starting Feature Number shall be returned", yes ? Odd. I will do some additional research, but right now I find it odd that ...

how do i automate this?

I believe this depends on your distro really, but theoretically
Should do the trick on most distros. Reboot afterwards, and voila.