MKVToolNix v89.0 released

[Mosu]

Originally Posted by Selur

Okay, how to set the PAR to 1:1 on a source?

No need to open an issue anymore. The problem should be fixed by this commit. Please read the explanation in the commit's message for details on what actually happend.

[Selur]

Thanks, afk. today, will look at it tomorrow evening and report back.

[Selur]

Okay, I did some tests:
av1:

mkvmerge --ui-language en -o "G:\Output\2023-09-03@18_46_32_6310__02.mkv" --global-tags "J:\tmp\mkvtags_2023-09-03@18_46_32_6310__02.xml" -d 0 --default-track 0:yes --default-duration "0:25/1fps" --aspect-ratio-factor 0:16/11 --no-chapters --compression -1:none --forced-track 0:yes --field-order 0:0 --no-audio --no-subtitles "J:\tmp\av1_1_2023-09-03@18_46_32_6310_01.av1" --track-order 0:1

x264:

mkvmerge --ui-language en -o "G:\Output\2023-09-03@18_46_46_6310__02.mkv" --global-tags "J:\tmp\mkvtags_2023-09-03@18_46_46_6310__02.xml" -d 0 --default-track 0:yes --default-duration "0:25/1fps" --aspect-ratio-factor 0:16/11 --fourcc 0:MP4V --no-chapters --compression -1:none --forced-track 0:yes --field-order 0:0 --no-audio --no-subtitles "J:\tmp\2023-09-03@18_46_46_6310_01.264" --track-order 0:1

x265:

mkvmerge --ui-language en -o "G:\Output\2023-09-03@18_46_54_1610__02.mkv" --global-tags "J:\tmp\mkvtags_2023-09-03@18_46_54_1610__02.xml" -d 0 --default-track 0:yes --default-duration "0:25/1fps" --aspect-ratio-factor 0:16/11 --no-chapters --compression -1:none --forced-track 0:yes --field-order 0:0 --no-audio --no-subtitles "J:\tmp\2023-09-03@18_46_54_1610_01.265" --track-order 0:1

Conclusion is: Now x264 and x265 works, but av1 is broken.
I tried av1 files created with QSVEncC, NVEncC, aomenc, svt-av1, to be sure it's not related to av1 from one encoder.
And the funny thing is the av1 streams from av1-svt, rave1 and aomenc are handled correctly, the others are not.
Uploaded the muxed files to GoogleDrive.

Cu Selur

[Boulder]

Running mkvalidator on one file muxed by mkvmerge 79.0, I get an error "ERR0B1: Block at 1439158911 track #2 is not a keyframe". Didn't try reinstalling the previous version yet, but is this something to submit an issue about?

[Mosu]

Originally Posted by Boulder

Running mkvalidator on one file muxed by mkvmerge 79.0, I get an error "ERR0B1: Block at 1439158911 track #2 is not a keyframe". Didn't try reinstalling the previous version yet, but is this something to submit an issue about?

No. That's wrongly labeled as an error by mkvalidator. In my personal opinion this shouldn't even be a warning. It's not a violation of the specs, it's not even a severe issue wrt. performance. Would it be ideal to have each cluster start with a key frame for each track? Sure. Is it always possible? Definitely not.

[Ripman]

Hey M. Hope you had a nice summer. About 34 today in NYC.

=> Is “Video Display Unit” (VDU) set based on the values for “Video Display Width” (VDW) and “Video Display Height” (VDH) passed with the --display-dimensions option? Or maybe based on whether the --aspect-ratio option or the --aspect-ratio-factor option was used.

(I’m assuming --aspect-ratio can be passed as 16x9, 4x3, 1.85, 2.40, etc., but I’m not sure what values can be passed for --aspect-ratio-factor.)

The reason I ask is because I have a widescreen mpeg2 video, that, after being cropped and encoded to mpeg4, shows a VDW of 11418 and a VDH of 6237 via the MKVToolNix header editor. This will give the proper aspect ratio of (almost) 1.85, but I think these “big” values can cause problems with TVs and other HW because the equipment isn’t expecting numbers that big. The cropped video is 718 wide and 462 high, and with a PAR of 32/27 gives the same aspect ratio as the big numbers above.

(Do these big values 11418 x 6237 seem normal - do they make sense?)

Here is a post where I describe the details with links to work files, etc. Go to the 2 most recent posts at the bottom - August 24.

https://forum.handbrake.fr/viewtopic.php?t=43016

Any insights are very much appreciated. I’m trying to figure out if this is an equipment/HW limitation, an encoding bug, or a lack of understanding on my part. The reason I asked about the options is for the case where it is an equipment/HW limitation or an encoding bug and some repairs would need to be done on older encodes - I’ve already developed a Perl script that uses mkvinfo and mkvmerge and updates the VDW and VDH values based on the “Video Pixel Width” and “Video Pixel Height” from the mkv header. I want know how to handle VDU. Thanks and best…..

