On some compiler versions with some options the previous way seemed to
cause errors wrt. undefined references. So give the variable a fixed
place to live.
Otherwise `qmake` might add compiler flags that aren't understood by
the other one.
Actual issue that triggered this change: on Arch with Qt 6.5.2 no
matter what `CC`/`CXX` are set to, `qmake` always assumes `g++` & uses
`linux-g++` as the spec, adding `-mno-direct-extern-access`. `clang`'s
equivalent is `-fno-direct-access-external-data`, though.
The sampling frequency in cores & in EXSS sub-stream elements may be
different. If a core is present, its sampling frequency must be used
for timestamp calculation; otherwise timestamps as well as the track's
overall duration will be wrong.
Therefore look for a core within the first probing buffer. If one is
found, start processing from there instead of from the first header
found.
Fixes#3602
Currently for raw OBU bitstream input only.
The metadata is present in metadata OBUs with metadata_type = 4.
The format of the AV1 RPUs contains the size bytes, and consists of the original
RPU with shifted bytes, so it must be shifted back to the original payload first.
The method was found in existing vendor Linux kernel codebases.
but not all the other file types MKVToolNix can read. There are two
reasons for it:
1. Even though the file association is registered as `Alternate`,
which should be the lowest one, users have reported that installing
MKVToolNix causes it to take over all file type associations it
supports.
2. Even when changing the association manually afterwards, the icons
the Finder shows for the supported file types are all MKVToolNix
icons.
Fixes#3588.
In order to keep the number of command line arguments low, the GUI
only adds the ones for setting the "forced display" flag if its new
value is different than its previous one. Therefore when deriving
"forced display" = "yes" from the file name the GUI must not also set
the internal "that flag was set" data. Otherwise it'll think the old &
new states are identical, leading it to not adding the appropriate
command line flags.
See #3586.
