@azraraktar Your setup looks correct for the file you posted, except that I'm not sure if DTS-HD MA will match "dtshd". To know for sure, one have to look in the log. Search for "Parsing results" and find the one that is for the file in question. If you use the cache (which you probably do), the parsing results might not be logged because the parsing information from the cache is used - if that's the case, turn off the cache and "browse" to the folder with the file, and it should be logged. Then turn the cache on again.
The excerpt from your log doesn't seem to be about this file. If you had included a bit more of the log (further up), it would say which file it was about. One thing that can be slightly confusing in the log, is that because UMS is multithreaded, several things happen at once - so completely unrelated things may come mixed together. The part in the [square brackets] shows the name of the thread, in this case "HTTPv2 Request Worker 3". When you look further up or down for what happened to the "case you are investigating", disregard everything that's not from the same thread. The reason it doesn't look like the same file is that the file in question has embedded subtitles, and the MediaInfo output you posted does not. The reason the file that is being evaluated is being transcoded, is that the renderer isn't configured to support subtitles track 2 (whatever format/type it is, that part of the log isn't there). I have no idea if your TV actually supports internal subtitles or this particular format, but this is also specified in the renderer configuration (both internal/embedded and external/subtitles file are specified separately).
@both The part we DO see in the log, is the least interesting (except for the first line). What happens is that after UMS determines that the file isn't supported (for some reason), it will pick a format to transcode to (Usually MPEG-TS or MPEG-PS). The same "resolving process" will then be performed for the transcoded format, which is what we see in the log. Unless the configuration is completely off, this will always find a match, so that part is something I just skip with my eyes when reading
@mik_s MPEG-TS and MPEG-PS are called (MPEG) Transport Stream and (MPEG) Program Stream respectively. They are different file formats, both often simply using the .mpeg extension. MPEG-TS is capable of much more than MPEG-PS, but a lot is identical too. I guess you could say that a Transport Stream is a kind of "container" that can contain many program streams. In addition, they can carry lots of extra metadata, like repeating "headers" (which makes them stream-friendly as you don't need to read the start of the stream to know what the content is), EPG tracks, encryption/decryption packets etc. MPEG-TS is very commonly used for TV broadcast (satellite, terrestrial and cable), where multiple radio, TV or data channels are all muxed into one transport stream. The tuner will then demux the stream, read EPG and "channel information" and the pick the tracks it's interested in for the selected channel. This channel is then usually a "program stream" within the transport stream. Some times, a program stream will end when one program ends and another one starts, while other times they "merge" different programs (and commercials) into one long program stream. If they use separate program streams for ads (which is really natural, as it's a different source), it would become much too easy to automatically remove them I guess
