Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
11th August 2022, 17:32 | #1682 | Link |
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,278
|
Mostly because it doesn't do anything with the data stored in the various "addition" blocks (the stuff that corresponds to the CodecPrivate of the base laye, the dvcC/dvvC atoms). For regular, non-DV HEVC it's quite common that the parameter set NALUs are only stored once at the start, and mkvextract tries its best to normalize them so they're present before each and every key frame.
It could do something similar with the Dolby Vision NALUs, but it doesn't yet (as that is simply not implemented). So yeah, for well-formed tracks you only take out and remux somewhere else as-is, the current code should work fine. The edge cases probably won't, though.
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
14th August 2022, 08:52 | #1683 | Link |
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,278
|
MKVToolNix v70.0.0 released
Heyo!
A new small release is ready, mostly fixing two annoying bugs in the GUI's handling of color parameters that unfortunately slipped in in v69. Here are the usual links: the MKVToolNix home page, the Windows installer/portable version & macOS DMG & Linux AppImage and the source code. The Windows and macOS binaries as well as the Linux AppImage are available already. The other Linux binaries are still being built and will be available over the course of the next couple of hours. Here are the NEWS since the previous release: Version 70.0.0 "Caught A Lite Sneeze" 2022-08-14 New features and enhancements
Bug fixes
Build system changes
Have fun 😁
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
15th August 2022, 08:51 | #1686 | Link |
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,278
|
New EXEs that have never been seen in the wild are often the target of false positives.
I create both the 7z and the installer from the same set of compiled EXEs. I compile on Linux. There's no Windows involved in the build process at all. So… yeah.
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
16th August 2022, 17:45 | #1687 | Link |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,297
|
A build question.
When you're building for Linux (we will forget targeting Windows for now). Will --enable-static-qt build QT (or something similar) ? If not, what will it do ? Is --enable-static-qt mandatory for --enable-static ? Or for --enable-static you just need to have installed the proper allready build QT package ?
__________________
My github. |
16th August 2022, 18:02 | #1688 | Link |
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,278
|
If you want to use a statically-linked Qt, you'll have to use "--enable-static-qt".
"--enable-static" compiles all programs as static binaries, requiring all libraries to exist as static libraries. This isn't supported. The option is only present because one user provided a merge request for it. I don't use it, I don't test it, I don't support it.
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
17th August 2022, 08:54 | #1690 | Link |
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,278
|
I only use static Qt libraries for the Windows builds, via the MXE project.
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
17th August 2022, 11:20 | #1692 | Link |
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,278
|
I'm not building with static Qt libraries on Linux. That's what I meant above. I only build with static Qt libraries when I build for Windows. For that I only use MXE.
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
21st August 2022, 20:10 | #1694 | Link |
Registered User
Join Date: Sep 2003
Location: Berlin, Germany
Posts: 3,078
|
https://forum.doom9.org/showthread.p...08#post1972708
Sorry for bringing this up again, but I think I found the issue now... It turned out that the source files are borked, but playing the original .TS files in any player did not reveal the problem. Only after converting the source to .MKV usind MKVToolNix the audio sync was broken. dmMediaConverter to the rescue. It reported THIS in its log: [mpegts @ 076b04c0] Non-monotonous DTS in output stream 0:1; previous: 16190735, current: 16189009; changing to 16190736. This may result in incorrect timestamps in the output file. The solution was to just repack the source with dmMediaConverter (everything in DirectStreamCopy mode) to another .TS file and then use this repacked source file as the input for MKVToolNix. All audio sync errors are gone... Cheers manolito Last edited by manolito; 21st August 2022 at 20:17. |
22nd August 2022, 11:49 | #1695 | Link |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,297
|
@Mosu
Assuming i want to build a Linux release, the same way you do, but from a clean fresh mkvtoolnix repo cloning. My guess is that i have to do the following, am i correct ? Code:
./autogen.sh (is there parameters here ?) ./configure (what parameters are you using ?) rake (is there parameters here ?)
__________________
My github. |
22nd August 2022, 12:14 | #1696 | Link |
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,278
|
Highly depends on which distro I build for, if I build for development, if I try to test certain features.
For releases I build from source tarballs, not git repo checkouts, meaning that you don't have to run "autogen.sh" (that builds the "configure" script, but the source tarball already includes "configure"). "autogen.sh" doesn't need parameters. In general I only add those parameters to "configure" that are required for it to find the required libraries if they're stored in locations "configure" doesn't search in. Ideally I don't add any parameter to "configure". "rake" doesn't need any parameters either.
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
24th August 2022, 02:31 | #1698 | Link |
Registered User
Join Date: Oct 2013
Posts: 204
|
I used MKVToolnix to put a subtitle (SRT) inside a m2ts file, and noticed that as MKV the filesize decreased from 65.1 to 61.9 GB.
By comparing both MediaINFO details from them, can this reduction be explained? m2ts (original file): https://pastebin.com/VuBWVUn8 MKV: https://pastebin.com/r1VSWpXu Is the MKV still "lossless" after I used MKVtoolnix? I only added the SRT. EDIT: I just found this explanation: Is that it? The CONTAINER OVERHEAD of a transport stream is much greater than the container overhead of other formats (MPG, AVI, MKV, MP4). In this way, when you remux from (m2)ts to Matroska, you will ALWAYS get a very-noticeable filesize reduction. Last edited by Perenista; 24th August 2022 at 02:34. |
24th August 2022, 10:19 | #1699 | Link |
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,278
|
Yes. The MPEG (2) transport stream container has one of the highest overhead of all the usual containers. It's really noticeable.
Another possible part of the explanation are filler NALUs. Video streams might contain so-called "filler NALUs" that don't contain any data and are only present to keep the effective bitrate above a certain threshold. As those NALUs are completely superfluous wrt. decoding, they're dropped by MKVToolNix.
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
Tags |
matroska |
Thread Tools | Search this Thread |
Display Modes | |
|
|