OK so I copy-pasted the text below into S99custom, but its the same behavior as before (splash screen has sound, emulationstation no sound). Do you know the command to trigger the output-device change? I.e. from USB Audio to HDMI … would like to try something

#!/bin/bash

test -e "/recalbox/share/system/custom.sh" && /recalbox/share/system/custom.sh $1

systemsetting="python /usr/lib/python2.7/site-packages/configgen/settings/recalboxSettings.pyc"
config_script=/recalbox/scripts/recalbox-config.sh

rb_volume_configure() {
settingsVolume="$systemsetting -command load -key audio.volume"
if [ "$settingsVolume" != "" ];then
recallog "setting audio volume to $settingsVolume"
eval $config_script "volume" "$settingsVolume" 2>&1 | recallog
fi
}

rb_audio_configure() {
recallog "Restoring ALSA mixers configuration"
alsactl -f /recalbox/share/system/configs/asound.state restore
settingsAudio="$systemsetting -command load -key audio.device"
if [[ "$settingsAudio" == "" ]];then
settingsAudio="auto"
fi
recallog "setting audio to $settingsAudio"
eval $config_script "audio" "$settingsAudio" 2>&1 | recallog
}

( rb_volume_configure ; rb_audio_configure ) & # 1.0

@taurin
Hallo, ich hab nun einige n64 Roms auf meinen XU4 getestet. Bei mir ist alles ok, ich hab keine Soundprobleme.

@nilocretep no idea. Try it on another pc and compare. It might be something isn‘t fully supported in our build.

I have managed to get sound working, although the volume is high and cannot be changed from the Recalbox GUI. But too much sound is better than no sound ;-)

What I did was this:

Remounted root as writable:

mount -o remount,rw /

Add env var for nano to work:

export TERM=xterm

Created a .asoundrc file:

nano ~/.asoundrc

with the following contents:

pcm.!default {
type plug
slave {
pcm "hdmi:0,3"
}
}
ctl.!default {
type hw
card 0
}

Saved the above file and rebooted from the GUI.

I still didn’t have sound and figured I might need another approach, like directly editing the conf file. Before doing that I went one more time to the GUI and tried selecting each audio output. Lo and behold now hw:0,7 worked!

To see if the settings would stick I rebooted. Sound still worked.

For grins I ssh’d back in and tool a look at ~/.asoundrc. To my surprise it was different than the file that I created. It now contained the hw:0,7 settings that must have come from my audio change in the GUI. Here’s the current contents of ~/.asoundrc:

pcm.!default {
type hw
card 0
device 7
}

ctl.!default {
type hw
card 0
}

Apparently the HDMI device 7 does work on my hardware as long as it’s set as the asla default? Strikes me as odd that I could not get this to work when calling aplay directly.

Anyway it appears that the real issue here is that the absence of a writable ~/.asoundrc file was the problem all along. Making the partition writable and creating this file has now allowed recalbox to be able to successfully write its own contents here and make sound work.

If I'm right about this and Recalbox needs to be able to create and write to the ~/.asoundrc file then this seems like a bug.

I guess I’m happy with this because I have sound. But it’s kind of a pain that the system volume slider is useless. It seems like the PC is now pumping out full volume, so I have to turn the TV sound bar way down when using recalbox.

It would be nice to be able to specify HDMI as the output and be able to control the volume. If anyone has ideas, please let me know. Otherwise I’ll just take what I have as a win.

@glockwizard ¡Hola!
No tengo un ODROID XU4, así que nunca tuve este problema, pero investigando al respecto, lo único que encontré sobre los problemas de HDMI en esta placa fue el enlace:
https://github.com/recalbox/recalbox-os/wiki/Odroid-XU4-ignore-HDMI-CEC
No sé si ese es el problema, pero creo que puede estar relacionado ...

Bizarre je viens de tester chez moi sur mon odroid xu4 et je n ai aucun probleme avec le son

Tried various things with .conf files above after getting root (/) filesystem mounted as rw, but still unable to get things working.

Used retroarch directly after stopping emulationstation manually, i.e.
retroarch --menu --verbose ; customretroarch definitely being read-in including the following audio settings. have confirmed that audio_device is @ 0,1 and modified the audio_driver with alsa too.

retroarch --features compiled with ALSA as expected, nothing else valid to use:

audio_enable = "true"
audio_driver = "alsa"
audio_device = "hw:0,1"
audio_sync = "true"

simply getting an "failed to initialize audio" error from retroarch log:

[ERROR] [ALSA]: Failed to initialize... [ERROR] Failed to initialize audio driver. Will continue without audio.

--

decided to take a good look at osmc config with retro and what its using:
audio_driver = "alsathread"
audio_resampler = "sinc"
audio_device = ""
audio_sync = "true"

I emulated this in recalbox, and the errors in retroarch stop with the following in the retroarch startup as in osmc

[INFO] ALSA: Using signed 16-bit format.
[INFO] ALSA: Period size: 384 frames
[INFO] ALSA: Buffer size: 1536 frames

so figured I was onto something, however still no sound.

really just clueless now. remember, I launch emulation in osmc (from kodi) and I start up a game... audio just works.

i suppose my next question is: is there something in kodi that launches stuff correctly or emulation station, or is this simply a recalbox 'startup driver problem' that doesnt recognize the audio correctly. can anyone shed light on this for me?

Peace.

@voljega This is the SD card I'm using https://www.amazon.com/gp/product/B06XWN9Q99/
I'm pretty sure it's a good one. More likely is people just aren't reading what I'm actually typing.

How to test:
1)Fresh install recalbox onto a Pi 3B.
2)Add Mario 3 ROM to game list.
3)Start Mario 3 game and press select button to move the little red arrow. It will make a sound as it moves.
4)Press Hotkey + B and use that menu to write a savestate (doing it other ways will not reproduce the bug)
5)Use that green Retroarch menu you're in to restart the game.
5)press select button to move the little red arrow. It will make a sound way after it moves, and you will notice the awful audio lag.

@nyny77 regarde au niveau des réglages son sur la télé voir si par hasard elle n'est pas sur hdmi au lieu de jack

resuelto...

resulta que era culpa del theme "clean retro", si pongo el theme normal si me funciona bien el volumen, no entiendo porque, pero es lo que me estaba pasando!
salu2

Hello @helldash-0

https://buildbot.libretro.com/.docs/library/pcsx_rearmed/

Ideas :
try another bios
try another roms

Ciao,
il raspberry ha una uscita jack che puoi usare per collegarlo all'eventuale ingresso che ha il monitor o a casse aggiuntive.

Che io sappia, no dipende da come è stato programmato, probabilmente

@nwsw i have no idea how these connectors look like, but it's basic electronics. I guess you could simply do the right cutti gs with a 3.5 jack cable

That disk usage looks seriously suspect - due to the way files are stored I didnt think it was possible to get to 100% usage.....

You have to go back to basics.
Fresh install again - is it fine?
If not, try any old microSD just to get up and running - still not fine?
Id then think it was the PI.......

@maldorhan said in Potential Audio Beneficial Audio Change:

The white noise you talk about on the Rpi3 is only when using the 3.5 jack output right? I've noticed it too but it doesnt occur with audio through HDMI, thought it would be useful to some readers to point that out ;)

Yes, you are correct. RPi3 and audio jack. Good catch. :)

Everything is working... thank you very much guys!

In order to make the NUC6CAYH function correctly you have just to upgrade the BIOS and the Firmware of the NUC link text. You will need a Windows installed in the NUC in order to install the updates.

I guess the same problema happens in NUC7ixBN, cause the firmware upgrade is availiable for both models.

Regards!