[tormento]

I have found this utility.

Is it possible to do the same with "standard" MKVToolnix package?

[Ripman]

Originally Posted by tormento

I have found this utility.

Is it possible to do the same with "standard" MKVToolnix package?

Yes. MKNToolNix is a more comprehensive tool with excellent stability and accessible expertise. That’s the gui version. There are also command line utilities in the bundle so that all operations can be ‘batched’ - mkvinfo mkvmerge mkvextract.

Read the man pages. They are very detailed.

[tormento]

Sorry if it's been already asked but I have searched and not found.

When importing a BD episodic playlist, sometimes there are opening and ending sections for every episode in the middle of the episode itself, before the epilogue or after the prologue.

Besides having the "Before chapters", it would be nice to have a syntax such as "4-5+10-11, 12-13+18-19" or something like that to tell the program to use from chapters 4 to 11 but chapters 5 and 11 and from chapters 12 to 19 but chapters 13 and 19.

I could do it splitting by hand, encoding and joining by hand but I should deal later with chapters, subtitles, etc.

[hubblec4]

cE has such an option to split and join the parts you have mentioned automatically.
BD2mkv -> Split-section
OK, there you can only enter time stamps, not chapter numbers.

[tormento]

Originally Posted by hubblec4

cE has such an option to split and join the parts you have mentioned automatically. BD2mkv -> Split-section
OK, there you can only enter time stamps, not chapter numbers.

Thanks for the info and the feature.

Unfortunately, manually inserting time stamps would be a PITA for large BD collections.

[TheEqualizer]

Originally Posted by filler56789

mp4fpsmod?

  -d, --delay <n>       Delay audio by n millisecond.

Is it possible to select a specific audio track to apply the delay (we are talking about when there are several audio tracks in the video), I tried the -map parameter, swears that I don't understand, I can't find a solution.

[tormento]

I am trying to split a mpls by frames, using 'After frame/field numbers' and in 'Frames/fiels:' I am feeding the values:

951,44243,79459,85791,121017,124634,127241,129940,162576,166176,172438.175137,204104,207714,209988,212687,245555,251865,287078,290673,292920,295619,328600

The resulting error is:

Invalid frame for '--split' in '--split frames

The resulting CLI is:

mkvmerge.exe --ui-language en --output ^"N:\Raw\26-00017.mkv^" --language 0:en --language 1:it --language 2:ja --language 3:it ^"^(^" ^"N:\Naruto_BD26\BDMV\PLAYLIST\00017.mpls^" ^"^)^" --split frames:2698,37951,44243,79459,85791,121017,124634,127241,129940,162576,166176,172438.175137,204104,207714,209988,212687,245555,251865,287078,290673,292920,295619,328600 --chapter-language und --generate-chapters-name-template ^"Capitolo ^<NUM:2^>^" --track-order 0:0,0:1,0:2,0:3

What am I doing wrong?

[Mosu]

frames: expects a single number, which is taken to mean "split after every n frames".

Try "by parts by frames" or whatever it's called in the GUI; the CLI equivalent: "--split parts-frames:a,b,c,d,…"

[Boulder]

I've been trying to teach the AI to create a simple chunked encoding tool. The basic stuff works fine, but it stumbles upon joining the resulting webm files. Is there a way to feed a simple list of files to concatenate with mkvmerge? I'd rather not use ffmpeg as it seems to cause some issues like repeating frames. The input list would be like:

F:\Temp\Captures\encodes\lotr_fotr\chunks\encoded_chunk_0.webm
F:\Temp\Captures\encodes\lotr_fotr\chunks\encoded_chunk_1.webm

etc. The number indexing is not a problem, that can be adjusted.

[Mosu]

With a shell that expands shell wildcards (e.g. bash, zsh), sure: mkvmerge -o out.webm [ encoded_chunk*.webm ]

[tormento]

Originally Posted by Mosu

With a shell that expands shell wildcards (e.g. bash, zsh), sure: mkvmerge -o out.webm [ encoded_chunk*.webm ]

Your download repository is giving me bad gateway error.

Anyone else?

[Mosu]

Thanks for the heads-up. I've restarted the offending daemon.

[Magister Irrylio]

Will A_MS/ACM support ever be added to mkvextract? I can get around it by just putting it into an mka with mkvtoolnix and then converting that to FLAC with ffmpeg, but it's inconvenient compared to just extracting every track, especially when working with multiple files. Don't really see why mkvextract can't simply extract it.

[Mosu]

I'm not interested in implementing it.