-
Notifications
You must be signed in to change notification settings - Fork 160
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
Differentiating DTS:X and DTS-HD MA for IMAX enhanced movies (special variant of DTS:X) #422
Comments
Detection of DTS:X is from empirical checks, as I have no spec. |
I emailed you a sample that is not being detected as DTS:X MA on MediaInfo 19.09. It might be related to some new spec/slight changes in the last couple of months. I just noticed the same issue with the 4k disk of Jumanji Next Level |
If it helps, prima facie, it seems like the commonality between these disks is that they are all |
And I thought it was me! Drove me crazy. Jumanji TNL is indeed detected as DTSHDMA 7.1 and not DTS-X 7.1. I checked Phantom Thread and that one shows DTS XLL X properly. I dont see mine as being IMAX enhanced though. |
Any update on this? Mainly, were you able to also replicate/see the issue, or am I and loungebob just going crazy? |
I have some urgent paid support to provide before checking this issue. For speeding up the check on my side:
Please provide a version number about when it is detected. |
No worries, that makes sense. I think I was not fully clear. No version of MediaInfo that I tested seems to be recognizing this file as DTS X. Actually, what I was saying is that MediaInfo version 19.09 does recognize |
I was going to report this, good thing I checked first. |
Might be worth sending him an email with it. Not sure if my sample was very good. I definitely notice this specifically with IMAX enhanced movies with DTS X tracks. It is a special variant
Source: https://www.highdefdigest.com/blog/imax-enhanced-dts-audio-format-debut/ |
The more is the better, in order to have more chances to understand how it is "hidden" in the file. The best would be at the minimum to have DTS provide their specs as Dolby does... |
I sent you an email. I've uploaded the entire track as I didn't know if spliting it would mess with something, so to be completely sure I didn't do it. |
DTS has standalone frames, anyway it can be useful to test all frames so thanks for the complete file. |
Thanks for working on this, no pressures here. |
Was any progress made on this? I can provide some interesting samples if that would help (Imax Enhanced and high object count DTS:X) |
Not sure if it is best to raise a separate issue but there are some normal DTS:X tracks which do not detect: All of the above are detected fine by my receiver but Mediainfo thinks they are plain DTS HD. |
@Krobar please few frames of each file, work on that is still stalled but having more files would be better when I decide to work on that, especially because for the moment I see only reverse engineering as a possibility, I didn't find any spec about that. |
@Krobar appreciated. |
@JeromeMartinez I'm seeing what I believe is a strong pattern on what is and is not detected as DTS:X by MediaInfo. If the media contains DTS:X with Fixed Channels and no objects then it detects OK. If the media contains DTS:X with objects (Regardless of if fixed channels are included or not) then it fails to detect. |
Detection of DTS:X is by reverse engineering, with some byte patterns. so I guess they changed a bit the bytes with objects. |
You might want to check if Whisky Tango Foxtrot and Zoolander 2 have the same pattern as they were likely authored by the same people. |
Can confirm that the DTS:X track from Independence Day 4K 20th anniversary edition does not get detected as DTS:X from mediainfo as of version 22.09. |
No change there, we didn't check by reverse engineering or so. Is it detected by any other open source software? |
Not that I know of. |
@Krobar @loungebob @acedogblast @rg9400 @parasiteoflife @alexdns1: We implemented parsing of the XLL addition (DTS-HD MA) in order to catch the end of the bitstream (and the real lossless bit depth, by the way) as specified in latest available spec and probe the bytes next to the end of this known bitstream, then we check for "magic values"; it is reverse engineering and empirical tests, we found 2 magic values (1 bit difference) in the streams we found for IMAX, so maybe there are maybe more streams not caught with that. Also, we are a bit lost in what is what, you know better than us. Current implementation: DTS:X:
IMAX Enhanced:
Does it make sense? i.e. is it true that IMAX version is not compatible (DTS:X non IMAX plays only the DTS-HD MA, not catching any DTS:X)? is it true that DTS:X is object based and IMAX Enhanced channel based? It removes the count of channels from the legacy layer because we want to show data from the most advanced detection (and we don't have the count of IMAX, only from DTS+HD MA), but DTS-HD MA channel count will come back in a later patch, more general about legacy layers? |
I believe your labeling is wrong
No you fallback to DTS-X on compatible sink devices
DTS-X is DTS HD MA with object based tracks on top
That statement means that the max DTS-X 2 or 4 object channels which is 7.1.4 or 9.1.2. While TrueHD Atmos can do 17 ? i think object channels
No there are lots of DTS-HD MA 7.1 tracks without object channels so they are not DTS-X
DTS-HD MA spec is up to 7.1 - anything above that is DTS-X for sure
IMAX doesn't add any additional channels... Channel(s) : Object Based Instead of displaying "Object Based" can you display the DTS channel count + Object Based |
"Magic values" are very different (0x02000850 for DTS:X vs 0xF14000D0 for IMAX), I guess that there was some provision for legacy DTS:X not IMAX, so OK I flag that as "X IMAX" until someone says that their IMAX thing does not work on their DTS:X non IMAX decoder.
Technically it seems that there is no such limit for MA. I am interested in a sample stream with 9.1.2 channels.
This stuff makes me crazy, there is more marketing stuff than anything technical...
This is what is already used for DTS:X not IMAX, but now I check Dolby Atmos and I see that the display does the difference between "classic" stream and the object parts, with a "Bed channels" line, so for the moment let's keep the "classic" stream (core+MA) channels. New version: DTS:X:
IMAX Enhanced:
Wondering... DTS-HD MA is lossless, is DTS:X or IMAX lossless too? |
DTS HD MA max technical channels are 8 in a 7.1 configuration. There is no object audio on it - that is DTS-X
Well they need to sell stuff to people that have already perfectly working receivers/sink - they cant otherwise
Yep that works great !
Oh boy you are in for a treat ! |
They use the same commercial name for so different things... even worse that they use DTS-HD MA (so lossless) as the base for then lossy stuff. |
Its about how they are encoded and from what source. You can encode DTS HD-MA or DTS-X in any bitrate you like |
Could you share some audio frames of this "lossy" streams? I am curious to see how XLL extension is used in that case (XLL is supposed to be lossless... Maybe they just ignore the lossless part and jump directly to the "X" part, I would like to see that). |
@JeromeMartinez sorry i dont have any DTS-X IMAX streaming releases but i will ask around to see if i can come up with something for you |
I've tested with some movies and it detected the tracks as:
In the current stable release they are detected as:
There is definitely an improvement. I've only tested the movies I have and that I found in this list, it seems most releases go with Dolby. Thanks! |
FYI, due to #710 I refactored some code and cleaned up the DTS output. In order to keep track of what is "under" DTS:X, I keep now the underlying commercial name.
Hope it is coherent with what your AVR display, else please report incoherencies. Development snapshot: Windows, macOS
Added. |
This isn't fixed completely; only for some movies. The designation is wrong for some other files: https://drive.google.com/drive/folders/1pq5XC9P9Isw-IAkriikHl4p8t_IjNxxC?usp=sharing These files will only be hosted for a bit. Please tell me when everyone's acquired them. Jumani: The Next Level is correct: I have four other movies with IMAX Enhanced that I can clip for you to test with. Those all show up correctly. This is from a DTS demo called Between Zero and One: The Trinnov receiver company sent me some demos. They are Dolby Atmos, DTS:X, and DTS:X Pro. For some reason, the DTS:X Pro files only show regular DTS:X on my receiver, and MediaInfo doesn't know what to do with them: My receiver is a Marantz AV 10. It has support for IMAX Enhanced and DTS:X Pro. DTS:X Pro supports more than 11 channels which is good because my receiver has 15 channels + LFE. I'm not sure if DTS:X Pro is supposed to show up on the receiver though. My thinking is it just means you have more base layer channels available; I don't think it's a different protocol than DTS:X though. |
Do I need to post this same data somewhere else? Since this ticket is closed, it might not get the same view as open tickets. |
Sorry, I have delay in managing tickets., still on my todo-list. |
Thanks! Just didn't wanna have this info get lost. |
Mediainfo version 19.09
I noticed that a lot of recent 4k releases have DTS:X tracks, but when I rip them and check the mediainfo, it is identified as DTS-HD MA with no discernible difference in the mediainfo between that and an actual DTS-HD MA track. I did check older releases, and they do have the proper
XLL X
parameter listed.I had this tested via playback on a Denon receiver, and the receiver did pick up
DTS:X MA
as the codec. The movie isCharlie's Angels
though I noticed similar behavior forA Beautiful Day in the Neighborhood
andZombieland Double Tap
as well. Listing the full mediainfo for the file below.EDIT: IMAX enhanced movies are using a special variant of DTS X that MediaInfo is not able to currently recognize.
Source: https://www.highdefdigest.com/blog/imax-enhanced-dts-audio-format-debut/
The text was updated successfully, but these errors were encountered: