1.8.10 Generating Multiple Invalid Timecodes

Everything related to MakeMKV
Post Reply
ronblade
Posts: 8
Joined: Wed May 21, 2014 8:36 pm

1.8.10 Generating Multiple Invalid Timecodes

Post by ronblade »

While investigating a remuxing issue with 1.8.10, I have also discovered that all of the Blu Ray MKV I have made with 1.8.10 seem to have multiple, sometimes hundreds of invalid timecodes.

The issue is only made clear when attempting to remux a MakeMKV 1.8.10 file -- MakeMKV displays no notice that anything has gone awry during the initial extraction. Upon remuxing the same file with MakeMKV, I seem to be getting the following notice of timecode errors:

=============

Saving 1 titles into directory XXXXXXXXX using profile 'WDTV' from file 'C:\Program Files\MakeMKV/wdtv.mmcp.xml'
AV synchronization issues were found in file XXXXXXXXX (title #1)
AV sync issue in stream 0 at 0:00:03.003 : video frame timecode differs by +1ms
AV sync issue in stream 0 at 0:01:02.103 : video frame timecode differs by +1.291ms
AV sync issue in stream 0 at 0:01:09.944 : video frame timecode differs by +1.125ms
AV sync issue in stream 0 at 0:01:50.443 : video frame timecode differs by +1.333ms
AV sync issue in stream 0 at 0:02:35.321 : video frame timecode differs by +1.166ms
AV sync issue in stream 0 at 0:02:35.363 : video frame timecode differs by +1.458ms
AV sync issue in stream 0 at 0:02:38.032 : video frame timecode differs by +1.125ms
AV sync issue in stream 0 at 0:03:05.226 : video frame timecode differs by +1.291ms
AV sync issue in stream 0 at 0:04:02.992 : video frame timecode differs by +1.25ms
AV sync issue in stream 0 at 0:04:42.448 : video frame timecode differs by +1.166ms
AV sync issue in stream 0 at 0:04:42.448 : too many video frames with invalid timecodes, future messages will be suppressed
AV sync issue in stream 0 at 1:43:16.940 : video stream has 358 frames with invalid timecodes
1 titles saved

=============

If I use 1.8.7 for the initial MKV extraction, the remuxing displays no such errors, even when using 1.8.10 for the remuxing. It appears that 1.8.10 has introduced this issue when it creates MKVs from Blu Ray discs.

Thank you to everyone for your help on this!
mike admin
Posts: 4075
Joined: Wed Nov 26, 2008 2:26 am
Contact:

Re: 1.8.10 Generating Multiple Invalid Timecodes

Post by mike admin »

Can you please do the following:
- Create MKV file (001.mkv) from the disc with 1.8.7
- Create MKV file (002.mkv) from the disc with 1.8.10
- Using mkvtoolnix trim both files to about 3 minutes - you'll get 001_small.mkv and 002_small.mkv .
- Confirm that "small" MKV files still exhibit the issues with 1.8.10 - pgs remuxing fails, and timecodes re invalid on 002_small.mkv but valid on 001_small.mkv

Then upload 001_small and 002_small to dropbox and send the link to support@makemkv.com .

Also, please do a following quick test - try processing the 002.mkv with 1.8.10, you'll get "invalid timecodes" message. Then process the produced file again with 1.8.10 - would you get anything?
ronblade
Posts: 8
Joined: Wed May 21, 2014 8:36 pm

Re: 1.8.10 Generating Multiple Invalid Timecodes

Post by ronblade »

Thanks for your quick reply! I have just emailed you the links to the two trimmed files, which exhibit the behaviors I have described.

As for processing the "bad" file a second time through 1.8.10, yes, it seems to report the timecode errors every time.

If it matters, I use the OSX version of MakeMKV for all of my processing, though I have a Windows machine that I can test on in a pinch.

Thank you for continuing to do such excellent work on this amazing piece of software.
ronblade
Posts: 8
Joined: Wed May 21, 2014 8:36 pm

Re: 1.8.10 Generating Multiple Invalid Timecodes

Post by ronblade »

I just installed a new blu ray drive in my Mac system and I am getting the same timecode errors with 1.8.10. Still wondering if I am the only one experiencing this issue.
Woodstock
Posts: 10385
Joined: Sun Jul 24, 2011 11:21 pm

Re: 1.8.10 Generating Multiple Invalid Timecodes

Post by Woodstock »

A thought - at version 1.8.7, I remember the display of AV sync messages was disabled by default. In 1.8.10, they are enabled by default. Since I turned them on many versions before that (just after I learned about them), that setting has stayed enabled since then. I only noticed the change in default when I installed MakeMKV on a different machine.

On your 1.8.7 installation, go to the Preferences menu, General tab, and make sure that "Show AV synchronization messages" is checked. Then the two installations will be "in sync", as far as error and information messages are concerned.

That would be the true test of whether or not the messages really are JUST because of the version change.
ronblade
Posts: 8
Joined: Wed May 21, 2014 8:36 pm

Re: 1.8.10 Generating Multiple Invalid Timecodes

Post by ronblade »

Thanks for suggesting this, Woodstock, but I have had "show AV synchronization messages" checked in 1.8.7, and however far back that option was available.

Have you used 1.8.10 to remux any blu ray MKV files that you have created with 1.8.10? It seems that these AV sync errors are discovered during the remuxing process, and are only present in files made with 1.8.10.

It's a distinct change that occurred somewhere between 1.8.7 and 1.8.10, and without my system having been changed, I don't know how to further troubleshoot this.
archangel3740
Posts: 1
Joined: Fri May 30, 2014 5:14 pm

Re: 1.8.10 Generating Multiple Invalid Timecodes

Post by archangel3740 »

I'm suffering the same issue, but I've only recently started using 1.8.10. I came across this issue in re-saving default MKVs to WDTV profile MKVs using 1.8.10. I have to go through my 200 movies and find which ones have forced subtitles to make them compatible with my WD TV Live SMP, so I would love to know if I should wait or not.

FWIW, my titles save fine.
ronblade
Posts: 8
Joined: Wed May 21, 2014 8:36 pm

Re: 1.8.10 Generating Multiple Invalid Timecodes

Post by ronblade »

Thank you, archangel3740, for being the first to confirm this behavior on your own system. I was beginning to wonder if I was alone in this. Something tells me that most users do not regularly remux their MakeMKV rips, because this is a really easy issue to spot when you do remux (with "show AV sync errors" turned on). It sounds like you were able to avoid a failure message, at least, when you included subtitles, so that is interesting. Due to the introduction of timesync errors in 1.8.10, though, I am sticking with 1.8.7 until this is resolved, and I recommend that you do, too.
ndjamena
Posts: 830
Joined: Mon Jan 07, 2013 12:23 am

Re: 1.8.10 Generating Multiple Invalid Timecodes

Post by ndjamena »

I forgot this thread, well actually I thought it was about subtitles, since they were mentioned. I tried remuxing a file with MakeMKV to see if it fixed the MediaInfo variable frame-rate problem:

Code: Select all

MakeMKV v1.8.10 win(x64-release) started
Debug logging enabled, log will be saved as C:\Users\Chad/MakeMKV_log.txt
Operation successfully completed
Saving 1 titles into directory E:/Make using profile 'COPYFLAC' from file 'C:\Program Files (x86)\MakeMKV/CopyFlac.mmcp.xml'
DEBUG: Code 0 at ~}Y%g#=<AqntX]+_[7o:121264809
DEBUG: Code 0 at ~}Y%g#=<AqntX]+_[7o:29395517
DEBUG: Code 4294967295 at bd\[Kd6uTi,QKe730o}M:213133480
DEBUG: Code 0 at bd\[Kd6uTi,QKe730o}M:29394482
DEBUG: Code 5292 at bd\[Kd6uTi,QKe730o}M:29393286
DEBUG: Code 0 at 4(yOYXRk(~=y3s-rF"jD,:213135090
LIBMKV_TRACE: Exception: Error while reading input
AV synchronization issues were found in file 'E:/Make/Young_Justice_-_01x05_-_Schooled_t00.mkv' (title #1)
AV sync issue in stream 0 at 0:00:00.480 : video frame timecode differs by +1ms
Failed to save title 0 to file E:/Make/Young_Justice_-_01x05_-_Schooled_t00.mkv
0 titles saved, 1 failed
I thought the error be caused through processing a file modified with MKVPropEdit, so I re-ripped the episode and retried on the clean version and:

Code: Select all

MakeMKV v1.8.10 win(x64-release) started
Debug logging enabled, log will be saved as C:\Users\Chad/MakeMKV_log.txt
Operation successfully completed
Saving 1 titles into directory E:/Make using profile 'COPYFLAC' from file 'C:\Program Files (x86)\MakeMKV/CopyFlac.mmcp.xml'
DEBUG: Code 0 at ~}Y%g#=<AqntX]+_[7o:121264809
DEBUG: Code 0 at ~}Y%g#=<AqntX]+_[7o:29395517
DEBUG: Code 4294967295 at bd\[Kd6uTi,QKe730o}M:213133480
DEBUG: Code 0 at bd\[Kd6uTi,QKe730o}M:29394482
DEBUG: Code 5292 at bd\[Kd6uTi,QKe730o}M:29393286
DEBUG: Code 0 at 4(yOYXRk(~=y3s-rF"jD,:213135090
LIBMKV_TRACE: Exception: Error while reading input
AV synchronization issues were found in file 'E:/Make/Young_Justice_-_01x05_-_Schooled_t00.mkv' (title #1)
AV sync issue in stream 0 at 0:00:00.480 : video frame timecode differs by +1ms
Failed to save title 0 to file E:/Make/Young_Justice_-_01x05_-_Schooled_t00.mkv
0 titles saved, 1 failed
So I retried with a file remuxed with MKVMerge and:

Code: Select all

MakeMKV v1.8.10 win(x64-release) started
Debug logging enabled, log will be saved as C:\Users\Chad/MakeMKV_log.txt
Operation successfully completed
Saving 1 titles into directory F:/ using profile 'COPYFLAC' from file 'C:\Program Files (x86)\MakeMKV/CopyFlac.mmcp.xml'
DEBUG: Code 0 at ~}Y%g#=<AqntX]+_[7o:121264809
DEBUG: Code 0 at ~}Y%g#=<AqntX]+_[7o:29395517
DEBUG: Code 4294967295 at bd\[Kd6uTi,QKe730o}M:213133480
DEBUG: Code 0 at bd\[Kd6uTi,QKe730o}M:29394482
DEBUG: Code 5590 at bd\[Kd6uTi,QKe730o}M:29393286
DEBUG: Code 0 at 4(yOYXRk(~=y3s-rF"jD,:213135090
LIBMKV_TRACE: Exception: Error while reading input
AV synchronization issues were found in file 'F://Young Justice - 01x05 - Schooled.mkv' (title #1)
AV sync issue in stream 0 at 0:00:00.480 : video frame timecode differs by +1ms
Failed to save title 0 to file F:/Young Justice - 01x05 - Schooled.mkv
0 titles saved, 1 failed
The error may have nothing to do with this thread, but the 1ms time code message there may be. Or maybe not, since it's still there after being remuxed with MKVMerge. I thought the 1ms difference in the timecode existed because two audio streams shared the same timecode with the video, but if MakeMKV is reporting it as an AVSync issue I may have been wrong. I should stop posting now.
Post Reply