- #MAKEMKV BETA KEY MARCH 2019 UPDATE#
- #MAKEMKV BETA KEY MARCH 2019 REGISTRATION#
- #MAKEMKV BETA KEY MARCH 2019 OFFLINE#
- #MAKEMKV BETA KEY MARCH 2019 PLUS#
One more strange note: In the Win10 VM, under LibreDrive Information, all of the statuses below "firmware version" show "Yes", but in the MakeMKV docker, "Unrestricted read speed" shows "possible, not yet enabled". I edited the docker to set PUID and PGID to 0 each, restarted the docker, and bam the drive is visible. Fire up the MakeMKV docker (privileged mode), and poof, no drive. I tested it in the VM, ripped a basic Blu-Ray, no issues.
I fired up a Win10 VM, passed the drive through, and flashed with a patched version of the 1.02 firmware (1.02-MK) so I can backup blu-rays. Upon first installation of the drive into my Unraid machine, I installed and fired up the binhex-makemkv docker, and the drive was, with no changes to the template or extra parameters (privileged mode), visible in MakeMKV. So, another person to throw their hat into this ring, as I am having the same issue, but I happened to see something possibly interesting (or maybe entirely irrelevant) before the issue started.ĭrive: LG WH16NS60, mounted internally via SATA. I decided to give jlesage's docker a try and with the -device /dev/sg6 -device /dev/sr0 setting it worked right away. cd/dvd PIONEER BD-RW BDR-209D 1.34 /dev/sr0 /dev/sg6Īfter trying -device=/dev/sg6 -device=/dev/sr0 and -device /dev/sg6 -device /dev/sr0 (which I'm certain I was using in Extra Parameters previously) I tired other variations like -device=/dev/sg6:/dev/sr0, -device=/dev/sr0:/dev/sr0, -device=/dev/sg6, -device=/dev/sr0 none of which worked. So when I had trouble getting binhex's docker to work, I thought it was something I was doing wrong. Stupidly I deleted Saarg's docker as soon as I read his abandon post so I lost my 'config' to refer to. However I can not get binhex's MakeMKV docker to recognize my SATA optical drive. I'm happily using binhex's emby and krusader dockers so I figured, let's keep it in the family. Recently he broke it and decided to abandon the project and recommended binhex's or jlesage's project. So I changed the date and time via the CMD Line and I can currently rip DVDs.I have been using Saarg's MakeMKV docker for years.
I checked the BIOS Date and it was still March 15th were I set it but doing a "date" command with the CMD Line showed the actual current time. I shutdown my Vortexbox and changed my system time at start-up and it shows that new older date/time in the GUI Window when the ripper initializes, but right before the actual ripping starts it shows the actual current time and the rip fails out with the Key Expired error. Lastly note that changing the system time in the BIOS might not work but doing the CMD Line does work for sure.
#MAKEMKV BETA KEY MARCH 2019 OFFLINE#
The second line (hat tip MarkDan) prevents the Name Search via the offline IP Address that causes the ripping script to fail. Also the date and time are bracketed by the ' grave mark and not quotation marks. NOTE: one does an ENTER/Return at the end of each line (last time I typed Return somebody kept typing in the word 'return'). This will set the date of the Vortexbox back to 2AM on March 20th when the Key is still good for the current MakeMKV version.
#MAKEMKV BETA KEY MARCH 2019 REGISTRATION#
Please download the latest version or enter a registration key to continue using the current version." and the new MakeMKV Key has still not been issues yet, try changing the date and time from the CMD Line:
If your are getting this error "This application version is to old. " In the past this has meant the Beta one was using was expired and the latest version needed to be pulled down from the REPO with a new 30 day user key. Please download the latest version or enter a registration key to continue using the current version. " Error 'Scsi error - ILLEGAL REQUEST:READ OF SCRAMBLED SECTOR WITHOUT AUTHENTICATION' occurred while reading 'DVD+R-DL HL-DT-ST DVD-RAM GH40L RB02' at offset '1048576' "
#MAKEMKV BETA KEY MARCH 2019 PLUS#
And if it works for me, I will post it up to the Wiki for everybody.Īnd yes, I know I can buy a KEY from MakeMKV to instantly make it work again, but I am waiting to get a reply to one of my questions over on MakeMKV plus it looks like the DVD I am ripping might need a new version of MakeMVK to rip this DVD. Does anybody have the procedures/instructions for using the CMD Line to actually pull this down from MakeMKV? If so, I would love to try it.
#MAKEMKV BETA KEY MARCH 2019 UPDATE#
The latest version does not come down from the REPO using the Upgrade Button in the GUI or by CMD Line dnf update -y. I can't rip anymore DVDs because it seems the Beta MakeMKV version on my 2.4 Vortexbox is past the 30 day Beta and needs a new version/update.
0 kommentar(er)
