Hello Friends,
Is it possible to use a shared Blu-Ray drive in makemkv?
I have a Workstation which is controlled via Remote Desktop and a Blu-Ray Drive on an other PC.
I want use makemkv on the Workstation to rip Blu-Rays from the Networkdrive
Maischens
Network shared Blu-Ray drive
Re: Network shared Blu-Ray drive
MakeMKV needs to talk to the drive at a very low level, usually not allowed via network connections. There are many people who use MakeMKV on "headless workstations", connecting via remote desktop-type software, but that still requires that MakeMKV have access to the drive interface.
MakeMKV Frequently Asked Questions
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
-
Fozzy Fozborne
- Posts: 1
- Joined: Tue Sep 03, 2019 3:55 am
Re: Network shared Blu-Ray drive
The only method I've found is Paragon Net Burner.
https://www.softpedia.com/get/CD-DVD-To ... rner.shtml
You install the 'server' version on the computer with the burner and the 'client' version on the computer(s) you want to access it.
It's an iSCSI connection so it allows the drive to appear to Windows at a similar level as straight from a SATA controller.
(The major exception would be that you wouldn't want to do a firmware update over the network).
It works for me with one PC with a Blu Ray burner and another that doesn't have a drive, both Windows 10 Pro.
I can backup BR discs over the network and burn just fine using an old CT10L drive and a Pioneer BDR-209DBK.
I don't have a UHD drive so I can't comment on that.
You will want to enable removable drives through remote sessions if you're using Windows 10.
This wasn't necessary on Windows 7, but...
This is outlined in the second post here: https://social.technet.microsoft.com/Fo ... itpromedia
In the local Group Policy editor, go into Computer Configuration/Administrative Templates/System/Removable Storage Access
Enable the policy "All Removable Storage: Allow direct access in remote sessions"
(This is done on the 'server' computer).
Once you have the drive mounted on the client computer you just point MakeMKV (it usually/(always?)) defaults to the network drive and use it like you normally would.
Here's the guide I used if you get stuck:
https://dottech.org/16667/share-your-cd ... et-burner/
If you get to the point where they can't connect try temporarily disabling Windows firewall just to check they can connect. From there you can add a local exception.
https://pureinfotech.com/allow-apps-fir ... indows-10/
(Select the main executable with private access if it doesn't show up on the list).
https://www.softpedia.com/get/CD-DVD-To ... rner.shtml
You install the 'server' version on the computer with the burner and the 'client' version on the computer(s) you want to access it.
It's an iSCSI connection so it allows the drive to appear to Windows at a similar level as straight from a SATA controller.
(The major exception would be that you wouldn't want to do a firmware update over the network).
It works for me with one PC with a Blu Ray burner and another that doesn't have a drive, both Windows 10 Pro.
I can backup BR discs over the network and burn just fine using an old CT10L drive and a Pioneer BDR-209DBK.
I don't have a UHD drive so I can't comment on that.
You will want to enable removable drives through remote sessions if you're using Windows 10.
This wasn't necessary on Windows 7, but...
This is outlined in the second post here: https://social.technet.microsoft.com/Fo ... itpromedia
In the local Group Policy editor, go into Computer Configuration/Administrative Templates/System/Removable Storage Access
Enable the policy "All Removable Storage: Allow direct access in remote sessions"
(This is done on the 'server' computer).
Once you have the drive mounted on the client computer you just point MakeMKV (it usually/(always?)) defaults to the network drive and use it like you normally would.
Here's the guide I used if you get stuck:
https://dottech.org/16667/share-your-cd ... et-burner/
If you get to the point where they can't connect try temporarily disabling Windows firewall just to check they can connect. From there you can add a local exception.
https://pureinfotech.com/allow-apps-fir ... indows-10/
(Select the main executable with private access if it doesn't show up on the list).