Possible new bug, 1.9.8 - Dvd disc loading

[Krawk]

Have had this happen to me tonight, possibly a new bug that I have never seen before.
Would this have happened on previous versions? Is it a random glitch never to be repeated? Is this a new glitch present in the newest version?

After ripping several dvds, I loaded the dvd title Hostel (2006 Unrated) - yeah I know, crappy movie, anyway, MakeMKV showed the animation of the disc tray closing and then the disc spinning and the little blinky light. The drive itself reported the disc ready after a few seconds (and the drive light went out to indicate it) but in the program it still showed the light blinking and disc spinning. After a couple of minutes I ejected the disc, the program was still stuck on the spinning disc blinking light animation and even with the tray open it still showed the disc loading animation. I closed the tray again, a few seconds later the drive reports it is loaded but the program still shows the loading animation.

At this point I ejected the disc, closed the program, reloaded the program, closed the tray and it accepted this disc like it normally would, within a few seconds.
One thing to note about the disc - After the disc as "loaded" and I click the analyze disc button, the program reports the IFO is corrupt and the disc needs to be scanned. I think the corrupt IFO is simply part of the protection on the disc.

Drive is a Sata ASUS DRW-21B1st Ver. c1.05
Windows 7/64 SP1
Have successfully ripped hundreds of discs on this drive.
Drive has done several more rips while I am typing this message.

[Woodstock]

First guess would be that the drive is in a "confused" state, according to Windows.

I'd stop MakeMKV (with the task manager if necessary!), then try to take a directory of the disk in Explorer. If you can read the disk through Explorer, try starting MakeMKV again.

If it can't be read with explorer, it is likely that you need to reset the machine to get the drive to behave. While USB drives can usually be "made right" by unplugging them, internal SATA drives aren't so easy to do that with.

[Krawk]

It just happened again. This time with Air Force One.


This time I followed your suggestion but follow what I did.

MakeMKV is still in the animation mode of where it's got the disc spinning while it is awaiting the disc to load.
Next, I tried Windows Explorer. Directories and such are accessible.
Next, I load VLC and hit Control-D, it opens the disc and goes right to the disc menu.

Per your suggestion, I just killed the program with task manager, as opposed to closing the program like I had done the first time in my first post.
Disc is still accessible in Windows.
Restarting MakeMKV though after killing the task instead of just closing it, it is stuck "scanning cd rom devices" - It is stuck on CdRom0
So killing the program instead of closing it has locked it out of both optical drives. I suspect a reboot or logoff/logon is in order to restore the drives to the program.

The drives are still accessible in Windows.

While I did kill the program in task manager, there are still processes running, which might explain the program's inability to reset.
makemkvcon64.exe is the task, x 3

I would attach a screenshot of task manager but apparently even a 26k file is too big!

[Edit] Trying to force stop those 3 makemkv processes is unsuccessful, they continue to run. Yes I am in Administrator Mode.

[Edit 2] - Ok, force stopping the 3 tasks "appears" to be non-productive, but closing task manager and restarting it shows the tasks gone, and MakeMKV is once again able to detect the drives without a Windows restart/logon.

Back to the drawing board, but I would honestly say that this happening twice now is more than coincidence. FWIW - I ripped about 30 or so dvds before this happened today.

[Woodstock]

It has been a couple of years since I saw "detached" console tasks in MakeMKV; It used to be a problem with running updates, but that stopped happening around the end of the 1.7.x series.

Mike will have to review this in case it is a one-time issue, or if something changed that could bring them back.

[Krawk]

It has been a couple of years since I saw "detached" console tasks in MakeMKV; It used to be a problem with running updates, but that stopped happening around the end of the 1.7.x series.

Mike will have to review this in case it is a one-time issue, or if something changed that could bring them back.

It is happening now once again. It took about 25 previous rips before it happened.

Is there anything I can do while it is happening or do I have to turn on debug/log and use it normally, deleting the log every so often because it will get large?

This time I closed the program with the X and restarted it, but still no dice. The previously mentioned task is there twice, one of them using over 500MB of ram.
I tried killing the processes but they appear to be still there. Each time I load the program, one additional occurrence of the process appears, but taking 4Mb. Not sure what the 500Mb is exactly.

You mention detached consoles - there is a conhost.exe running as well. Related?

[Edit] - so after unsuccessfully killing the processes, 15 minutes later I notice they're gone. Windows having trouble killing them or are they timing out on their own?

[Woodstock]

conhost.exe windows are normal in Windows, and unrelated to MakeMKV... I have a couple of them showing on my system right now, with no instances of MakeMKV running.

As for Windows not being able to close the makemkv* instances immediately, that is unusual.

[mike admin]

The drive itself reported the disc ready after a few seconds (and the drive light went out to indicate it) but in the program it still showed the light blinking and disc spinning.

This essentially means that the program still waiting some data from the disc. Appears to be a some sort of communication failure between the program and drive. What exactly is at fault - I don't know. Would blame the drive at first

[Krawk]

Thanks mike for your input. And yes it is easy to blame the drive. But when all other aspects of accessing the disc work 100%, such as browsing the disc via windows explorer or loading the movie into VLC or Windvd, it makes me question the validity of assuming the drive is to blame.