After update, some audio formats playback as PCM 2.0. Please help

Help and Support Raspberry Pi
1

Due to a power outage causing corruption on the SD card, I had to update my
Raspberry Pi 3 Model B+ which was running OSMC / Kodi 17.1 to the latest version
(build 21.1 / OSMC 2024.08-1 / kernel: Linux 5.15.92-1-osmc). My main use of Kodi is
listening to multichannel music files (flac 5.1) which have been able to easily
playback as far as I can remember. They’re now being output to my receiver as
PCM 2.0, which is also the case when playing video files with Dolby Digital+ or
Dolby Digital+ with Atmos audio, which also used to play as they should before the update.

I’ve tried every ‘audio output device’ available, changed the number of channels from 5.1 to 2.0, etc. and switched ‘allow passthrough’ on & off.

I don’t really know what I’m looking at on the log, but noticed lines 382-413 & 693-711 state something that looks to me could be the problem.

Summary of audio formats playback results:
(Standard) DTS: Yes
(Standard) Dolby Digital: Yes
Multichannel flac: No, PCM 2.0
Dolby Digital+ (with Atmos): No, PCM 2.0

Thanks, any help is greatly appreciated.
Log:
https://pastebin.com/cdc02XdE

2

Hi

Please upload full logs

Thanks

Sam

3

Sorry, this is my first time posting here, the full log is linked in my original post. Pastebin downloads the log in .txt format. I tried the upload option but only allowed jpg, bmp, not .txt files allowed.

4

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.

Depending on the used skin you have to set the settings-level to standard or higher, in summary:

  • enable debug logging at settings->system->logging

  • reboot the OSMC device twice(!)

  • reproduce the issue

  • upload the log set (all configs and logs!) 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

Thanks for your understanding. We hope that we can help you get up and running again shortly.

OSMC skin screenshot:

image
image960×539 41.4 KB

5

I posted a link to the log in my original post. Here it is again…
https://pastebin.com/cdc02XdE
Would it make a difference if I got the link directly in OSMC?

6

That instructions not only cover how to enable debug logging but how to upload logs so that the OSMC team can help to check your issue

7

So this is no good then? https://pastebin.com/cdc02XdE

8

@jz1276 you have probably overlooked this several times now