Any way to persist HDMI edid data?

pt2339-209 · 29 September 2018 09:01

Hi guys,

my issue is that when vero4k has been rebooted while AVR and Projector are on Standby, there will be no sound and no 24p video until I reboot vero4k again while AVR and Projector are switched on. Apparently, HDMI edid info is read freshly on each boot and when AVR is on standby it will use defaults? Is there any way to persist HDMI edid data? As my devices do not change for years I do not see any reason for readong edid info on each boot.

Thanks!

sam_nazarko · 29 September 2018 19:00

Hi,

Try powering on everything first; then Vero 4K. Then:

sudo cp /sys/class/amhdmitx/amhdmitx0/disp_cap /home/osmc/.kodi/userdata/disp_cap
reboot

angry.sardine · 1 October 2018 12:14

Ooh, I’m glad I found this.

@sam_nazarko, it seems logical to me to cache the EDID automatically: if it powers up and encounters a new EDID with different abilities, it should obviously adapt to them; but if it encounters no EDID at all, it should assume the cached version is still correct (and not change any of the settings) until it detects something.

grahamh · 1 October 2018 15:26

We could do that. Concentrating on getting it to check the EDID immediately before playing some media. Vero is picking up EDID changes as they happen , it’s just Kodi that doesn’t update atm.

angry.sardine · 1 October 2018 15:50

I think it’s correct that it should respond immediately if it detects a different EDID; the problem is what happens if there is no EDID at all, because the Vero 4K+ isn’t connected to anything - or it is, but the thing it’s connected to is switched off.

As it stands, if you reboot the Vero 4K+ with the television turned off, it changes its output resolution to 720p.

So, at the moment, the logic is something like “when rebooting, if I cannot detect an EDID that supports the current resolution, turn the resolution down”; it should be “if there actually is some kind of EDID, and it doesn’t support the current resolution, switch down”.

thegremlinlives · 1 October 2018 16:30

This makes a lot of sense to me.
It would also get around the issue of settings->system->resolution being changed to 720p. As I understand it [edit: possibly incorrectly], even if the EDID is later read correctly, the system/GUI resolution will not revert back to 1080p or whatever it had been previously set to.

sam_nazarko · 1 October 2018 16:39

That’s right. We need a callback mechanism or a way to inform Kodi when this changes.

pt2339-209 · 1 October 2018 18:08

Hi guys, happy to see you are taking care! Wondering why nobody else ever did complain about the current behavior - it’s really annoying. No other device (e.g. blu-ray player or PS4) behaves likes this - it just doesn’t matter in which order devices are turned on.

Looking forward to a fix!
Thanks!

pt2339-209 · 1 October 2018 18:11

Hi @sam_nazarko,

this worked for me, however, only for the video part (24p). As I expected it does nothing on the “no sound” issue. So my idea was to also copy the files “edid” and “aud_cap” from same location but unfortunately it had no effect. Any ideas?

Thanks!

grahamh · 1 October 2018 19:17

we only look for disp_cap.

I wonder how Kodi does this on other platforms?

sam_nazarko · 1 October 2018 20:29

Audio shouldn’t be interpreted by Kodi based on aud_cap or autosetting sane defaults would’ve been much easier

Sam

pt2339-209 · 4 October 2018 18:46

So for audio there is no solution for the moment? I have to reboot vero 4k with AVR switched on to resolve it? No other way?

grahamh · 4 October 2018 19:10

I don’t think ‘no sound’ is an EDID problem. Kodi only looks for ALSA devices and makes choices when you start to play media.

We would need some debug logs to help you with that.

pt2339-209 · 6 October 2018 16:04

Well, but aud_cap file is empty in case of vero is booting when AVR is on standby. Since I have configured pass-through for all possible audio formats I would assume that it refuses playback when output device is (wrongly) assumed to not support it?
Which logs are you asking for exactly?
Thanks!

grahamh · 6 October 2018 16:44

Kodi never reads aud_cap. If you have a look in .kodi/temp/kodi.log you should see this, even if your hdmi cable is unplugged:

