Makemkv command line3/2/2023 ![]() ![]() ![]() ![]() ifoīlu-Ray discs and DVD’s can be quite large which makes converting take some time, but ultimately how long the entire procedure lasts depends on a few things: the length of the movie being converted, the speed of the Blu-Ray/DVD drive itself, and the performance of the Mac in general. * MakeMKV can open any Blu-Ray, DVD, HD-DVD, ISO, or MKV file with the app, either by pointing directly at the disc itself, or by selecting a compatible video file format, which is any of the following video file types. Click the “Make MKV” button to start the conversion process.Choose the output folder (default is set to ~/Movies/DiscName).Select any options from the side menu, choosing whether to include all audio streams, subtitles, or only include specific languages (i.e.Launch MakeMKV and open a compatible video disc or file format* with the app, which then scans and imports the file/disc.Take a moment to download MakeMKV free from the developer (Mac and Windows versions available).This works to rip any compatible disc or file format* to an MKV, we’re running through this on a Mac but if you have a Windows PC with a BluRay disc the process should be the same because the app is cross-platform compatible. I went through and did some regression testing with 8.5.9.0, 8.6.0.0, 8.6.1.0 and 8.6.2.0 and they all had the same behavior as long as I ejected the disc between installs, so this is most likely unique to my setup or something with the new Windows 11 22H2 build.Ripping a Blu-Ray Disc or DVD to MKV with MakeMKV It seems like something during the install/initialization process is getting it to work with the current inserted disc, but once the disc is ejected then it breaks? Same with running MakeMKV where it seems to initialize something for the inserted disc. Once I eject/close the disc tray then it will go back to the bad OPD. Something interesting that I stumbled upon when I forgot to eject the disc while I was installing different versions of AnyDVD is that if I don't eject the disc after re-installing AnyDVD (same version) then it generates the correct OPD in the log. I have also tried creating a log file a second time without ejecting the disc and it was still the bad OPD. Unfortunately, the log still shows Info: Using OPD BD_d8f9d36eabdc which is not the good one. I stopped and disabled the cdrom arbiter service, ejected/closed the disc tray and created a log file like previous testing. OPD without MakeMKV running: BD_bb1d000daaf4 (Bad)ĪnyDVD logs attached for the two scenarios on both drives.Ĭlick to expand.I went through and did some regression testing with 8.5.9.0, 8.6.0.0, 8.6.1.0 and 8.6.2.0 and they all had the same behavior as long as I ejected the disc between installs, so this is most likely unique to my setup or something with the new Windows 11 22H2 build.īack to using 8.6.2.3. OPD with MakeMKV running: BD_df8884bfebb1 (Good)Īttached is the AnyDVD log for the Inception UHD physical disc in the LG WH16NS40 drive. OPD without MakeMKV running: BD_d8f9d36eabdc (Bad) LG WH16NS40 with 1.05 MK firmware and an ASUS BW-16D1HT with 3.10 MK firmware.Īttached is the AnyDVD log for the Inception UHD physical disc in the ASUS BW-16D1HT drive. Although it may continue working until the drive door is opened and closed. Both generate a different but unique to the drive bad OPD without MakeMKV running. I have not rolled back to any previous AnyDVD versions yet since I just identified the correlation with MakeMKV running.Ĭurrently using AnyDVD HD 8.6.2.3 and two drives in my system. I haven't run the scanner against my unsupported protected UHD ISO's for several months until today so I don't know when the issue started. Initially I thought my issue might be from updating to Windows 11 22H2. This started over in the unsupported UHD thread until I discovered I was generating bad OPD ID's in the scanner report. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |