In Part 1 of my 2014 vs 2019 iMac comparison articles, I provided an overview and a number of comparison benchmark results. In Part 2, I looked at changes in gaming performance between the two machines.
But there was one more thing I wanted to do: Compare Blu-ray ripping speeds. At the time, though, I didn’t have any new movies to rip, and I really didn’t want to spend the time re-ripping an existing movie. Now, though, I do have a few new movies to rip, as I’m trying to finish our collection of all the films in the first three phases (now called the Infinity Saga) of the Marvel Cinematic Universe.
That meant buying the films I’d liked the least—The Incredible Hulk and the first two Thor movies. With that came the chance to compare the Blu-ray ripping speed of the two iMacs. I use the method described in my article Revisiting ripping Blu-ray discs, which is this:
Use MakeMKV to create an MKV file on the hard drive that contains the video and audio tracks.
Use Don Melton’s Video Transcoding tools to create the final movie from the MKV file.
Using The Incredible Hulk, I timed how long it took to create the MKV file and how long it took to create the finished movie. Without further ado, the results (times are in hh:mm:ss format)…
We’ve had our 4K Vizio M70-C3 TV for about 2.5 years, but we just added a Sony UBP-X800 4K Ultra HD Blu-ray player last October. We have a few 4K movies, plus what we watch on the Apple TV and Amazon Prime Video. Stuff mostly looks great, but when watching The Martian the other day, I noticed this odd “wave” effect in the background, whenever the camera panned across a scene. I wrote it off as a one-time thing, until yesterday.
I was trying to watch the extras (which are in 1080p) on the new Black Panther 4K disc, and I noticed the exact same problem. This time I filmed a bit of it with my phone:
Needless to say, this makes it really hard to watch anything—it’s not only distracting, I actually start feeling queasy after a while. After testing a bunch of settings in both the TV and the Sony player, I found the cause: The Sony player’s 4K upscaling. With it disabled, everything looks normal. Turn it on, and any 1080p content gets wavy when panning. Problem solved!
But what about The Martian, which was 4K to begin with, but still had the waves? That was, ummmm, most likely user error: I must have loaded the non-4K disc in the player, as when I tested it yesterday with the 4K disc, everything was fine. Oops!
I have no idea if I have a defective player, or if it’s a limitation on the upscaling, or if it’s just a strange issue between the Sony player and the Vizio TV. Regardless, if you happen to have a similar setup and are seeing annoying waves when the camera pans, try disabling the 4K upscaling feature.
Speed: Faster is better; measured in minutes required to rip.
Size: Smaller is better; measured in MB of drive space used.
Quality: Higher is better; the closer the image quality is to the original, the better.
An ideal rip would be one that happens in seconds, saves into a 10KB file, and has quality matching the original. The reality, though, is far from the ideal. Ripping a movie involves making trade-offs between those three competing measures: Maximizing any one measure requires some sort of tradeoff with one or both of the other measures.
After ripping so many DVDs and Blu-rays over the years, I was curious about how HandBrake and Don Melton’s Video Transcoding tools handle those tradeoffs, so I decided to do some testing.
If you’d like to see what I discovered about ripping time, file sizes, and—with lots and lots of frame grabs—image quality, keep reading…
My problem is that I often forget to do this, because—unlike most GUI Mac apps and the Mac App Store—there’s no built-in “hey, there’s an update!” system. Suddenly, two months and many revisions later, I finally remember (usually when I see a tweet about a new version of something.) So I thought I’d try to write my own simple update reminder.
I didn’t really want a scheduled task, like a launchd agent—it’s not like these tools need to stay current on a daily basis. (And one of them needs to run with admin privileges, which complicates things.) I just wanted something that would remind me if it’d been a while since I last checked for updates, and then install the updates if I wanted it to do so.
After mulling it over, I came up with a script that runs each time I open a Terminal window (which I do daily). The referenced script looks at the date on a check file, and asks me if I’d like to check for updates if that date is more than a week older than today’s date. This is perfect for my needs: The reminder is automatic, but I can choose when to install the updates based on what I’m doing at the time. If it’s been under a week since I last checked, nothing at all is different about my Terminal launch.
Read on for the script and implementation details. (Note: This is not written for a Terminal beginner, as it assumes some knowledge about how the shell works in macOS.)
While writing up this week’s Watch It selection (The Stunt Man), I was rewatching the movie on my TV, and wanted to switch over to the computer. I own a many-years-old DVD version, so I popped it into my iMac, fired up HandBrake and set to ripping it. But I got nothing—HandBrake ripped a 4KB file, then claimed it was done. Not a good start.
A glance at HandBrake’s activity window showed this error:
libdvdread: CHECK_VALUE failed in ifo_read -- error message
Searching on that error message pointed to an error in dvdnav, and some suggested ways of working around it, including installing a patched version. There were also other errors, and searching on those indicated something about the copy protection was causing a read error with the disc.
I also tried RipIt’s built-in rip-and-compress, but it also failed. After mucking about with those two apps, and nearly every other video-related app I own, here’s how I finally managed to rip my legally-purchased version of The Stunt Man:
Used RipIt to copy the DVD to my hard drive. (No settings to worry about here at all.)
Used MakeMKV to make an MKV from the ripped file. I pointed it at the folder from step one, and clicked the Make MVK button. The end result was a number of files, with the longest one being the movie itself.
Used HandBrake to convert the longest MKV file to an m4v file. I just left the settings at the default (high quality), and the end result was a nice quality 1.9GB movie (down from a 7GB MKV file) that plays on all my devices.
I’m posting this here mainly so I remember what I did, but perhaps it’ll help with your stubborn discs as well.