lasassuper.blogg.se

Makemkv registration code incorrectly
Makemkv registration code incorrectly






The drive appears and i can actually start reading the dvd. I then did the console thing a user has posted before and executed the commands starting with "pacman -S -noconfirm usbutils". I tried mounting via menu option "add device", but no luck, the cdrom doesnt show up. "cd/dvd PLDS DVD-RW DS8A9SH E元A /dev/sr0 /dev/sg11". i tried finding the commands for finding mounted drives and somehow ended up with I also encountered the missing drive error. So this is my noob experience report, i tried connecting a optical dvd drive to rip a dvd with binhex makemkv. I found the other docker you are using and it worked perfectly after i added the device to extra parameters. For the life of me i couldnt get this version to see my internal SATA Bluray drive. Maybe there is something strange with the firmware causing the drive not to be recognized by the docker with the default 99/100 PUID/PGID? I have no idea how that would be, but that's the only thing that changed between the first boot-up and then using the patched version.Įxact same boat for me. Already have a correction: I re-ran the test in the WIn10 VM to make sure I was ripping the same exact stream from the disk and the speeds are nearly identical (16MB/s) to what the docker was able to read (15.4MB/s), so I guess I originally ripped a different stream further to the edge of the disc. There at least seems to be a difference in performance as the read speed seems to be limited at a steady 15MB/s read from the docker, but manages almost 30MB/s from Win10. 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.

makemkv registration code incorrectly

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. I have been using Saarg's MakeMKV docker for years.








Makemkv registration code incorrectly