why only DTS?
Closed this issue · 2 comments
You could replace "audio (A_DTS)" with "audio (A_DTS)|audio (A_AAC)" check in greps or add some switch and cover also AAC5.1 that is not supported by many devices that not support DTS.
Agreed, but then we would need to change the name of the script! :)
There is also the challenge of finding a cmdline tool that converts AAC. As it stands, we have to use several programs for DTS conversion to AC3 and finding AAC to AC3 could be problematic. The industry went through a phase of choosing not to support DTS and this was a specific tool to support the need to convert that format to something that is generally supported.
Almost everyone (Almost) has moved on and have a player that supports modern formats which is why neither Jake nor I use this program and mostly don't support it anymore. We get very few comments anymore which is why I make the bold statement that almost everyone has moved on to a more modern player/solution with support for DTS, AAC, Dolby Digital, etc.
The player I was using, WDTV 1st gen, is long gone replaced with a WDTV Live Plus. However the 1st gen WDTV did support AAC but not DTS; hence the support for DTS conversion at the time.
The script does DTS conversion because DTS decoding requires a license fee for hardware solutions. Other codecs, whether it be AC3 or AAC or the like, are either open source or freely available for implementing.