DTSX getting reported wrong in Emby?

[BurntTech 6]

I've got the movie serenity that seems to get reported 5.1. While Using VLC Player or mkvinfo i'm able to see there is 7.1 on this mkv file. Is this something I did wrong with the mkv or emby might be using generic text?

 

 

 

[Luke 42081]

Hi, try refreshing metadata on that title and see if our newer ffmpeg build detects it differently. Thanks.

[BurntTech 6]

The image got updated when I did a manual update but the audio reports the same. I'm also wondering if it might be 5.1? bluray.com reports it should be 7.1 and others talk about dts:x.  This is screen shot of what should be the same UHD copy of serenity.

 

Edited July 30, 2018 by BurntTech

[Luke 42081]

Ok then I guess that's just how ffmpeg is detecting it. Future server releases will update ffmpeg again so we should probably re-evaluate at that time. I would not anticipate this causing you any problems other than the display of number of channels.

[BurntTech 6]

Thanks for taking the time to validate mkv wasn't incorrect. I'll check some of my other dts:x movies too.

[Luke 42081]

Thanks for the feedback.

 

@@Waldonnis do you have any files like this?

[BurntTech 6]

I will disclose that I owned the bluray before that had the same folder name before I got the 4k version. I figured the refresh metadata would have fixed any possible issues too.

[Waldonnis 148]

Good question.  I have a couple of DTS:X UHDs to look at (Incredible Hulk and Gladiator, the latter of which is sitting on my desk right now), so I'll copy one and see what's going on.  DTS:X is a bit weird anyway (like Atmos, it's object-based rather than being discrete channels).

[Luke 42081]

Thanks !

[Waldonnis 148]

Found a callout sample while I wait for Gladiator to copy (~20mins more), so I'm looking at that first.  So far, it looks like ffprobe doesn't know how to detect the DTS:X layer and only returns info about the MA layer.  Still, at least for this sample, it does show that the MA layer is 8-channel.
 

I've got the movie serenity that seems to get reported 5.1. While Using VLC Player or mkvinfo i'm able to see there is 7.1 on this mkv file. Is this something I did wrong with the mkv or emby might be using generic text?
 
 

 

Any chance you can load the mkv in MKVToolNix again, scroll over to see the stream details, and post what it says under the "properties" heading?  It should say something like "48000Hz, 8 channels".  I only ask because the name on the track is "Surround 7.1", but that doesn't really mean anything (that's just a label likely based on the original stream detection, but may not be what was copied).  I just want to be sure that it didn't just copy the core (DTS 5.1) rather than the full DTS-HD Master Audio track (which would be 7.1).

 

If you happen to have mediainfo installed, that would be great to see as well (just the audio section; mediainfo does detect DTS:X and breaks out the channel counts and layouts for the core, MA, and X separately).  If not, no worries.

[BurntTech 6]

Here is the property column which shows it has 8 channels. Would it work to test this and see what stats for nerds reports if it can see that stream correctly?

 

[Waldonnis 148]

Here is the property column which shows it has 8 channels. Would it work to test this and see what stats for nerds reports if it can see that stream correctly?

 

 

Huh, wacky, so it's definitely an 8-channel track.  Gladiator's showing 8 channels as well, although ffprobe definitely doesn't know about DTS:X yet and just reports the DTS-HD MA track info:

            "index": 1,
            "codec_name": "dts",
            "codec_long_name": "DCA (DTS Coherent Acoustics)",
            "profile": "DTS-HD MA",
            "codec_type": "audio",
            "codec_time_base": "1/48000",
            "codec_tag_string": "[0][0][0][0]",
            "codec_tag": "0x0000",
            "sample_fmt": "s32p",
            "sample_rate": "48000",
            "channels": 8,
            "channel_layout": "7.1",
            "bits_per_sample": 0,
            "r_frame_rate": "0/0",
            "avg_frame_rate": "0/0",
            "time_base": "1/1000",
            "start_pts": 0,
            "start_time": "0.000000",
            "bits_per_raw_sample": "24",

Here's what mediainfo reports on the same file, just for comparison:

ID                                       : 2
ID in the original source medium         : 4352 (0x1100)
Format                                   : DTS
Format/Info                              : Digital Theater Systems
Format profile                           : X / MA / Core
Codec ID                                 : A_DTS
Duration                                 : 2 h 34 min
Bit rate mode                            : Variable / Variable / Constant
Bit rate                                 : 7 589 kb/s / 7 589 kb/s / 1 509 kb/s
Channel(s)                               : Object Based / 8 channels / 6 channels
Channel positions                        : Object Based / Front: L C R, Side: L R, Back: L R, LFE / Front: L C R, Side: L R, LFE
Sampling rate                            :  / 48.0 kHz / 48.0 kHz
Frame rate                               : 93.750 FPS (512 SPF)
Bit depth                                :  / 24 bits / 24 bits
Compression mode                         :  / Lossless / Lossy

My guess is that there's stream info data from the old BRD copy left in the database for some reason.  A refresh should've taken care of that, but I have no idea why it didn't.  Probably the best thing to try is rotate the logs, do a refresh metadata on the movie, then post the log that includes the refresh so Luke can take a peek at what the server is doing (or thinks it's doing).

[Guest asrequested]

I'm confused by this. DTS-X and Atmos have never been shown in the server. I was under the impression that ffprobe just can't see the metadata. Cinema mode doesn't use Atmos, either. I haven't tested DTS-X. I have a feeling this is why.

[BurntTech 6]

The question I was curious on it was reporting 5.1 instead of 7.1 for DTS-HD MA. I was curious if I had the wrong rip or by updating the movie from 1080 to 4k  copies left metadata for the audio tracks behind.

[Guest asrequested]

Oh, DTS-X isn't the issue, just the channel count?

[Waldonnis 148]

I'm confused by this. DTS-X and Atmos have never been shown in the server. I was under the impression that ffprobe just can't see the metadata. Cinema mode doesn't use Atmos, either. I haven't tested DTS-X. I have a feeling this is why.

 

I was mostly concerned that DTS:X tracks may cause some misdetection or misreporting, so I wanted to eliminate that as a cause.  ffmpeg/ffprobe clearly doesn't know anything about DTS:X yet, but it detects the DTS-HD Master Audio layer just fine and should report an accurate channel count for that layer (in this case, that would be 8 channels).

 

Oh, DTS-X isn't the issue, just the channel count?

 

Yep.  Since they replaced an old BRD remux that had a 5.1 track, I'm guessing that data is still in the database.  The file clearly has 8 channels, though, so it's more about why the probe isn't happening or overwriting the info in the database.

[Guest asrequested]

I'm caught up, now. I was misled by the topic. Ffprobe is likely just going with what the dca decoder utilizes.