Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[madbrain]

Installed a fresh Raspberry OS 05/27/2020 image on a dedicated SD card.
Downloaded from https://downloads.raspberrypi.org/raspios_full_armhf/images/raspios_full_armhf-2020-05-28/2020-05-27-raspios-buster-full-armhf.zip
Pi3 is connected directly via HDMI to my TV, Sharp Aquos LC-60LE835U.
I updated the OS as instructed in the guide. Also edited the /boot/config.txt .
Installed firefox (iceweaver).
Finally, installed MC 26.0.94 .

I can't get any sound out of MC when using Tools / Audio calibration with 2 channels at either 44.1 or 48 kHz (didn't try higher, doubt the TV supports it).
No matter the settings, I always get "something went wrong with the playback" pop-up.
This is true even if I select the NULL output device.
I think I have tried most of the 8 available audio devices to no help.

I have set DSP settings to 2 channels . Output encoding : none.
Sample rate : no change.
Mixing . no upmixing or downmixing.

I wish there was a way to reset everything to default settings in MC, but don't see how. Uninstalling it with apt remove , and then reinstalling it, doesn't give me default settings back.

I get sounds fine out of other apps in the Raspberry OS, such as the built-in games.
Sounds play onto the TV speakers through HDMI as expected. I tried with the analog DAC and attached headphones, and can play sound in the Pi games onto those as well.

Any idea what might be the problem with MC here?

I collected some logs in case this helps.

I tried with MC25 with default settings also. It can't play audio either, with default settings out of the box. I'm guessing it's incompatible with the current version of the Raspberry Pi OS I downloaded somehow.

[JimH]

I think this is a bug or just not implemented yet.   I see the same thing on a Chromebook running Linux.

[Hendrik]

Did you try to play actual audio, instead of the calibration files?

[madbrain]

Did you try to play actual audio, instead of the calibration files?

No.

[JimH]

It would be a good idea.

[madbrain]

It would be a good idea.

Indeed. I just tried it, and surprisingly, it does work. So, it looks like only the calibration function is broken. I assume a fix will be forthcoming for MC26. May I request that it gets fixed on MC25 as well ? The latest .114 version had the same issue. I haven't purchased MC26 yet. I was evaluating it when I found this problem.

[Awesome Donkey]

May I request that it gets fixed on MC25 as well ?

Considering MC25's development has long ended, I wouldn't expect it in my opinion.