Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
audio_issues [2021/11/10 00:30] – added info about RPi headphone jack audio atariaudio_issues [2022/08/02 09:31] – added profile section atari
Line 14: Line 14:
   - Go back into **SYSTEM SETTINGS** -> **AUDIO OUTPUT** and test all available outputs, exiting to the **MAIN MENU** between each change.   - Go back into **SYSTEM SETTINGS** -> **AUDIO OUTPUT** and test all available outputs, exiting to the **MAIN MENU** between each change.
   - If none of the **AUDIO OUTPUT** options worked, repeat steps 1-2 for a different **AUDIO PROFILE**. Your **AUDIO OUTPUT** options might change depending on the **AUDIO PROFILE** selected.   - If none of the **AUDIO OUTPUT** options worked, repeat steps 1-2 for a different **AUDIO PROFILE**. Your **AUDIO OUTPUT** options might change depending on the **AUDIO PROFILE** selected.
 +
 +If the appropriate options are not being listed in the menu, you could try using the generic name for the audio device by manually editing the configuration file. Open ''system/batocera.conf'' and modify (or add if not already present) the ''audio.device'' key to be:
 +
 +<code>
 +audio.device=hdmi
 +</code>
 +
 +where "hdmi" is the generic name for your audio device.
  
 <WRAP center round info> <WRAP center round info>
Line 46: Line 54:
   - Replace the second digit with your audio number. For instance, if it is ''audio.device=0,3'', then according to our example it would be ''audio.device=0,4''. The following text doesn't particularly matter, that's just the label it shows in EmulationStation.   - Replace the second digit with your audio number. For instance, if it is ''audio.device=0,3'', then according to our example it would be ''audio.device=0,4''. The following text doesn't particularly matter, that's just the label it shows in EmulationStation.
   - Reboot, and if your audio still isn't working then try ''audio.device=1,3'', then ''audio.device=2,3'' and so on.   - Reboot, and if your audio still isn't working then try ''audio.device=1,3'', then ''audio.device=2,3'' and so on.
 +
 +===== Not all of my speakers are being used =====
 +
 +Ensure you have selected the right audio profile in 
 +
 +For instance, a 5.1 surround sound setup would want to use the "SURROUND 5.1" profile:
 +
 +{{:audio-profile.png?nolink&600|}}
  
 ===== I have sound in emulators and the main menu, but not during video previews ===== ===== I have sound in emulators and the main menu, but not during video previews =====
Line 114: Line 130:
 It could be that your audio buffer isn't high enough. It could be that your audio buffer isn't high enough.
  
-You can change your default audio buffer for Libretro cores by navigating to **MAIN MENU** -> **GAMES SETTINGS** -> **PER SYSTEM ADVANCED CONFIGURATION** -> [system affected by audio cutting out-> **AUDIO LATENCY**.+You can change your default audio buffer for libretro cores by navigating to **MAIN MENU** -> **GAMES SETTINGS** -> **PER SYSTEM ADVANCED CONFIGURATION** -> <system affected by audio cutting out-> **AUDIO LATENCY**.
  
-To change the setting for all Libretro cores, you can add ''global.retroarch.audio_buffer=128'' to your ''batocera.conf'' file, with your intended buffer in milliseconds. Try a higher number if it's still cutting out, it should gradually get better. If it isn't gradually getting better, refer to the [[#my_audio_is_consistently_cutting_out_irrelevant_of_what_my_system_is_doing|section below]].+To change the setting for all libretro cores, you can add ''global.audio_latency=128'' to your ''batocera.conf'' file, with your intended buffer in milliseconds. Try a higher number if it's still cutting out, it should gradually get better. If it isn't gradually getting better, refer to the [[#my_audio_is_consistently_cutting_out_irrelevant_of_what_my_system_is_doing|section below]].
  
 <WRAP center round info> <WRAP center round info>
-Note that this will only affect Libretro cores. If you have audio skipping on other emulators, you'll need to discover how to adjust the audio buffer settings for that emulator in particularusually can be found on its [[:systems|system page]].+Note that this mostly only affects libretro cores. If you have audio skipping on other emulators which this setting has no effect on, you'll need to discover how to adjust the audio buffer settings for that emulator in particular (usually can be found on its [[:systems|system page]]'s troubleshooting section).
 </WRAP> </WRAP>
  
Line 154: Line 170:
  
 This is more likely to be a hardware fault. Replug the cable, try a different cable, using a different interface (like 3.5mm analog audio instead of HDMI), etc. This is more likely to be a hardware fault. Replug the cable, try a different cable, using a different interface (like 3.5mm analog audio instead of HDMI), etc.
 +
 +===== How do I diagnose my audio cutting out? =====
 +
 +While running a game, SSH into Batocera and run ''%%pw-top%%''. One line will be for ''alsa_output'' (depending on the emulator) and another line will be for the emulator (in most cases, ''retroarch''). Look at the ''ERR'' column, if both are increasing this indicates an issue with underrun audio frames. This can be solved via increasing the audio latency, choosing a more optimized audio backend or reducing the overall CPU usage.
 +
 +===== My audio device is not appearing in the list of available audio outputs on Raspberry Pi =====
 +
 +Try using the fake kernel mode setting instead of the full one as a workaround.
 +
 +In ''/boot/config.txt'', comment out the ''dtoverlay=vc4-kms-v3d'' and uncomment the ''dtoverlay=vc4-fkms-v3d'' lines. It should look like this:
 +
 +<code>
 +# Enable DRM VC4 V3D driver on top of the dispmanx display stack
 +# Preferred 'Full' Kernel Mode Setting (KMS)
 +#dtoverlay=vc4-kms-v3d
 +
 +# Optional 'Fake' KMS for displays that won't work with 'Full' KMS
 +dtoverlay=vc4-fkms-v3d
 +</code>
 +
 +Using the fake kernel mode setting may introduce performance issues. It is preferable to instead figure out the root cause of the issue instead.
 +
 +===== I need to automate something involving my audio settings =====
 +
 +You can use [[:launch_a_script|Batocera's scripting capabilities]] to do so. [[:launch_a_script#batocera_scripts1|Scroll down to find an example related to audio settings.]]
  
  • audio_issues.txt
  • Last modified: 4 months ago
  • by maximumentropy