MKVToolNix v24.0.0 released

[Mosu]

Originally Posted by yetanotherid

but either way is there any way to mux the AC3 into an MKV without it skipping parts of the stream?

Not with mkvmerge, no. In Matroska such garbage data would be invalid anyway.

Even though there's no doubt non-audio sections in the edited AC3 stream for some reason (I don't know what VirtualDubMod is doing there) it remuxes the video into an AVI which stays in sync and which plays perfectly, so I'm wondering if MKVMergeGUI can do the same thing.

mkvmerge usually does a good job at staying in sync if the garbarge is at the very beginning by calculating the delay that garbarge inside the AVI represents. If there's garbarge somewhere in the middle then you're mostly out of luck.

[yetanotherid]

Originally Posted by Mosu

mkvmerge usually does a good job at staying in sync if the garbarge is at the very beginning by calculating the delay that garbarge inside the AVI represents. If there's garbarge somewhere in the middle then you're mostly out of luck.

Thanks for the reply.
But yeah..... it's the garbage in the middle which causes the problem. No doubt I can get around it. Re-encoding the audio stream while it's still inside the originally edited file seems to do the job (via directshow) but I thought I'd ask in case there is a way to avoid re-encoding which I'd been missing.

Cheers.

[yetanotherid]

I just thought I'd add something to my previous post in case someone with a similar problem stumbles across it. So far, I've been able to split files containing AC3 audio using VirtualDub 1.9.10 without any sync issues while remuxing to MKV, while the last version of VirtualDubMod does something to cause the sync problem when it edits.
For VirtualDub you need to install the AC3 plugin or it'll not not what you're giving it when the audio is AC3, and it'll laugh at you when you try to import AC3 audio without the plugin.

[Episodio1]

YETANOTHERID, yes, I have same problems with VDubMod: after you demux AC3 you have to run "ac3fix.exe" to fix that AC3 file. The output file will be OK for Mkv always.

[yetanotherid]

Originally Posted by Episodio1

YETANOTHERID, yes, I have same problems with VDubMod: after you demux AC3 you have to run "ac3fix.exe" to fix that AC3 file. The output file will be OK for Mkv always.

Thanks for that. There's a program/utility for everything.
I also read where someone suggested demuxing with Project X would fix the problem too, although I can't remember where.

Unfortunately though I had a dummy spit and deleted all the files and started again, so now all the editing has been done with VirtualDub so I've not got any out of sync audio to test. I'll have to make one later and try them both out.

It seems kind of odd VirtualDubMod seems to make a mess of the AC3 as it edits video, while VirtualDub does not... Given the first supports AC3 audio but the second requires a third party plugin to open/decode it. At least it seems somewhat odd to me.

[dirk362]

Feature Request - Artist property via mkvpropedit
To be able to set the Artist property field via scripts etc.

At present properties such as Title is setable, but some applications also set Artist as part of their encoding to match their application name.
I'm all for shameless plugs of the programmers efforts, but feel it more preferable to have Artist relate to the original creator of the works.

[Mosu]

Matroska file headres don't contain a field for an author. What you want would require tags, and mkvpropedit cannot edit/replace set tags at the moment. This is planned, but without any priority.

[Xanderian]

hello mosu,
mkvmerge 4.4 here

trying to mux a mov into mkv but for the audio track i get this error

"Warning: Quicktime/MP4 reader: The audio track 1 is using an unsupported 'object type id' of 0 in the 'esds' atom. Skipping this track."

so the file output has no audio..do you have any suggestions ? I can pm you a link for the file btw..

[Mosu]

You can upload it, but I cannot promise you when or even if I take a look at it. The QuickTime format is not really a priority for me at the moment.

[MrVideo]

Tools 4.4.0

I have some h.264 source files, both 1080i and 720p.

When I use the --default-duration 0:59.94fps on 720p source, the playback is at 59.94 fps.

But, for the 1080i h.264 source (from two different suppliers), the 0:29.97fps setting appears to used, as mediainfo shows the frame rate as being 29.97. But, when VLC plays it back, or when streamed to my Blu-ray player, the audio is at the right speed, but the video appears to be at 25 fps.

[... time delay while I try something ...]

Actually it is 15000/1001 fps. As a wild stab, I set the frame rate to 59.94, which is totally wrong for interlace 1080 video, but now it plays correctly.

Anyone have any ideas why double the frame rate needs to be set for it to work?

[Mosu]

mkvmerge has a known issue with calculating the default FPS for interlaced h264 video. I cannot give you a time frame when or if I might get around to working on it.

I'd be really grateful if someone with knowledge about interlaced h264 could chime in a give me some clues about how to derive a frame's duration in interlaced cases. Does the frame rate in the h264 headers (the SPS or whereever it is stored) simply apply to fields in those cases? I'd guess "not always".

[MrVideo]

Originally Posted by Mosu

mkvmerge has a known issue with calculating the default FPS for interlaced h264 video. I cannot give you a time frame when or if I might get around to working on it.

OK, no rush, as there is a workaround.

[madshi]

Originally Posted by Mosu

I'd be really grateful if someone with knowledge about interlaced h264 could chime in a give me some clues about how to derive a frame's duration in interlaced cases. Does the frame rate in the h264 headers (the SPS or whereever it is stored) simply apply to fields in those cases? I'd guess "not always".

