Failed to save title error from Spooks S4 disk 2 DVD

[DannyBoy999]

Hi, I am getting a failure to save title error on DVD rip - Spooks Series 4, disk 2, episode 3.
I have tried creating the mkv straight from the DVD and also copying the disk contents to HDD first, fails both times. All other episodes are fine, including the other title on the same disk.

Log as follows:
MakeMKV v1.6.5 win(x86-release) started
Debug logging enabled, log will be saved as C:\Users\Dan/MakeMKV_log.txt
Opening files on harddrive at C:/Users/Dan/Desktop/VIDEO_TS/
Calculated BUP offset for VTS #0 does not match one in IFO header.
Calculated BUP offset for VTS #1 does not match one in IFO header.
Calculated BUP offset for VTS #2 does not match one in IFO header.
Titleset start sector mismatch for titleset 2 : 1574246 != 1574262
Title #0 has length of 30 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #1 was added (8 cell(s), 0:58:47)
Title #2 was added (9 cell(s), 0:58:59)
Operation successfully completed
Saving 2 titles into directory E:/Spooks/Series 4
DEBUG: Code 42 at oi`['a$bye-y&K@ ERr:213134377
DEBUG: Code 149 at oi`['a$bye-y&K@ ERr:29398070
DEBUG: Code 4 at oi`['a$bye-y&K@ ERr:213134423
DEBUG: Code 0 at TAs$+JwO"O@C3']rJd;qV:29397449
LIBMKV_TRACE: Exception: Error while reading input
Failed to save title 0 to file E:/Spooks/Series 4/title00.mkv
1 titles saved, 1 failed

Any help appreciated, thanks!

[mike admin]

This is a disc mastering error. The full log file ( C:\Users\Dan/MakeMKV_log.txt ) should contain a lot of additional debug strings - please send it to support@makemkv.com and we'll add a workaround. There's nothing else you can do unfortunately.

[DannyBoy999]

Email sent. What is a mastering error? Will the workaround allow me to rip the remaining episode?

[crowfax]

What is a mastering error?

It means when the disc was produced they incorrectly followed the DVD specification.

[DannyBoy999]

@mike admin - Have you an idea of when this workaround will be available?

[DannyBoy999]

Hi, not sure if this workaround was included in v 1.6.6 but if so it has not worked.