Good catch. I've never encountered an DTS-HD file, so overlooked adding it to the TV profiles. I'll add that in for the next version. Since we had been discussing DTS, it didn't occur to me that you had a DTS-HD file. Standard DTS and DTS-MA are both already handled in the TV profiles.
The reason it's commented out on the non-TV profiles is that I created the profiles based on the assumption that an external player will be connected to an AVR, which in most cases will process practically all audio codecs. For the TV profiles, that particular audio codec will need to always be transcoded. The commented line only captures DTS-HD if the video codec is H.264. You should probably alter the line to:
- Code:
<Matches container="*" aCodec="dts-hd" />
That's the way I will be changing the two TV profiles.
In fact, I suggest you add the above line to the 4K TV profile, and not use the 4K Media Player (2016+) profile, since your TV will play MPEG2 video but that profile will transcode it. Actually, I just checked both of the TV profiles and that line was already there. However, I don't think it was located in the best place. Placement within the profile impacted which line is used, and I don't think it was where it should have been. Fixed that as well for the next version.
Thanks for the assistance!
Dan
LG NANO85 4K TV, Samsung JU7100 4K TV, Sony BDP-S3500, Sharp 4K Roku TV, Insignia Roku TV, Roku Ultra, Premiere and Stick, Nvidia Shield, Yamaha RX-V583 AVR.
Primary server: Intel i5-6400, 16 gig ram, Windows 10 Pro, 22 TB hard drive space | Test server Windows 10 Pro, AMD Phenom II X4 965, 8 gig ram
HOWTO: Enable debug logging HOWTO: Identify media file contents