IIRC, the h264 "frame rate" is actually always the *field* rate. So e.g. for 1080i50 content, you have a field rate of 50. For 1080p50, you have a field rate of 100. For 1080p24 you have a field rate of 48/1.001. For 1080i60 you have a field rate of 60/1.001.

The average duration of an interlaced field should be "1000 / field rate" milliseconds. The average duration of a progressive frame should be "1000 / frame rate" = "2 * 1000 / field rate".

Originally Posted by Mosu

The QuickTime format is not really a priority for me at the moment.

What is a priority for you at the moment? Or is it a secret?

[Mosu]

Thanks for the info, Madshi. With that info fixing it shouldn't be too hard.

My priorities are pretty much fixing bugs and improving the documentation. Yeah, that's not a lot. Programming in my free time is on the back burner for me for the time being. Mostly a motivational issue as I program full time for a living at the moment. And no matter how much I like programming it's mentally exhausting.

With that being said I think I'll take a look at the frame/field rate issue sometime next week.

[Xanderian]

Mosu I've uploaded the mov file starting with Exp* along with the caps..Hope you can take a look at this issue..

[shon3i]

I have somehow weird problem, i don't know that maybe hardware fault, or is just problem with mkvtoolnix, other muxers are not show this behavior.

I have perfectly "gitch" free 264 stream, when i muxed and watch or examine that stream with DGIndexNV, there is gitches.

Problem is that i can't replicate it every time, at same place. Sometimes muxing can pass without completly.

is there any tool can detect it or something?

btw i think i found way to check, stream will not demux here is eac3to log:

[a02] Invalid EBML data (1). <ERROR>
[a02] Invalid EBML data (1). <ERROR>
[v01] Invalid EBML data (1). <ERROR>
Aborted at file position 1929641984. <ERROR>

[shon3i]

I think i found perfect way to check mkv for errors using mkvextract with

mkvextract tracks "input.mkv"

which scans stream show errors (if any) without real extracting streams.

i will do future invastigate, and report what can be reason. And just less thinking that is problem is on hardware side, i already finished surface memory test without problems, now i do surface test for HDD's which i will have results later.

[LeMoi]

Your file seems to be corrupted. Try mkvverify or even MPEG File Bitrate Viewer to check integrity

[shon3i]

Thanks LeMoi, here is cutted log of scaned mkv.

(mkv parser) file is b0rked:
  pos. 42,031,135: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,150: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,152: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,167: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,169: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,184: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,186: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,201: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,203: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,218: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,220: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,235: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,237: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,252: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,254: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,269: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,271: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,286: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,288: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,303: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,305: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,320: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,322: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,337: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,339: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,354: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,356: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,371: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,373: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,388: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,390: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,405: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,407: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,422: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,424: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,439: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,441: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,456: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,458: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,473: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,475: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,490: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,492: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,507: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,509: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,524: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,526: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,541: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,543: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,558: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,560: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,575: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,577: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,592: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,594: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,609: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,611: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,626: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,628: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,643: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,645: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,660: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,662: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,677: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,679: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,694: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,696: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,711: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,713: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,728: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,730: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,745: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,747: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,762: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,764: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,779: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,781: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,796: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,798: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,813: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,815: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,830: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,832: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,847: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,849: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,864: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,866: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,881: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,883: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,898: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,900: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,915: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,917: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,932: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,934: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,949: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,951: 1st byte of EBML-ID indicates size larger than 4

(mkv parser) warning:
  pos. 42,031,966: element size of 0 encountered

(mkv parser) file is b0rked:
  pos. 42,031,968: 1st byte of EBML-ID indicates size larger than 4

[Cheshire Cat]

Originally Posted by Mosu

No idea, sorry.

Don't know if you recall my posts, but they are right at the last page.

Since our last talk i have been kind of "debugging" what could cause those access issue to mkvs made with more recent mkvtoolnix versions and i've gathered some new data...

In the meanwhile i've tested mkvtoolnix on windows xp. Last version - 4.4.0 - and haven't had any problems. Haven't tested on vista though. But since 7 is my main OS, i guess that is what matters.

With Google's help i've been able to track down some other people with similar complaint and with some testing i've able been able to pinpoint the issue to be somewhat related to the file being left indefinitely open after being accessed (maybe somewhat related to thumbnailing since the files who show these symptoms never show any kind of thumbnail). Let me remind that they are somewhat blocked. Readable but unable to be deleted, renamed or moved. Just after a reboot and even then sometimes they refuse to budge. If one disables the "details pane" the files are indeed movable/deletable & etc. But as soon as that pane is turned back on, problems return with the "defective" files.

I've also been trying different mkvtoolnix versions since the older ones and currently i'm at 3.2.0.0. At the moment things still do work perfectly and i can't report any problem. But as you can imagine testing one version at a time is indeed time consuming. So in a shortcut fashion, could you, or would you be able to say if at a given time you have introduced some modifications to the way mkvtoolnix handles remuxed files?

Since the program's older versions don't have any problems and this symptoms i have been report only show up at these newer versions it has to be some bug related with mkvtoolnix, the way it handles/writes files and/or/with windows 7 explorer...