04.09.2021, 13:01
To make this clear:
Hybrid is build and tested on Mac OS X 10.16 (download section usually shows the version I used).
If you run Hybrid on an older/newer Mac OS X version is might have problems, like in your case that starting with MKVToolnix v54, Catalina was the minium supported version:
That said, Hybrid does, at least at the moment, not use anything that especially requires MKVToolnix v54 or up.
So one can replace the MKVToolnix.app with the v53 release.
If you do this before the first start of Hybrid, Hybrid will detect the older version.
If you do it afterwards you need to trigger "Config->Tools->Clear all cached tool infos" for Hybrid to reevaluate the tool versions.
---
So what happend in your case was that you used Hybrid on a system which isn't supported by the MKVToolnix version which came with Hybrid.
Hybrid then, instead of a proper version string got:
for the versions and crashed on checking when checking the version info during job creation.
Cu Selur
Hybrid is build and tested on Mac OS X 10.16 (download section usually shows the version I used).
If you run Hybrid on an older/newer Mac OS X version is might have problems, like in your case that starting with MKVToolnix v54, Catalina was the minium supported version:
Quote:* MKVToolNix is now using the C++17 library feature "file system library"csee: https://mkvtoolnix.download/doc/NEWS.md
instead of Boost's "file system" and "system" libraries. For the GNU
Compiler Collection (gcc) libstdc++ this means v8 or newer is required; for
clang's libc++ it means v7 or newer. For macOS this means that provided disk
image will only run on 10.15 "Catalina" or newer.
That said, Hybrid does, at least at the moment, not use anything that especially requires MKVToolnix v54 or up.
So one can replace the MKVToolnix.app with the v53 release.
If you do this before the first start of Hybrid, Hybrid will detect the older version.
If you do it afterwards you need to trigger "Config->Tools->Clear all cached tool infos" for Hybrid to reevaluate the tool versions.
---
So what happend in your case was that you used Hybrid on a system which isn't supported by the MKVToolnix version which came with Hybrid.
Hybrid then, instead of a proper version string got:
mkvextract -> yld: lazy symbol binding failed: Symbol not found: __ZNKSt3__14__fs10filesystem4path16__root_directoryE
mkvinfo -> yld: lazy symbol binding failed: Symbol not found: __ZNKSt3__14__fs10filesystem4path16__root_directoryE
mkvmerge -> yld: Symbol not found: __ZTINSt3__14__fs10filesystem16filesystem_error
Cu Selur