Randon Pixelation
Posted: Fri Feb 22, 2019 12:10 pm
Hi, I am new to mkv. Many years ago I embarked on a project to rip lossless episodic DVD and BD to Emby Server for Netflix-Style on-demand playback. I ripped DVD using CloneDVD and BD using AnyDVD and BDRebuilder, but project faltered due to time.
I have a Ryzen7 2700X/32Gb Workstation 64-Bit Windows10, Asus BW-16D1HT (3.02fw) and end-goal will be direct NFS share playback via DuneHD 4K. I was not quite decided on mkv episodes or ISO Rips, but have tried both methods with the latest MKV build. I am favouring 1:1 full ISO as it seems a much quicker process, and Emby Server now has limited support for indexing full ISOs, and storage is so cheap compared to when I last did this.
Using Makemkv in default options, on both BD Backup and MKV episode rips, I see random pixelations on file playback. When I say random, I mean the pixilation can occur in different places when ripping the same disc with same settings over again. But on an output file, the pixilation on playback is always in the same place, and can be replicated on network playback via Emby App on Xbox/AppleTV, Panasonic UHD Player, as well as the preferred DuneHD device. So the issue seems to be inherent pixilation/artifacts within the created video file. I have tried cleaning/wiping the discs - 3 separate discs tried thus far, and disks play flawlessly in the Panasonic UHD Player.
So I reverted to AnyDVD ripping to drive instead of Makemkv, and also BDRebuilder - I have the same pixilation issues on those methods as well. So it's not a specifc Makemkv problem, but as it's the most popularly used tool, I'm still asking for advice here.
Looking though posts on the forums, I have already troubleshooted as follows with no change :-
1. Tried a different BD Drive - Pioneer BDR-206D - same issues
2. Tried changing target Output Folder from underlying Hard Drive to SSD Drive - same issues
3. Tried Backup to Drive before running MKV or BDRebuilder to output mkv files - same issues
4. Used Single Drive Mode and BD+ dumps in Expert Mode
5. Ran Windows Memory Diagnostic Test - No Issues at all
I have seen other references to limiting CPUs in some way, and running MD5 checksum on original versus output files, but it wasn't clear how to do this. Any suggestions or other ideas herein?
I have a Ryzen7 2700X/32Gb Workstation 64-Bit Windows10, Asus BW-16D1HT (3.02fw) and end-goal will be direct NFS share playback via DuneHD 4K. I was not quite decided on mkv episodes or ISO Rips, but have tried both methods with the latest MKV build. I am favouring 1:1 full ISO as it seems a much quicker process, and Emby Server now has limited support for indexing full ISOs, and storage is so cheap compared to when I last did this.
Using Makemkv in default options, on both BD Backup and MKV episode rips, I see random pixelations on file playback. When I say random, I mean the pixilation can occur in different places when ripping the same disc with same settings over again. But on an output file, the pixilation on playback is always in the same place, and can be replicated on network playback via Emby App on Xbox/AppleTV, Panasonic UHD Player, as well as the preferred DuneHD device. So the issue seems to be inherent pixilation/artifacts within the created video file. I have tried cleaning/wiping the discs - 3 separate discs tried thus far, and disks play flawlessly in the Panasonic UHD Player.
So I reverted to AnyDVD ripping to drive instead of Makemkv, and also BDRebuilder - I have the same pixilation issues on those methods as well. So it's not a specifc Makemkv problem, but as it's the most popularly used tool, I'm still asking for advice here.
Looking though posts on the forums, I have already troubleshooted as follows with no change :-
1. Tried a different BD Drive - Pioneer BDR-206D - same issues
2. Tried changing target Output Folder from underlying Hard Drive to SSD Drive - same issues
3. Tried Backup to Drive before running MKV or BDRebuilder to output mkv files - same issues
4. Used Single Drive Mode and BD+ dumps in Expert Mode
5. Ran Windows Memory Diagnostic Test - No Issues at all
I have seen other references to limiting CPUs in some way, and running MD5 checksum on original versus output files, but it wasn't clear how to do this. Any suggestions or other ideas herein?