A Chapter too far?
Posted: Thu Jan 02, 2014 1:13 pm
This was my first post on the MakeMKV Forum:
http://www.makemkv.com/forum2/viewtopic.php?f=1&t=5997
Dan corrected MetaX to properly handle chapters without End Times, so on the surface the fix would seem to be superfluous. However, if one person encounters a problem it's likely someone else will encounter the same problem as well. Personally, I've found this feature to be a godsend. I've written a powershell script to get MKV chapters via MKVExtract and convert them to a .ttxt I can feed to MP4box, without the End Time on the final chapter I'd have been forced to find the running time of the file myself and enter it manually. I've only recently discovered how to get that sort of file information into scripts automatically. Being the first time I'd been on the forum I mistakenly believed the responses I received were from the developers, it turns out Mike didn't participate in the discussion at all, yet apparently read it and realised the value of the request as it was implemented in the next update. I'm glowing at the moment so I'll hold back. It's nice when things work out.
Anyway, I noticed an addition long after I'd left 'ensures that chapter start times point to an I-frame'
I just ripped Buffy and have been entering the chapter names. I know Matroska doesn't allow for negative 'Audio Delays' and apparently the audio for the episodes begin BEFORE the Video. The result being rather then truncating the audio to fit Matroska Specs the delay is instead applied to the Video, meaning the first I-Frame for the video I'm currently looking at is at 80ms and according to MediaInfo and MKVMerge Chapter Editor the first Chapter starts at 80ms as well, rather than absolute Zero (0). It's something I can live with and I don't really mind, but I'm wondering if that's entirely necessary (for those of us with obsessive personalities).
http://www.makemkv.com/forum2/viewtopic.php?f=1&t=5997
Dan corrected MetaX to properly handle chapters without End Times, so on the surface the fix would seem to be superfluous. However, if one person encounters a problem it's likely someone else will encounter the same problem as well. Personally, I've found this feature to be a godsend. I've written a powershell script to get MKV chapters via MKVExtract and convert them to a .ttxt I can feed to MP4box, without the End Time on the final chapter I'd have been forced to find the running time of the file myself and enter it manually. I've only recently discovered how to get that sort of file information into scripts automatically. Being the first time I'd been on the forum I mistakenly believed the responses I received were from the developers, it turns out Mike didn't participate in the discussion at all, yet apparently read it and realised the value of the request as it was implemented in the next update. I'm glowing at the moment so I'll hold back. It's nice when things work out.
Anyway, I noticed an addition long after I'd left 'ensures that chapter start times point to an I-frame'
I just ripped Buffy and have been entering the chapter names. I know Matroska doesn't allow for negative 'Audio Delays' and apparently the audio for the episodes begin BEFORE the Video. The result being rather then truncating the audio to fit Matroska Specs the delay is instead applied to the Video, meaning the first I-Frame for the video I'm currently looking at is at 80ms and according to MediaInfo and MKVMerge Chapter Editor the first Chapter starts at 80ms as well, rather than absolute Zero (0). It's something I can live with and I don't really mind, but I'm wondering if that's entirely necessary (for those of us with obsessive personalities).