Is this a drive failing?

[mwebb]

Hi there team,

I'm currently using a Pioneer BDR-S12U as may main UHD ripping drive, and things seem to have be working smoothly for a number of years. Windows 10, drive firmware 1.01 running in LibreDrive mode. Updated to WIndows 11 in October.

I've recently ripped Arrow's UHD of the thetrical The Good, The Bad and The Ugly. Rip copleted fine however on replay there were a couple of sections that displayed a number of video breakups in VLC. Ripped again, and again completed without error; output file is the same size to the byte. Replay in VLC still shows breakups, however now in different locations.

I didn't think a rip could complete cleanly and then result in a corrupted file. Could this realistically be anything other than a failing Bluray drive?

Thanks for your input.

[MartyMcNuts]

Hi there team,

I'm currently using a Pioneer BDR-S12U as may main UHD ripping drive, and things seem to have be working smoothly for a number of years. Windows 10, drive firmware 1.01 running in LibreDrive mode. Updated to WIndows 11 in October.

I've recently ripped Arrow's UHD of the thetrical The Good, The Bad and The Ugly. Rip copleted fine however on replay there were a couple of sections that displayed a number of video breakups in VLC. Ripped again, and again completed without error; output file is the same size to the byte. Replay in VLC still shows breakups, however now in different locations.

I didn't think a rip could complete cleanly and then result in a corrupted file. Could this realistically be anything other than a failing Bluray drive?

Thanks for your input.

The disc could have a scratch or something but more likely to be a codec or hardware issue on playback. What are your PC specs?

[mwebb]

PC is an old i7 NUC. I normally use an OSMC Vero V for replay and I originally noticed the problem as this was suffering from replay stuttering in the problem sections. I then noticed that VLC on my PC shows picture breakup where the Vero stutters. The PC may be underpowered, but the Vero V certainly shouldn't be. ANywho, I feel really confident that the problem is in the output file and not just the replay device.

[mwebb]

After some testing I note that with this disc as source, every time I rip the movie the resulting MKV is of the same length but has a different MD5 hash code.

...is that normal because of a different date and time stamp encoded in the Matroska metadata?

[keydb_helper]

I didn't think a rip could complete cleanly and then result in a corrupted file.

MakeMKV validates the data as it is read via the AACS content hash tables. Any corrupt data should be flagged during reading.

Try to open the ripped MKV file in a video editor such as Avidemux to see whether the corruption you noticed during playback is reproducible when stepping through problematic timestamps frame by frame.

After some testing I note that with this disc as source, every time I rip the movie the resulting MKV is of the same length but has a different MD5 hash code.

...is that normal because of a different date and time stamp encoded in the Matroska metadata?

Yes, that is to be expected.

[mwebb]

I'll give the Avidemux check a go. I've just started running recent rips through ffmpeg -v error and everything I've checked from recent ripping has errors. I'm just going back to something the pre-dates my Windows 11 update in October.

I've also re-commissioned my old BU40N drive, and tried ripping this disc to different destination drives. All combinations currently generate some degree of errors according to ffmpeg.