Configuration Advice and 4K UHD MakeMKV Ripping Opinion:
I have the following Hardware & wanted input on which SSD I should configure the following ways:
Intel 7th Gen Kaby Lake i7-7700
Intel Integrated HD 630
Samsung 850 EVO 500GB 2.5-Inch SATA III Internal SSD (MZ-75E500B/AM)
Samsung 850 EVO 500GB - M.2 SATA III Internal SSD (MZ-N5E500BW)
Samsung 2x 8GB Samsung Streamed 2400MGHz RAM Double Channel
LG Electronics External Blu-ray/DVD Writer 3D Blu-ray Disc Playback & M-DISC Support (BE16NU50 )
Would you guys partition and boot Windows 10 from:
Samsung 850 EVO 500GB 2.5-Inch SATA III Internal SSD (MZ-75E500B/AM)?
or
Samsung 850 EVO 500GB - M.2 SATA III Internal SSD (MZ-N5E500BW)?
What are the chances of ripping 4K UHD Blu-ray with what I got?
Thanks for the input....
SSD or M.2 SATA Configuration Inquiry & 4K UHD Ripping Q'&A'
Re: SSD or M.2 SATA Configuration Inquiry & 4K UHD Ripping Q
At this point, your ability to rip UHD/4K content is ZERO. It is not possible at this time.
http://makemkv.com/forum2/viewtopic.php?f=1&t=16115
Discussion of ripping UHD content can be found in that link.
Fast hardware makes UHD playback in real time possible, with the proper drive and approved software, but there are no ripping solutions yet.
(personally, though, I put the SSD as the boot drive, which speeds EVERYTHING up. but ripping isn't affected, because the limitation on speed there is your optical drive)
http://makemkv.com/forum2/viewtopic.php?f=1&t=16115
Discussion of ripping UHD content can be found in that link.
Fast hardware makes UHD playback in real time possible, with the proper drive and approved software, but there are no ripping solutions yet.
(personally, though, I put the SSD as the boot drive, which speeds EVERYTHING up. but ripping isn't affected, because the limitation on speed there is your optical drive)
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