DTS X Passthrough

[Mahinepua 81]

Send it through, pretty sure its just a flag for DTS-HD that hasn't been configured properly in the new player. 

Ive tried a number of DTS-HD bluray and 4k remuxes none pass DTS-HD.

[Guest]

I'm attaching a preconfigured mpv. Just unzip the folder to your desktop. Launch mpv.exe and drop your video on it. What are the results?

 

mpv.zip

[Mahinepua 81]

works perfect!

[Guest]

Well, that would imply there is a bug in the Emby build/config somewhere. I wanted to rule out that it was an mpv bug.

[Mahinepua 81]

Can Santa Softworkx duplicate your settings in the new player?

Edited December 24, 2024 by Mahinepua

[Guest]

1 minute ago, Mahinepua said:

Can Santa Softworx duplicate your settings in the new player?

He's going to have to check things on that end, and find where the fail point is. Could be config, could be build...

[Mahinepua 81]

Thanks for your help and have a good Christmas the both of you.

[Guest]

If you're testing DV, open the mpv.conf in portable_config. At the top, delete the line target-colorspace-hint=no. If you have Windows HDR enabled, the windows compositor will upconvert the tone-mapped DV into HDR10

[softworkz 5066]

33 minutes ago, Mahinepua said:

Can Santa Softworkx duplicate your settings in the new player?

Sure, please give it a little time, though.

[Guest]

This might simply be a typo, and missing a hyphen 

  AudioPassthroughFormats: AC3,EAC3,DTS,TrueHD,DTSHD

instead of this

  AudioPassthroughFormats: AC3,EAC3,DTS,TrueHD,DTS-HD

 

[Mahinepua 81]

I think your correct! Softworkz is probably on his 4th beer by now though lol

[softworkz 5066]

6 minutes ago, generiq said:

This might simply be a typo, and missing a hyphen 

  AudioPassthroughFormats: AC3,EAC3,DTS,TrueHD,DTSHD

instead of this

  AudioPassthroughFormats: AC3,EAC3,DTS,TrueHD,DTS-HD

The docs say otherwise:

I had dtshd originally as that's what the old app had and it didn't work, so I had double-checked with the docs, changed it to dts-hd as described and the user had reported it as fixed.

 

[softworkz 5066]

Forget about it. I see the error. 

Will be fixed in the next update.

Thanks

[Mahinepua 81]

It still says dtshd not dts-hd.

are you sure you changed it?

[Guest]

6 minutes ago, softworkz said:

The docs say otherwise:

I had dtshd originally as that's what the old app had and it didn't work, so I had double-checked with the docs, changed it to dts-hd as described and the user had reported it as fixed.

 

You're confirming what just said. The top log quote is directly from the log. The second quote is my correction. As you say, dts-hd is correct, but it appears that dtshd is waht is being applied 

Edited December 25, 2024 by generiq

[Mahinepua 81]

Softworkz was saying dtshd is incorrect documentation shows this should be dts-hd

[softworkz 5066]

It's defined correctly, but the conversion from the enum string to the value attribute was missing in this case

So, yes you were right.

Thanks

[Guest]

Just now, Mahinepua said:

Softworkz was saying dtshd is incorrect documentation shows this should be dts-hd

And is exactly what I said and showed

[Mahinepua 81]

Oh easy fix then. Can this be updated manually without a formal release? Heading to the holiday home tomorrow 

[softworkz 5066]

5 minutes ago, Mahinepua said:

Oh easy fix then. Can this be updated manually without a formal release? Heading to the holiday home tomorrow 

Sorry, but no. All the big things have been addressed just in time with huge effort. 

But this isn't a big issue for once; also you've been part of the beta, where you had more than two months to report it, so I'm really afraid, but it will take a while until we'll push the next version.

[Mahinepua 81]

All good have a good holiday you’ve deserved it.

[Mahinepua 81]

The Truehd bug is also still present, bitstreaming audio drops out after ff/rw and stops completely on some movies at certain points, avatar 2 is one example.

Will link the mpv github post, I think some sort of buffering or padding might fix it, a custom mpv build resolved it but I understand it’s an ffmpeg bug.

Something to look at after the dts-hd fix.

[softworkz 5066]

DTS-HD is fixied in the next update.

Thanks