-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DTS-HD Audio not recognised or processed #107
Comments
I was able to get my specific file to work by manually specifing the track ID, and by commenting out lines 427-432, but this is of course just a workaround. |
Yeah, DTS-HD wasn't even a glimmer when this script was created (6+ years ago!) so it was never designed to be more robust for future DTS tracks. However, in theory you should just have to remove the ')' from line 408 (and maybe 425) and it should cover all DTS tracks. Untested though... I continue to be surprised people still need this function, DTS conversion to AC3, since there are so many modern devices that play DTS just fine. Not degrading, just reflecting and amazed that the need is still there. |
Same. I haven't needed this script in 6 years! On Thu, Dec 24, 2015 at 11:42 PM Chris Hoekstra [email protected]
|
Well, what can I say? My parents' relatively new "smart" TV seems incapable of reading DTS audio in any of its forms, so it has been a bit of a mad rush to find something that can automate the arduous process of reencoding and remuxing. @choekstr I'll try that out later. Merry Christmas, everyone! |
It might also be worth mentioning that "TrueHD" is an increasingly common audio format which is of course also not recognised by this tool. |
@choekstr More robust solution may be to just change line 410 pattern match fr
to
Am I missing something? Will the processing engine still work with DTS-ES tracks to convert to AC3? (I still need to use this because Sonos Playbar does not support DTS still even though it's 2018) |
actually just removing the ) would do the same thing but as the string keeps changing, both for different variants of DTS like ES, HD, etc, but also for other ways of writing the track moniker. With all the testing we did back when this was actively developed the string matched as it was the only thing that ever showed up when a file was queried. But there are 2 parts to this: MATCHING BY SCRIPT CONVERTING VARIOUS DTS FORMATS |
You might get a few more new users (like me!). Samsung have dropped DTS support for at least some of their 2018 TVs: https://developer.samsung.com/tv/develop/specifications/media-specifications/2018-tv-video-specifications
|
I have some files I'm trying to convert which have DTS which can't be read by our TV, but some have instead "DTS-HD" audio. mkvmerge -i output gives
Track ID 1: audio (DTS-HD Master Audio)
for example.Assuming it's still within the intended scope of the program (I'd expect so), it should probably consider these also as tracks needing re-encoding and replacement. As far as I can tell, there's no way to force these tracks to be reencoded by this tool.
The text was updated successfully, but these errors were encountered: