At the risk of upsetting someone, mkvtoolnix does not function in isolation - it produces data from or for other products and as such one has to mention other things than mkvtoolnix... (if English is not your first langauge, let me underline this is not an attack or critique of mkvtoolnix)
So my question is in relation to mkvtoolnix.... (so please read it twice)
ProgramA outputs an mkv - we'll call it mkvA
If I now play mkvA in deviceB it has certain defects.
I now take mkvA and 'add' it to Mkvmerge Gui - uncheck a few items in MkvMerge Gui and output mkvB
If I now play mkvB it takes a while to play, but then it plays fine.
BUT
If I take Mkvcleave and extract all items from mkvA
And I then only add the items required to Mkvmerge GUI and output mkvC
Then mkvC starts playing fine right away.
So the question about Mkvmerge gui/mkvtoolnix is:
why is there a difference between mkvB and mkvC - they both contain the same(3) items - we just arrived at the content differently.
Does mkvmerge gui reuse the parts of the container (but not the contents) when you start out by using an existing mkv??? I would have thought it authored from scratch so there shouldn't be a difference? (But there is)
|