Macro Blocking with Wonder Woman animated

[isu4me]

I've been doing some searching but I can't find anything where this was seen before. I've used makeMKV on hundreds of disks and never had a problem (dvd and blu ray), however I recently picked up the blu ray of the animated Wonder Woman and have found when I create the MKV there is some terrible macro blocking in the opening sequence of the movie, and I have not idea why. When I play the movie in a blu ray player or in power DVD 15 it plays fine. However MKV from makeMKV shows these macro blocks, some pretty bad. I noticed this also when playing through some other blu ray player software on the PC (actually only power DVD 15 seem to play it correctly) as well. I have never seen this before and have no idea how (or if there is a way) to get around it. I assume it has something to do with how the video is processed.
Here is a couple examples of what I'm seeing:






After the opening sequence the move seems to be just fine - I haven't wanted the entire movie, but scanning through I found no further evidence of this. I just use the default settings in makeMKV so I don't know if there are any advanced settings that may be recommend, but any insight would be very helpful.

[Woodstock]

Did you get any messages during the rip about BD+ processing? If not, what is in the file should be a correct copy of the BD data. It is simply the video track copied out of the m2ts file and into an MKV file.

Playback introduces questions about whether or not the player can keep up with the video bandwidth of the file. The first thing that happens when it can't is that the video gets pixelated. Some machines simply cannot copy the data through fast enough for proper display, and the player software uses short-cuts on decoding the video to keep things in time.

[isu4me]

I did not receive any errors during the BD+ process - from the log:

Saving 1 titles into directory N:/
Forced subtitles track #6 turned out to be empty and was removed from output file
Forced subtitles track #8 turned out to be empty and was removed from output file
1 titles saved

I agree where some players may have problems, however I've done this process several times from makeMKV and another application. Played all videos in different players (VLC, plex) with same results. I even played the MKV file that was created in power DVD and it also shows the artifacts - where as it does not when paying the blu ray. These are always the same artifacts in the same place in every copy attempt which leaves to be believe that there is some issue in the creation of the video file (where even other blu ray player apps have shown the issue). I've run the video file through handbrake as well to change it from mkv to mp4 (using the high profile preset) and the artifacts (same ones as before) show up in this file as well, so the problem is with the mkv file being created. It's very odd, and out of doing this hundreds of times, I've never run into this issue before.

I'm using 1.9.2 of makeMKV - windows 8.1 64 bit - i7 - 2600 @ 3.4Ghz 8GB Ram

[isu4me]

Just as an update ... it does not appear to be the video file pulled from makeMKV that is the problem, but how some applications are 'reading' the file. The file I pull from makeMKV (before any other processing) does indeed play without any artifacts / macro blocks from PowerDVD and KMPlayer. However if I play that exact same file through VLC (v2.2.1) or through plex it gets artifact errors. Also if I run the video through handbrake (using the 'high profile' preset), the artifacts show up in the completed file - even when playing through PowerDVD and KMPlayer that previously had no issues - since we know the file played good through before the conversion, but after has the same artifacts after as some players did on the original (pre converted) file. I don't know what's going on. So while I don't think this i really related to makeMKV anymore, any input would be appreciated.

[Woodstock]

VLC 2.2.x has been problematic. I don't think even the latest release version qualifies as "beta test", as much as it crashes.

Fortunately, I still have the install files for 2.1.5...