{"action":"created","issue":{"url":"https://api.github.com/repos/mbunkus/mkvtoolnix/issues/2140","repository_url":"https://api.github.com/repos/mbunkus/mkvtoolnix","labels_url":"https://api.github.com/repos/mbunkus/mkvtoolnix/issues/2140/labels{/name}","comments_url":"https://api.github.com/repos/mbunkus/mkvtoolnix/issues/2140/comments","events_url":"https://api.github.com/repos/mbunkus/mkvtoolnix/issues/2140/events","html_url":"https://github.com/mbunkus/mkvtoolnix/issues/2140","id":269322283,"number":2140,"title":"DVBSUB timestamps and duration","user":{"login":"mkver","id":18448094,"avatar_url":"https://avatars1.githubusercontent.com/u/18448094?v=4","gravatar_id":"","url":"https://api.github.com/users/mkver","html_url":"https://github.com/mkver","followers_url":"https://api.github.com/users/mkver/followers","following_url":"https://api.github.com/users/mkver/following{/other_user}","gists_url":"https://api.github.com/users/mkver/gists{/gist_id}","starred_url":"https://api.github.com/users/mkver/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mkver/subscriptions","organizations_url":"https://api.github.com/users/mkver/orgs","repos_url":"https://api.github.com/users/mkver/repos","events_url":"https://api.github.com/users/mkver/events{/privacy}","received_events_url":"https://api.github.com/users/mkver/received_events","type":"User","site_admin":false},"labels":[{"id":215927211,"url":"https://api.github.com/repos/mbunkus/mkvtoolnix/labels/app:mkvmerge","name":"app:mkvmerge","color":"fbca04","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2017-10-28T14:36:57Z","updated_at":"2017-11-12T09:49:51Z","closed_at":"2017-11-12T09:49:51Z","author_association":"CONTRIBUTOR","body":"Hello,\r\n\r\nI'm experiencing a weird issue with DVBSUB timestamps and durations. From a point onward, every second DVBSUB packet (namely those packets that actually contain a subtitle, not those that just indicate the end of a subtitle) has a gigantic duration:\r\n```\r\nI frame, track 1, timestamp 3792102 (01:03:12.102), duration 2160.000, size 2396, adler 0x282a954b\r\nI frame, track 1, timestamp 3794262 (01:03:14.262), duration 2720.000, size 55, adler 0x98141639\r\nI frame, track 1, timestamp 3796982 (01:03:16.982), duration 3380.000, size 3531, adler 0x257fae87\r\nI frame, track 1, timestamp 3800362 (01:03:20.362), duration 53340.000, size 54, adler 0x46f6131f\r\nI frame, track 1, timestamp 3853702 (01:04:13.702), duration 95445040.000, size 1948, adler 0xfc7ec1d3\r\nI frame, track 1, timestamp 99298740 (27:34:58.740), duration 460.000, size 54, adler 0x464b1325\r\nI frame, track 1, timestamp 99299200 (27:34:59.200), duration 95445120.000, size 4099, adler 0xdbea0502\r\nI frame, track 1, timestamp 194744317 (54:05:44.317), duration 500.000, size 54, adler 0x4c4d1366\r\nI frame, track 1, timestamp 194744817 (54:05:44.817), duration 95445576.000, size 3604, adler 0xc9ece815\r\nI frame, track 1, timestamp 290190395 (80:36:30.395), duration 2300.000, size 54, adler 0x447f1257\r\nI frame, track 1, timestamp 290192695 (80:36:32.695), duration 95445520.000, size 1715, adler 0x8ea65280\r\nI frame, track 1, timestamp 385638213 (107:07:18.213), duration 3280.000, size 54, adler 0x4b7f1397\r\nI frame, track 1, timestamp 385641493 (107:07:21.493), duration 95445176.000, size 1943, adler 0xb184dd1c\r\nI frame, track 1, timestamp 481086671 (133:38:06.671), duration 11900.000, size 55, adler 0x924615d7\r\nI frame, track 1, timestamp 481098571 (133:38:18.571), duration 95445920.000, size 3190, adler 0x16b64802\r\n```\r\nSome more info: My recording device splits the files it creates into about 1 GiB pieces. The above issue happens in the sixth file; but if I remux this file alone, everything's fine. If I add files 3-6 to the second file as additional part, the issue doesn't show up. But if I add the sixth file to the first one (as additional part) it does happen (even when I omit the files in between). Therefore I am uploading the first and the sixth file first; if you can already reproduce it, then I might not need to upload the rest.\r\nmkvmerge isn't the only tool that shows weird timestamps: SubtitleEdit gives the first entry a timestamp of 26:27:19.218 and wraps around during the first file:\r\n![se](https://user-images.githubusercontent.com/18448094/32135423-ab60c702-bbee-11e7-8c56-64bdf0a2d2cb.png)\r\nI tested this on Windows 7 x64. Maybe it's an overflow affecting only Window as has already happened in #1883.\r\n\r\nGrüße\r\nAndi\r\n\r\nPS: During transmission of the first file the FileZilla showed the following error message: \"Fehler:\tIncoming packet was garbled on decryption\r\nFehler:\tDateiübertragung fehlgeschlagen nach Übertragung von 551.616.512 Bytes in 3610 Sekunden\". Given that FileZilla was aware of this error, it could probably correct it by retransmitting the data. Just to be sure: The CRC64 of 00000.ts is CD828EB1505376A2; for 00005.ts it is 12904FD309D00976.\r\n[Edit]: I have now uploaded the first and sixth file and am currently uploading the second one, although I don't think that it is needed."},"comment":{"url":"https://api.github.com/repos/mbunkus/mkvtoolnix/issues/comments/343725184","html_url":"https://github.com/mbunkus/mkvtoolnix/issues/2140#issuecomment-343725184","issue_url":"https://api.github.com/repos/mbunkus/mkvtoolnix/issues/2140","id":343725184,"user":{"login":"mbunkus","id":414282,"avatar_url":"https://avatars0.githubusercontent.com/u/414282?v=4","gravatar_id":"","url":"https://api.github.com/users/mbunkus","html_url":"https://github.com/mbunkus","followers_url":"https://api.github.com/users/mbunkus/followers","following_url":"https://api.github.com/users/mbunkus/following{/other_user}","gists_url":"https://api.github.com/users/mbunkus/gists{/gist_id}","starred_url":"https://api.github.com/users/mbunkus/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mbunkus/subscriptions","organizations_url":"https://api.github.com/users/mbunkus/orgs","repos_url":"https://api.github.com/users/mbunkus/repos","events_url":"https://api.github.com/users/mbunkus/events{/privacy}","received_events_url":"https://api.github.com/users/mbunkus/received_events","type":"User","site_admin":false},"created_at":"2017-11-12T09:49:51Z","updated_at":"2017-11-12T09:49:51Z","author_association":"OWNER","body":"This looks due to mkvmerge's handling of other types of broken subtitle timestamps in transport stream files. As this is a big mess already and as fixing your particular issue would most likely cause other broken files (that mkvmerge now handles fine) to become broken again, I won't spend more time on this. It will remain unfixed. Sorry."}}
{"actor":{"display_login":"mbunkus"}}