Homatics Box R 4K Plus

Homatics, See the Headline. As I said, it works on Android but not on CE. In Kodinerds Forum we have the same discussion, for some (Dune)it works for some not.

In the shield of course its works. The homatics atv firmware missed the dtshd dts-x codec. Will coming in the future…

@mark5564 as I said, not possible under atv . There is no passtrough for that.

ohh ok i see thank you for the explanation :slight_smile:
So CE works and Android will follow :smiley:

It works with the Marven Build based on Alpha1 , I just setup kodi-21.0-Omega_alpha2-armeabi-v7a and DTS-HD is not working but Dolby Vision.

This are the Dune HD Media Center specifications

Dolby and DTS formats: Audio tracks in the following Dolby and DTS formats can be played: Dolby Digital, Dolby Digital Plus, Dolby Digital Plus with Atmos, Dolby TrueHD, Dolby TrueHD with Atmos, DTS, DTS HD HRA, DTS HD MA, DTS X. All formats can be decoded by the media player and output to HDMI as multichannel uncompressed PCM (up to 7.1 channels, 48KHz). The following formats can be output as a bitstream: Dolby Digital, Dolby Digital Plus, Dolby Digital Plus with Atmos, Dolby TrueHD, Dolby TrueHD with Atmos, DTS. Dolby formats can also be output as multichannel-audio using Dolby MAT technology (multichannel PCM with Atmos) when the receiver supports it.

If it doesn’t work for CE only then check your audio settings.
https://wiki.coreelec.org/coreelec:audio
You should use AVR HDMI (HD Audio)[4] settings and set HDMI Multi Ch PCM as audio output device and HDMI in passthrough settings.

1 Like

I have set everything except the channel selection, I thought with Passthrough this would not be necessary, but anyway, it does not work. Would a log file bring light into the darkness?

Yep, please upload both kodi and dmesg log after this file playback and file sample on some file sharing resource.

kodi.log (958.5 KB)

So I hope I did it right, in the link you can find the file to download.

Your log is from Android, not from CoreELEC.
https://wiki.coreelec.org/coreelec:debuglogs

http://ix.io/4zDE

21.0-Omega_nightly_20230505

You should use something much newer!

I’ can but it’s the same result.

kodi.log (838.1 KB)

Only in txt, becouse URL logfile it failed .

Your test file is working on my Homatic box and in kodi log all looks ok

2023-07-03 11:11:47.835 T:1121     info <general>: CAESinkALSA - Use card "hw:0" and set codec format "DTS-HD MA"
2023-07-03 11:11:47.838 T:1121     info <general>: CAESinkALSA - Set Spdif to HDMITX to "Spdif_b"

What about dmesg log?
And how is you AVR connected? Directly to the box or via EARC?

I don’t know how to make a dmesg log. Via E-Arc

Dolby Digital, Dobly Digital Plus, Dolby TrueHD, Dolby Atmos,
DTS Digital Surround, DTS-HD HRA, DTS-HD MA, DTS:X, IMAX DTS,
IMAX DTS:X, PCM

dsmg log

http://ix.io/4zE7

Update is on hold and is postponed at this moment, reported by Homatics, there seems to be an issue with slow boot with the V5310 build (although we as V5310 users didn’t noticed at all, I know I didn’t).

Edit: fixed and pushed again :+1:

please help, I go all steps but when I run in ssh ir-keytable -a /storage/.config/rc_maps.cfg -s rc0

I get this errors:

' not recognised, no mapping for scancode 0x041d022e
' not recognised, no mapping for scancode 0x041d0206
' not recognised, no mapping for scancode 0x041d0204
' not recognised, no mapping for scancode 0x041d0211
' not recognised, no mapping for scancode 0x041d020c
' not recognised, no mapping for scancode 0x041d020e
' not recognised, no mapping for scancode 0x041d024d
' not recognised, no mapping for scancode 0x041d020a
' not recognised, no mapping for scancode 0x041d0208
' not recognised, no mapping for scancode 0x041d024c
' not recognised, no mapping for scancode 0x041d0201
' not recognised, no mapping for scancode 0x041d0250
' not recognised, no mapping for scancode 0x041d0202
' not recognised, no mapping for scancode 0x041d0203
' not recognised, no mapping for scancode 0x041d021f
' not recognised, no mapping for scancode 0x041d021e
' not recognised, no mapping for scancode 0x041d0218
' not recognised, no mapping for scancode 0x041d021a
' not recognised, no mapping for scancode 0x041d021b
' not recognised, no mapping for scancode 0x041d0214
' not recognised, no mapping for scancode 0x041d0216
' not recognised, no mapping for scancode 0x041d0217
' not recognised, no mapping for scancode 0x041d0210
' not recognised, no mapping for scancode 0x041d0212
' not recognised, no mapping for scancode 0x041d0213
' not recognised, no mapping for scancode 0x04bf0e
' not recognised, no mapping for scancode 0x04bf44
' not recognised, no mapping for scancode 0x04bf43
' not recognised, no mapping for scancode 0x041d0219
' not recognised, no mapping for scancode 0x041d0251
' not recognised, no mapping for scancode 0x041d0215
' not recognised, no mapping for scancode 0x041d0255
' not recognised, no mapping for scancode 0x041d0254
' not recognised, no mapping for scancode 0x041d0259
' not recognised, no mapping for scancode 0x041d025c
' not recognised, no mapping for scancode 0x041d0209
' not recognised, no mapping for scancode 0x04bf0d
Old keytable cleared
Wrote 1 keycode(s) to driver
Protocols changed to
 bpf protocol in /etc/rc_keymaps/protocols or /usr/lib/udev//rc_keymaps/protocols