Changes between Version 115 and Version 116 of FAQ

Timestamp:

Oct 19, 2022, 11:41:15 PM (19 months ago)

Author:

Norse_Harold

Comment:

Add sound and audio advice about where OpenAL stores the configuration on Windows

FAQ

@@ -152 +152 @@
     }}}
     {{{#!td style="border-right:none;padding-left:0.5em"
-There are some settings in the game related to volume levels. From the main menu, click Settings, Options, Sound.
-
-Assuming that sound works for other apps while 0 A.D. is not running then troubleshooting the sound output of 0 A.D. likely involves troubleshooting OpenAL on your system. This is because 0 A.D. uses the OpenAL sound system for audio output. Check the OpenAL configuration, which on Linux and Mac is stored at /etc/openal/alsoft.conf. If it does not already exist then download [https://raw.githubusercontent.com/kcat/openal-soft/master/alsoftrc.sample alsoftrc.sample], rename it to alsoft.conf and store it there.
-
-Ensure that the correct "driver", also known as "audio backend", is being used. There are reports from users where unexpected drivers were used by OpenAL, for example trying to use jack, failing, next using alsa instead of Pulseaudio. The only documentation easily found about the OpenAL configuration is in the comments within alsoft.conf. When referencing drivers in the OpenAL configuration, use the name of the audio backend within the quote marks at [https://github.com/kcat/openal-soft/blob/master/alc/alc.cpp#L199 alc.cpp]. 
-
-Recommended OpenAL drivers:
-* Linux: pulse, alsa
-* Mac: core
-* Windows: wasapi
-
-Note that driver availability depends on your operating system and compile-time choices for your copy of the OpenAL library.
+There are some settings in the game related to volume levels. From the main menu, click Settings, Options, Sound. 
+
+If you connect a sound device after you start 0 A.D. then it is necessary to configure it to the default sound device in your operating system, then restart 0 A.D. in order for it to be detected.
+
+Assuming that sound works for other apps while 0 A.D. is not running then troubleshooting the sound output of 0 A.D. likely involves troubleshooting OpenAL on your system. This is because 0 A.D. uses the OpenAL sound system for audio output. Check the OpenAL configuration, which on Linux and Mac is stored at /etc/openal/alsoft**.conf**, and on Windows is stored in %AppData%\alsoft**.ini**. If it does not already exist then download [https://raw.githubusercontent.com/kcat/openal-soft/master/alsoftrc.sample alsoftrc.sample], rename it to the appropriate name for your OS and store it in the correct location, listed earlier.
+
+Ensure that the correct "driver", also known as "audio backend", is being used by OpenAL. There are reports from users where unexpected drivers were used by OpenAL, for example trying to use jack, failing, next using alsa instead of Pulseaudio. The only documentation easily found about the OpenAL configuration is in the comments within alsoft.conf. When referencing drivers in the OpenAL configuration, use the name of the audio backend within the quote marks at [https://github.com/kcat/openal-soft/blob/master/alc/alc.cpp#L199 alc.cpp]. 
+
+Recommended OpenAL drivers configuration statement:
+* Linux: {{{drivers = pulse,alsa,}}}
+* Mac: {{{drivers = core,}}}
+* Windows: {{{drivers = wasapi,}}}
+
+Note that OpenAL driver availability depends on your operating system and compile-time choices for your copy of the OpenAL library. The [https://github.com/kcat/openal-soft#utilities openal-info] utility lists detected devices. If you are using Linux then openal-info may be available for your distribution in a package called, for example, openal-info.
 
 For further help with OpenAL, contact the OpenAL developers via the means specified on their [https://openal-soft.org/ website].
+
+Note that OpenAL can only work as well as the audio backend or driver that it is configured to use, so that is another area to consider during troubleshooting.
     }}}
   }}}