Vero V and Dolby TrueHD/DTS HD Master issue

Help and Support
16

The article Audio hardware and software configuration explains the difference between ‘best match’ and ‘optimized’.

Since now all settings are done as suggested in this wiki article and there is no general known problem using DTS HD Master and Dolby True HD on the VeroV, I suggest:

  • provide another log set with the current settings showing the issue
  • swap the HDMI ports on the AVR and see if the problem moves
  • What DTS-HD and True HD have in common is that they require relatively large bandwidths. Another highspeed or premium highspeed HDMI cable for tests would be helpful.
  • Since you also seem to have this audio issue with a RPi4 (“Didnt have it so often”), it sounds to be more located on the AVR side in this scenario. I think you’re German, so this Yamaha RX-V473 topic sounds a bit like the behaviour you describe: Yamaha RX-V473 - Decoder Off bei Dolby True HD und DTS HD, Yamaha - HIFI-FORUM.

What really surprises me is the extremely large number of messages like

2024-04-27 21:59:52.521 T:3042    debug <CSettingsManager>: requested setting (label1018) was not found.
2024-04-27 21:59:52.521 T:3042    debug <CSettingsManager>: requested setting (label1029) was not found.
2024-04-27 21:59:52.521 T:3042    debug <CSettingsManager>: requested setting (label1035) was not found.
2024-04-27 21:59:52.521 T:3042    debug <CSettingsManager>: requested setting (label104) was not found.
2024-04-27 21:59:52.521 T:3042    debug <CSettingsManager>: requested setting (label1067) was not found.
2024-04-27 21:59:52.521 T:3042    debug <CSettingsManager>: requested setting (label1078) was not found.
2024-04-27 21:59:52.521 T:3042    debug <CSettingsManager>: requested setting (label1084) was not found.

...

in the logs. Obviously, you have installed or changed something on the system causing this but I cannot see what is the root cause for it. Whether this is related to the AVR behaviour … I don’t know.
Perhaps, others in the OSMC team have an idea.

Addition: Ok, these CSettingsManager messages seem to have its origin by the addon service.vpn.manager, see Debug logs fills up.