Changing mkv track header info result - unplayable

[setarip_old]

Hi!

I don't know if the following is relevant but, I seem to recall that a while back (perhaps several months ago), there was a big brouhaha resulting from "MKVMerge/Toolnix" changing its output from a "full" header" to a "compressed" header that was other than fully compatible with "MKVMerge/Toolnix" files created with "full" headers.

I wonder if this could have anything to do with what you're experiencing...

[Chetwood]

Doubtful. Mosu will make sure that newer versions of MKVToolnix can read all previously authored MKVs.

[setarip_old]

@Chetwood

Hi!

I believe you'll find posts referring to this situation in "Mosu's" thread at the Doom9 Forums...

[Chetwood]

URL or it didn't happen

[DiscoVision]

I'm going to resurrect this thread. I have found I can change the name of the audio channels without any problem. However, if I add the 'Commentary Track' element (flag) to ANY track, the resultant MKV file will not play in anything other than VLC. IMO, VLC isn't the end-all player. If none of the built in windows players (including windows explorer) recognize the file as valid.

I have just 'restored' a file which I had flagged 4 separate tracks with the "Commentary Track" flag by simply removing the element. But I had to remove it from all 4 tracks before the file will work in Windows and Plex.

[dcoke22]

I'm going to resurrect this thread. I have found I can change the name of the audio channels without any problem. However, if I add the 'Commentary Track' element (flag) to ANY track, the resultant MKV file will not play in anything other than VLC. IMO, VLC isn't the end-all player. If none of the built in windows players (including windows explorer) recognize the file as valid.

I have just 'restored' a file which I had flagged 4 separate tracks with the "Commentary Track" flag by simply removing the element. But I had to remove it from all 4 tracks before the file will work in Windows and Plex.

The Commentary Flag is a Matroska v4 element. It could be the case that some players don't know how to correctly parse a v4 file.