Yes I checked all the cables but it does not make a difference.
I played a blu-ray with DTS-HD Master audio on my ps4 pro, it worked fine.
Haha, no worries, I am really at the end of my ideas how to tackle this issue. So all your help is very much appreciated!
So setup is NEO U9-h --> soundbar LG SK10Y --> TV LG OLED65C8
Sound setting of the OLED65C8 are:
Sound output HDMI ARC, digital sound out, automatisch (only other option is pcm)
DTV audio-setting, automatic
AV Sync-adjustment, off
TV speakers are definitely disabled. The soundbar settings are quite limited. there no seem to be no options for choosing. For example when I run the Core Universe.m2ts on CoreELEC, the SK10Y recognises Atmos, shows that in the display and I cannot even change sound effects.
By the way, again something I cannot make sense of. I just tested Netflix' 6 underground (Dolby Vision and Atmos) straight from the tv app, while the Minix was turned off. On soundbar I chose Input source / Function ' OPTICAL/HDMI ARC'. The display switched automatically to 'OPTICAL' (I had no sound). Then I turned on the Minix, the soundbar switched automatically to ARC. When I pushed the information button on the remote I expected to see Atmos on the display of the soundbar, however it showed Dolby digital. I turned off TV, soundbar and Minix. Then turned on tv and soundbar (not Minix). Now the soundbar display says ARC and when information button on the remote is pushed it says Atmos.
You're welcome
. Just a shame there doesn't seem to be an obvious answer to this one
. (At this point, I'd be banging on LG's desk myself, so to speak
.)
When did you purchase the LG SK10Y? (A more extreme solution, but if it was quite recent you could consider returning it for another brand/model, or even pick up a decent mid range AVR for less than half of the SK10Y's original retail mark up. (Depending if you already have some half decent speakers too, you could also use them & add to them later, or build up a 5.1.2 system to accompany an AVR as you go/cash flow allows etc.))
Otherwise, the behaviour you've mentioned does make sense. (Obviously, because you're just using HDMI & no TOSLINK cable is required you'd also expect the optical audio option not to function with all else being correct.). You'd also expect the soundbar to enter ARC mode if it's just detecting the TV alone without any other active HDMI devices being present/powered on. So that part all seems fine.
When you power on the U9-H the soundbar should simply report detecting 2.0 PCM only for the default system sounds & most apps etc., (unless of course said apps can specifically support additional audio channels/passthrough such as Kodi). It's only when you bitstream RAW audio via passthrough that the soundbar should switch from PCM to the respective audio format that requires decoding.
Did I ask if you'd tried an older version of Kodi or a Kodi fork with the U9-H & Android? (You could try quickly installing 17.6 just to see if this is a weird glitch with Kodi 18.x.)
There are a couple of other things you could try adjusting with the U9-H, although usually they just wouldn't affect the audio side of things as you've been experiencing, but still...
...In the U9-H's settings, just turn the
CEC switch only
on if it wasn't already, but leave the other 3 CEC options disabled, (at least initially), then test again. Additionally, you'll also see an option called
playback settings, in there you'll see some options for the
HDMI self adaptation but these are typically for the visual aspect for apps to correctly switch between different display resolutions, (but again, just in case). Try setting that to
level 2, level 1, or off respectively & test again trying each one in turn. (I wouldn't expect it to make a difference in this instance but you really have nothing to lose by trying it. (FYI, my hardware works best using level 2 but the different options are obviously there for a reason.)
I understand you've been endlessly trawling through your TV & soundbar settings of late
!! But, have you also tried initiating any media on the U9-H encoded with TrueHD or DTS HS MA, & then whilst that media is actively playing go back through all of the available settings again in case something only pops up in a menu somewhere just when that media is playing that you possibly haven't seen before. (Certainly worth trying too if you hadn't already.). Then check Kodi again to see if the options suddenly appear.
When you have the PS4 Pro actively gaming/processing media, presumably the soundbar doesn't just decode DTS HA MA correctly, but the soundbar is also correctly decoding/switching between any of the different SD/HD audio formats as expected from the PS4 Pro too?
I'd also definitely enter a support ticket with LG at this point as there really is no normal explanation for why either Android or CoreELEC would behave as they are in conjunction with all of your LG hardware & it's not exactly cheap kit either. Not to mention, the SK10Y was LG's flagship soundbar in the not too distant past & as such it really shouldn't be suffering any incompatibility issues such as this!! (I'd be pretty frustrated if I purchased it to find it wasn't working as intended. There are also literally countless folk out there using the U9-H with a huge range of different AVR's, soundbars or other external audio hardware that all function as expected, it is well proven. I'm not saying all hardware will always function together with an absolute 100% guarantee, but the U9-H definitely supports what you're trying to do & as far as I can see your LG hardware is relatively new kit too that should also be functioning normally in this regard as well.)
If it helps too, include a link to this thread in your support ticket to LG so that they can see exactly what measures you've already gone to, to get this all working properly. Also, that you've obviously covered everything you possibly can as far as the actual output source is concerned & everything is correctly configured there too, and/or you've even been through the painstaking process of extensive troubleshooting & even factory resetting the source device already. (That may well be LG support's immediate & default suggestion but hopefully it could save you some time & arguments with their internal system if you've already been there.)
Keep us in the loop of what's happening as you never know, someone else could eventually pick up on your posts that may have seen the same thing or similar who may also have been through a long list of troubleshooting & eventually sorted it all out.
Finger's crossed
.