No sound over HDMI
-
I have problem with sound over HDMI. Works only analog output.
I've tried to change command line with "recalbox-user-config", over network connection too and all nothing. The system doesn't show option to choose sound over hdmi. Only analog. The cable has putted near to power cable.
I have RB 4, and TV Samsung Q80. Any sugestions? -
- What is your version of Recalbox (say version, don't say "latest")?
- Did you build your Recalbox yourself, or download a ready-made image from the internet, or did you buy everything ready-made?
- Have you tried with the other HDMI output of the RPi4? Another HDMI input from the TV?
- Have you tried with another TV? Another Cable?
- Ever tried to do a factory reset (via advanced settings)? Factory reset does not delete any personal files, but resets all custom settings.
Maybe this will help:
https://forum.recalbox.com/topic/23885/update-to-7-2-no-sound -
- I have version 7.2.2 (latest )
- I have bought clear RB Pi4 a installed Recalbox via Raspberry Pi Imager on Windows 10
- I have tried other cables, and other ports and still the same. But on ma second TV (old low-end Samsung 40'' 1080p) sound is working after editing line #sound output in recalbox-user-config file on SD card
- I have tried factory reset few times and also I have tried to install other OS like Raspberry OS or Retropie, ale still sound not working.
-
@kamilcieplak
Also I don't know how to find "retroarchconfigcustom.cfg", or I don't understand how to do this solution:
"Do the following:- Access recalbox by ssh, you can do it with the command ssh root @ IP in GNU / Linux or putty in other systems, the default access values are:
User: root
Password: recalboxroot"Where I have to enter to edit that?
What is retroarch menu? Is it on Recalbox system or somewhere in system files?
I'm huge retro games fan, but also I'm a new RP and recalbox user, so unfortunatelyI don't get many things
-
Access recalbox by ssh
For access via SSH, I recommend using the "WinSCP" software, but see the documentation:
And watch this video (enable subtitles):
What is retroarch menu?
There are basically 2 types of emulators in Recalbox: standalone emulators and Retroarch - Retroarch has many different cores, if you check the SNES for example, there are many different cores, but most of them work in retroarch.
To access the retroarch menu, just start any game that is not running in a standalone emulator (some SNES game for example), and press Hotkey+B to access the menu (as it is said here ).
See here which boards have which emulators, all LIBRETRO cores are running on retroarch:
https://recalbox.gitbook.io/documentation/hardware-compatibility/emulators-compatibilityExample: AdvanceMame is a standalone emulator, but Libretro Mame2003 is a core of Retroarch.
-
Is it possible my Pi is broken? Why I have the same problem with sound on three different operate systems? Still I don't understand all those putty like programs. I'm not some Neo or Mr. Robot
-
Is it possible my Pi is broken?
on ma second TV (old low-end Samsung 40'' 1080p) sound is working after editing line #sound output in recalbox-user-config file on SD card
Since you have sound on another TV, the problem doesn't seem to be with the RPi, but with the communication between your RPi and the TV you're trying to get it to work, possibly the problem is with some TV setup (but I don't know which one, I don't have this TV).
Still I don't understand all those putty like programs. I'm not some Neo or Mr. Robot
I understand that it's not something that a common user is used to doing on a daily basis, but it's not something that requires a lot of computer knowledge, don't be scared that you'll be able to try it patiently.
I recommend that you watch this video (turn on the subtitles):
https://www.youtube.com/watch?v=Bt4aHZ2Xo2g&list=PL2oNQ0AT7fx2ExiSNrfHUzga5GnogI4sh&index=34&ab_channel=RecalboxI'd rather use WinSCP than putty, so it might be interesting that you read the WinSCP documentation:
https://winscp.net/eng/docs/getting_startedAlso, there are several unofficial tutorials on the internet, if you search for "how to use winscp", you will find several videos, and probably some explaining how to use in Recalbox.
-
So. I've exchanged my Pi to new. Same problem. Next I've installed Batocera OS - even don't starting. Then I've installed Retropie. No sound at te first run, but after editing cofig files, sound was finally worked.
# uncomment to force a specific HDMI mode (this will force VGA) hdmi_group=1 hdmi_mode=16 # uncomment to force a HDMI mode rather than DVI. This can make audio work in # DMT (computer monitor) modes hdmi_drive=2
Tried the same cofiguration on recalbox (included deleting hashtags), but no result. I've makeing changes in different configuration files an then I did it. Sound was worked. But resolution was 720p. On 65" 4k TV. Not enough. So I was still editing to configure highest resoution like 1080p, but sound missing and I can not set it back. Tried to making changes in conf files , reinstalling OS, formating SD card and nothing. Now I can set any resolutin to Recalbox, but sound is only Analog output. No hdmi...
Maybe is 7.2.2. fault? Is it possible to get 7.1.1 version? I can't find it anywhere...
-
Maybe is 7.2.2. fault?
No, I'm sure the problem is specifically in the communication between your Rpi and your TV, your tests prove it. Also, there are no more users reporting any such problem, so it's something specific.
Is it possible to get 7.1.1 version? I can't find it anywhere...
It's not possible, that's why you can't find it, we don't support outdated versions, only the latest official version is available.
I've exchanged my Pi to new.
As I said, I figured the problem wasn't the RPi, but at least now you're sure of it.
But resolution was 720p. On 65" 4k TV. Not enough
As I said, the problem seems to be in the communication between the Rpi and your TV: your TV has a very large size / resolution / quality, it's not the one normally used (I'm not saying it's not possible to make it work, but, is not as easy as on other TVs).
Just for example (I know you tested it with another HDMI cable), but there are several versions of HDMI cable, the more modern the TV, the greater the possibility of the version interfering, as you can see reports from other users...
But from your testing, the problem appears to be in the video configuration of the
recalbox-user-config.txt
file (you will find several topics talking about theconfig.txt file
, but therecalbox-user-config.txt
file keeps your changes after an upgrade,config.txt
does not).I recommend that you check the result of the
tvservice
command as mentioned in this tutorials:And then edit the
recalbox-user-config.txt
file with your TV's resolution.If the optimal resolution doesn't work, there are other options available, see these links:
- https://www.raspberrypi.org/documentation/computers/config_txt.html#hdmi-mode
- https://www.raspberrypi.org/documentation/computers/configuration.html#hdmi-configuration
Note: the documentation makes it clear that on the "Raspberry Pi 4 ... you can also drive a single display at 4K with a 60Hz refresh rate: this requires that the display is attached to the HDMI port adjacent to the USB-C power input (labelled HDMI0)."
In last cases:
And, if necessary:
Unfortunately I don't have a TV as good as yours, so I can't do the tests, but I believe that with these links you have all the necessary information to make it work.
-
I have solved the problem! The solution was one option in my "genius" tv There is option "HDMI signal plus" and now sound work at any resolution. Apologize for the mess I have done and thank you for your help. Now I've learn much about Raspberry operating systems, included best system of retro gaming Recalbox
-
But It's still weird. Why sound works on Retropie without this option?
-
There is option "HDMI signal plus" and now sound work at any resolution.
I'm glad you managed to make it work, thanks for the feedback, this is very useful in case other people encounter the same issue in the future.
But It's still weird. Why sound works on Retropie without this option?
They are different operating systems, of course there are some technical differences, there is probably a driver that can communicate better with your TV, but the Recalbox driver can also communicate with your TV (with this option).
I'm not a developer, and it's not possible to be sure without a closer look, but it looks like that's it. -
I had the same problem.
It was solved changing the HDMI cable to the other port (I moved it from HDMI1 to HDMI0, the closest to charging port).No other change in configuration was required.