LG OLED 77C9PLA can´t direct play

[Morphoiz]

Server Version#: 4.22.3 (running on a Windows 10 machine)
Player Version#: 4.29.3
webOS#: 4.7.0

Hi guys,

I bought a new LG OLED 77C9PLA couple weeks ago and I have problems with direct play since then. Right now I´m not able to “Direct Play” my 4K HDR ripped Blu Rays on the TV. The PMS always tries to transcode it. See:

One sample file that cant be “Direct Played” is:

The strange thing is that it already worked without a problem - but In my opinion nothing changed. (network wise → connected with a cable, tv wise etc.)

Can anybody check the log files and see what the problem is? Although Í´m not sure which Log Files exactly are needed for that problem. Just contact me.

Thank you in advance!

[SE56]

Hi,
in your second screenshot can you please scroll down to the Audio part and post that please.

The video should play without issue, my guess you have some HD-MA audio

[Morphoiz]

Thanks for your answer. Here is the Audio Codec Information:

(this is the audio I choose)

I can upload the whole XML file if that is any help. The weird thing is I tried to watch the same 4k file and “Direct Play” worked today. Yesterday it didnt. Definitely nothing changed, I even made an speed check with an Laptop connected to the network port to see if I reach the full GIgabit Speed - no problem there. (copied an file from the NAS to the Laptop)
Unfortunately I’m not able to reproduce the problem.

Any help appreciated.

[SE56]

That audio should play without issue, so are subtitles used they can be troublesome

[Morphoiz]

So, do you have any idea why the playback is working so unreliable even though all requirments are fulfilled? (no subtitle is activated, just video and audio)

[Morphoiz]

After a lot of testing I found the solution. It was not a client specific problem, but a server configuration problem. The following setting under “Settings” --> “Network” was the problem:

When it’s activated I can “Direct Play” on all devices. Might be a problem with my Layer 3 Switch in use, not sure yet. Tested the described behaviour with the setting activated/deactivated and it always worked.