Using MakeMVS 1.6.5 on Snow Leopard 10.6.2

The place to discuss Mac OS X version of MakeMKV
Post Reply
Zenbillionaire
Posts: 1
Joined: Sun Mar 06, 2011 4:11 am

Using MakeMVS 1.6.5 on Snow Leopard 10.6.2

Post by Zenbillionaire »

1.8 Ghz Intel Core 2 Duo
MacOS 10.6.2
MakeMVS 1.6.5
DASPI 1.2

------

I've tried MakeMVS 4 or 5 times in the past few days with no success and some puzzling output I could use advice on. I'm using an external Buffalo BD-ROM drive according to the Drive Information displayed by MakeMVS, which shows the manufacturer code to be HL-DT-ST, revision EL00, firmware date 2010-04-05 12:34:56. The drive is described as a "Buffalo 8x EXTERNAL USB BLU-RAY WRITER - BUBRX816U2" by the vendor.

The program never seems to recognize the DASPI kernel extension. Each time I start it I see:

MakeMKV v1.6.5 darwin(x86-release) started?Optical drive "DVD-ROM MATSHITA CD-RW CW 8124 DACK" opened in OS access mode.?It's highly recommended to install DASPI kernel extension to improve performance.?Optical drive "BD-RE HL-DT-ST BD-RE BH10NS30 EL00" opened in OS access mode.?

I assume from the above that the part saying "opened in OS access mode.? It's highly recommended to install DASPI kernel extension to improve performance" means it isn't recognizing that DASPI has been installed? Why would this be?

% find /System/Library -name "daspi*" -print
/System/Library/Extensions/daspi.kext
/System/Library/Extensions/daspi.kext/Contents/MacOS/daspi


When I try using the Backup function I receive the following error:

Backing up disc into folder "/Volumes/Users/Movies/backup/RED_BIRD_2D_WW"
Evaluation version, 29 day(s) out of 30 remaining
Hit OS X IOSCSIMultimediaCommands bug, used type 2 workaround, see http://www.makemkv.com/osxbd/ for details.
Automatic SVQ downloading is disabled or failed.
Loaded 14 SVQ file(s)
Processing BD+ code, please be patient - this may take up to few minutes
Processing BD+ code using generic SVQ from builtin/00002.svq
BD+ code processed, got 1 FUT(s) for 1 clip(s)
Loaded content hash table, will verify integrity of M2TS files.
Hash check failed for file /BDMV/STREAM/00002.m2ts at offset 23404996608, file is corrupt.
Hash check failed for file /BDMV/STREAM/00002.m2ts at offset 23461423104, file is corrupt.
Hash check failed for file /BDMV/STREAM/00002.m2ts at offset 23461619712, file is corrupt.
Hash check failed for file /BDMV/STREAM/00002.m2ts at offset 23647807488, file is corrupt.
Hash check failed for file /BDMV/STREAM/00002.m2ts at offset 23648004096, file is corrupt.
Too many hash check errors in file /BDMV/STREAM/00002.m2ts.
Error 'Posix error - Input/output error' occurred while reading '/BDMV/STREAM/00002.m2ts' at offset '24145053696'
Backup failed


The disk I'm trying it on is a copy of Avatar. I'd planned to use the streaming feature to play the disk on a display attached to the Mini but I can't get the Stream button to light up. Someone mentioned using the Backup function first to get the program to read hte disk and enable streaming, but that doesn't seem to do the trick either. Any suggestions?
mike admin
Posts: 4075
Joined: Wed Nov 26, 2008 2:26 am
Contact:

Re: Using MakeMVS 1.6.5 on Snow Leopard 10.6.2

Post by mike admin »

Zenbillionaire wrote:1.8 Ghz Intel Core 2 Duo
MacOS 10.6.2
MakeMVS 1.6.5
DASPI 1.2

------

I've tried MakeMVS 4 or 5 times in the past few days with no success and some puzzling output I could use advice on. I'm using an external Buffalo BD-ROM drive according to the Drive Information displayed by MakeMVS, which shows the manufacturer code to be HL-DT-ST, revision EL00, firmware date 2010-04-05 12:34:56. The drive is described as a "Buffalo 8x EXTERNAL USB BLU-RAY WRITER - BUBRX816U2" by the vendor.

The program never seems to recognize the DASPI kernel extension. Each time I start it I see:

MakeMKV v1.6.5 darwin(x86-release) started?Optical drive "DVD-ROM MATSHITA CD-RW CW 8124 DACK" opened in OS access mode.?It's highly recommended to install DASPI kernel extension to improve performance.?Optical drive "BD-RE HL-DT-ST BD-RE BH10NS30 EL00" opened in OS access mode.?

I assume from the above that the part saying "opened in OS access mode.? It's highly recommended to install DASPI kernel extension to improve performance" means it isn't recognizing that DASPI has been installed? Why would this be?

% find /System/Library -name "daspi*" -print
/System/Library/Extensions/daspi.kext
/System/Library/Extensions/daspi.kext/Contents/MacOS/daspi


When I try using the Backup function I receive the following error:

Backing up disc into folder "/Volumes/Users/Movies/backup/RED_BIRD_2D_WW"
Evaluation version, 29 day(s) out of 30 remaining
Hit OS X IOSCSIMultimediaCommands bug, used type 2 workaround, see http://www.makemkv.com/osxbd/ for details.
Automatic SVQ downloading is disabled or failed.
Loaded 14 SVQ file(s)
Processing BD+ code, please be patient - this may take up to few minutes
Processing BD+ code using generic SVQ from builtin/00002.svq
BD+ code processed, got 1 FUT(s) for 1 clip(s)
Loaded content hash table, will verify integrity of M2TS files.
Hash check failed for file /BDMV/STREAM/00002.m2ts at offset 23404996608, file is corrupt.
Hash check failed for file /BDMV/STREAM/00002.m2ts at offset 23461423104, file is corrupt.
Hash check failed for file /BDMV/STREAM/00002.m2ts at offset 23461619712, file is corrupt.
Hash check failed for file /BDMV/STREAM/00002.m2ts at offset 23647807488, file is corrupt.
Hash check failed for file /BDMV/STREAM/00002.m2ts at offset 23648004096, file is corrupt.
Too many hash check errors in file /BDMV/STREAM/00002.m2ts.
Error 'Posix error - Input/output error' occurred while reading '/BDMV/STREAM/00002.m2ts' at offset '24145053696'
Backup failed


The disk I'm trying it on is a copy of Avatar. I'd planned to use the streaming feature to play the disk on a display attached to the Mini but I can't get the Stream button to light up. Someone mentioned using the Backup function first to get the program to read hte disk and enable streaming, but that doesn't seem to do the trick either. Any suggestions?

You have two separate problems. First, DASPI is not recognized - that's strange but it's not a main problem. The second, the failed hashcheck indicates either a bad disc or drive, there is no other explanation.
Post Reply