MKVToolnix VS tsMuxeR

Fourth, try remuxing one of the problem files. Use the Multiplexer section of MKVToolNix. This will copy the contents to a new MKV file. It is like putting a letter in a new envelope when the original is damaged, but the pages inside are OK. Source: 5 months ago

If the audio tracks are displayed as unknown, the language flag needs to be set. Use tools such as MKVToolNix Header Editor to configure the language for audio & subtitle tracks. Source: 10 months ago

As for extracting tracks from MKVs, the low-level way would be to use ffmpeg directly (something like ffmpeg -i video.mkv -map 0:s:0 subtitle.sup would extract the first subtitle stream to a .sup file, the extension used for standalone PGS subtitles), but something like MKVToolNix can probably do it as well. That won't help you too much on its own though, since you now just have an external image-based subtitle... Source: 10 months ago

You could use a tool outside of Plex (like MKVToolNix) to combine the video+audio of one version with the audio+subtitles of the other. It gets trickier, or at least more tedious, if the videos aren't exactly the same, since you'd then have to account for any audio/subtitle shifting. Source: 10 months ago

Option 3: Change to MKV container. Use MKVToolNix or similar tools and remux to a MKV container. Note that this may cause problems with Dolby Vision. LG TVs must have Dolby Vision in a MP4 container, otherwise the video will not play correctly. Probably affects other Plex clients as well. Source: 10 months ago

Dolby Vision supplements the HDR data already present in a video. For example, when you buy a Blu-ray disc that supports Dolby Vision, the disc contains several m2ts files containing HEVC encoded videos. Present within the HEVC stream is also the metadata, which supplies metadata for each frame. To see what this data is, I used[1], and then got the info for frame 1000 and saved it as a json in this [2] pastebin.... - Source: Hacker News / over 1 year ago

Clsid has continued to maintain MPC-HC after the original development team stopped due to a lack of interest back in 2017 (v1.7.13 being the last release). See: https://forum.doom9.org/showthread.php?t=175209. - Source: Hacker News / almost 2 years ago

Anecdote: I'm typing this on a 2013 Xeon (Haswell E3v3), and it's acceptable for web/productivity, but the x265 encode performance is absolutely abysmal compared to newer CPUs, especially AMD's. GPU encoding is good for ephemeral streams, but good archival encoding is all CPU-bound: https://forum.doom9.org/showthread.php?p=1908148#post1908148 """Luckily""" for me I do mostly standard-definition encodes and can get... - Source: Hacker News / almost 3 years ago