Dolby True HD and DTS-HD MA

[bnwbass 3]

Simple Question, media -info shows the audio format in my Emby library  as Dolby True HD and DTS-HD MA.  However,  Emby server home  view for these files displays as DTS 5.1?

See attached.

Edited January 5, 2020 by bnwbass

[Luke 42083]

Hi, that's what ffprobe told us. Are you experiencing a problem? If that file was scanned in a long time ago, try refreshing the metadata. Perhaps it might be different now when getting scanned in by a newer server version.

[Deathsquirrel 745]

Hi, that's what ffprobe told us. Are you experiencing a problem? If that file was scanned in a long time ago, try refreshing the metadata. Perhaps it might be different now when getting scanned in by a newer server version.

 

Not in my experience.  Files I ripped this weekend and added this morning show as having DTS-HD in the media info section at the bottom of the page but the audio dropdown at the top of the page shows DTS.  That's with server 4.3.1.0.

 

I checked ET 3.0.10 and it does the same thing.  The audio track chooser there shows DTS instead of DTS-HD.  Ditto for the Android TV client v 1.7.69g.

 

EDIT--Correction, looked back at the media info and it all matches up with the Title value.  The title of the DTS track in the media section says 'English DTS Stereo (Default)' which is what shows up in the audio track chooser at the top of the page in the browser.  The PROFILE value is what says 'DTS-HD MA'.

 

Perhaps there is a FR there to label the track differently in the audio chooser if the profile is DTS-HD.

Edited January 5, 2020 by Deathsquirrel

[Luke 42083]

Ok yes there's room for some improvement here. Thanks for the feedback.

[bnwbass 3]

Yes, I ripped today so these are recent and still show miss-match format between the source and Emby.  Also confirmed that Android device shows the same as Emby server.

Is there a fix? Do we know if the audio track is indeed coding to the correct format and that Emby is not downgrading to the default 5.1 format?

[Luke 42083]

Nothing is being downgraded. Thanks.

[Deathsquirrel 745]

Yes, I ripped today so these are recent and still show miss-match format between the source and Emby.  Also confirmed that Android device shows the same as Emby server.

Is there a fix? Do we know if the audio track is indeed coding to the correct format and that Emby is not downgrading to the default 5.1 format?

It's definitely sending the correct audio formats, assuming your devices all support them.  I can see that on my receiver.

[Luke 42083]

Yes it's just a display problem. We'll look at it. Thanks.

[SikSlayer 249]

It's been that way for a while (especially with Blu Rays I notice it, but any format really), but I assumed it was more ffprobe than anything else.

I should have reported it anyway. Probably could have been fixed by now.

[SikSlayer 249]

It's much improved in 4.4.0.6. Is there no way to implement this for UHD Blu Ray folders?

I remember being in on a discussion on that, that has never worked.

[Luke 42083]

Is there no way to implement this for UHD Blu Ray folders?

We're not really able to allocate much dev time towards these. For the best experience possible I would suggest converting to mkv.

[SikSlayer 249]

We're not really able to allocate much dev time towards these. For the best experience possible I would suggest converting to mkv.

 

It's already there for Blu Ray, its it really that much different?

Also, what abut the languages for the PGS subs? It's just marked as undefined, but many open source apps can show the language...

[Luke 42083]

We use ffprobe which does not have native support for bluray folders.

[softworkz 5073]

For normal (non-bluray-folder) media files, an ffmpeg transcoding log might be helpful to see as these show a significant part of the same information that ffprobe sees.