17:26:58.521 T:4080894544  NOTICE: Enumerated ALSA devices:
17:26:58.521 T:4080894544  NOTICE:     Device 1
17:26:58.521 T:4080894544  NOTICE:         m_deviceName      : default
17:26:58.521 T:4080894544  NOTICE:         m_displayName     : Default (AML-M8AUDIO Analog)
17:26:58.521 T:4080894544  NOTICE:         m_displayNameExtra: PCM
17:26:58.521 T:4080894544  NOTICE:         m_deviceType      : AE_DEVTYPE_PCM
17:26:58.521 T:4080894544  NOTICE:         m_channels        : FL,FR,UNKNOWN1,LFE,FC,BC,BL,BR,BLOC,BROC
17:26:58.521 T:4080894544  NOTICE:         m_sampleRates     : 32000,44100,48000,88200,96000,176400,192000
17:26:58.521 T:4080894544  NOTICE:         m_dataFormats     : AE_FMT_S32NE,AE_FMT_S16NE,AE_FMT_S16LE
17:26:58.521 T:4080894544  NOTICE:         m_streamTypes     : No passthrough capabilities
17:26:58.521 T:4080894544  NOTICE:     Device 2
17:26:58.521 T:4080894544  NOTICE:         m_deviceName      : hdmi:CARD=AMLM8AUDIO,DEV=0
17:26:58.521 T:4080894544  NOTICE:         m_displayName     : AML-M8AUDIO
17:26:58.521 T:4080894544  NOTICE:         m_displayNameExtra: HDMI
17:26:58.521 T:4080894544  NOTICE:         m_deviceType      : AE_DEVTYPE_HDMI
17:26:58.521 T:4080894544  NOTICE:         m_channels        : FL,FR,BL,BR,FC,LFE,SL,SR
17:26:58.521 T:4080894544  NOTICE:         m_sampleRates     : 32000,44100,48000,88200,96000,176400,192000
17:26:58.521 T:4080894544  NOTICE:         m_dataFormats     : AE_FMT_S16NE,AE_FMT_S16LE,AE_FMT_RAW
17:26:58.521 T:4080894544  NOTICE:         m_streamTypes     : STREAM_TYPE_AC3,STREAM_TYPE_DTSHD,STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTSHD_MA,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_512,STREAM_TYPE_EAC3,STREAM_TYPE_TRUEHD

To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.

So, in summary:

activate the logging
reboot the OSMC device
reproduce the issue
upload the log set either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A
publish the provided URL from the log set upload, here

For your case, please re-boot with your AVR off then turn on AVR and display then immediately try playing a track/video which you know doesn’t produce sound. Upload logs.

Can you also confirm ‘no sound’ applies to GUI sound as well, or just passthrough formats?

pt2339-209 · 7 October 2018 09:25

Hi,
find the logs here: https://paste.osmc.tv/awazonazoc
I also enabled debug tracing.
As you requested, the logs capture reboot while AVR is on standby, then, once up, directly playing back an .mka file with DTS HD MA audio. Issue also applies to GUI sounds, yes.
Thanks!

pt2339-209 · 11 October 2018 18:22

Hi grhamh, have you seen the logs I’ve provided? If you could have a look at it, I would be pleased! Thanks!

sam_nazarko · 11 October 2018 18:25

Did you take that log with the AVR on standby again?
I’d expect aud_cap to eventually populate.

pt2339-209 · 11 October 2018 18:30

Yes, as requested by grahamh. When AVR is switched on while vero4k is booting, then aud_cap is populated, yes.

grahamh · 11 October 2018 18:39

I’ve been trying to reproduce what you see, specifically this

00:24:21.519 T:4038062848 INFO: CAESinkALSA - ALSA: pcm_hw.c:327:(snd_pcm_hw_hw_params) SNDRV_PCM_IOCTL_HW_PARAMS failed (-22): Invalid argument

00:24:21.520 T:4038062848 INFO: CAESinkALSA - ALSA: pcm_hw.c:1250:(snd_pcm_hw_get_chmap) Cannot read Channel Map ctl : Invalid argument

no luck so far. There is a bug in the ALSA drivers but normally it hides away unnoticed. Do you have any custom alsa.conf files, perhaps?