vovamagazine.blogg.se

1. MAKEMKV 1.9.9 KEY REDIT MOVIE
2. MAKEMKV 1.9.9 KEY REDIT WINDOWS 8.1
3. MAKEMKV 1.9.9 KEY REDIT CODE
4. MAKEMKV 1.9.9 KEY REDIT ISO

I also put the log of a DVD rip from the LG drive. I tried ripping a DVD from the drive, and that worked, but also gave the "DEBUG" message.Īttached are the 3 MakeMKV logs from the Bourne box, and an HB log for Bourne 1. I'm using an external LG BD drive with both USBs connected to ports on a Win8.1 machine. Perhaps it's drive related sometimes I start MakeMKV and if there is a BD in the drive, I get thousands of DEBUG messages, which causes me to reboot. I never received this message prior to upgrading to 1.9.8.

I have received this message with every rip since upgrading to 1.9.8. (I upgraded to 1.9.9 yesterday.) On line 6 of each of the posted logs, there is a "DEBUG" message. I upgraded from 1.9.4 to 1.9.8 during the first week of 2016. Win8.1 shows the drive has 5 region selections remaining. Tbh, though, I am thinking that the external LG drive is locked now. I can send a piece of it if that makes sense - as can be seen in the attached HB log, the errors occur in chapter 13.

MAKEMKV 1.9.9 KEY REDIT MOVIE

The DTS-HD MA audio track from Bourne 1 movie is 3+ gb.

MAKEMKV 1.9.9 KEY REDIT CODE

MakeMKV is a tool for ripping Blu-ray and DVDs.I get the "Overread auxiliary data by 32 bits" from the dca decoder code in Handbrake for the 3 BDs in the Bourne box purchased at BB. Remember to NOT change the containerport! This container is based on Hurricanes dockergui container with both RDP and WEB interface support.įill in the rdp and WEB interface ports you want in the Port section of the template. You can change the resolution in the Environment section to whatever you want. config is the folder where MakeMKV saves it's settings. Where you save this on unRaid is up to you, but it should be on a cache only share.

UnRaid is where you map the folder you want to save you MKVs. Remember to change to the /unRaid folder in the settings of MakeMKV as the default location of saving MKVs. If you forget this you will fill up your docker.img!īecause MakeMKV changed how drives are detected, you need to figure out which device nodes is your DVD/BD-ROM. disk ATA TOSHIBA HDWD130 ACF0 /dev/sdd /dev/sg4 disk ATA OCZ-TRION100 11.2 /dev/sdc /dev/sg2 disk ATA Samsung SSD 850 1B6Q /dev/sdb /dev/sg1 disk SanDisk Cruzer Fit 1.27 /dev/sda /dev/sg0 Use the below command and find your DVD/BD-ROM. cd/dvd ATAPI iHOS104 WL0G /dev/sr1 /dev/sg5Īfter finding your device, labeled cd/dvd in the second column, add the below to the extra parameters field. Substitute the * with the actual number of your drive from the above command. If you want to use this container you have to add the text below to the template repositories box on the Docker page or search for the container in Community Applications. If the container starts, you don't need to remove it, but I guess it will complain that it can't find /dev/sr0. There is absolutely no harm in removing it from the extra parameters if you don't have a optical drive. My container failed to build with the extra parameters in the config.

MAKEMKV 1.9.9 KEY REDIT ISO

However, I tried using the program, and after getting it all set up/configured, and started it on extracting an MKV from an iso file, as soon as I confirmed I wanted it to create the directory into which it would save the file, my windows VM crashed, and the mkv file never actually started extracting. Sadly, it seems it's still not quite working right it eventually failed in the makemkv docker also. How is your setup of the VM and the docker? Volume mappings and such.

MAKEMKV 1.9.9 KEY REDIT WINDOWS 8.1

I have had no problem using MakeMKV while using my Windows 8.1 VM on my "desktop" unraid. I tried to use an ISO as source and no problems here.Ĭould it be you are running out of memory? On my server I have a Ubuntu tvheadend VM running at the same time as using MakeMKV also. Windows VM is running of an SSD outside the array. Dockers image is on disk 1, using 8 of 10GB.