🛠️🐜 Antkeeper superbuild with dependencies included https://antkeeper.com
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

83 lines
3.5 KiB

  1. Useful Environment Variables
  2. Below is a list of environment variables that can be set to aid with running or
  3. debugging apps that use OpenAL Soft. They should be set before the app is run.
  4. *** Logging ***
  5. ALSOFT_LOGLEVEL
  6. Specifies the amount of logging OpenAL Soft will write out:
  7. 0 - Effectively disables all logging
  8. 1 - Prints out errors only
  9. 2 - Prints out warnings and errors
  10. 3 - Prints out additional information, as well as warnings and errors
  11. ALSOFT_LOGFILE
  12. Specifies a filename that logged output will be written to. Note that the file
  13. will be first cleared when logging is initialized.
  14. *** Overrides ***
  15. ALSOFT_CONF
  16. Specifies an additional configuration file to load settings from. These
  17. settings will take precedence over the global and user configs, but not other
  18. environment variable settings.
  19. ALSOFT_DRIVERS
  20. Overrides the drivers config option. This specifies which backend drivers to
  21. consider or not consider for use. Please see the drivers option in
  22. alsoftrc.sample for a list of available drivers.
  23. ALSOFT_DEFAULT_REVERB
  24. Specifies the default reverb preset to apply to sources. Please see the
  25. default-reverb option in alsoftrc.sample for additional information and a list
  26. of available presets.
  27. ALSOFT_TRAP_AL_ERROR
  28. Set to "true" or "1" to force trapping AL errors. Like the trap-al-error config
  29. option, this will raise a SIGTRAP signal (or a breakpoint exception under
  30. Windows) when a context-level error is generated. Useful when run under a
  31. debugger as it will break execution right when the error occurs, making it
  32. easier to track the cause.
  33. ALSOFT_TRAP_ALC_ERROR
  34. Set to "true" or "1" to force trapping ALC errors. Like the trap-alc-error
  35. config option, this will raise a SIGTRAP signal (or a breakpoint exception
  36. under Windows) when a device-level error is generated. Useful when run under a
  37. debugger as it will break execution right when the error occurs, making it
  38. easier to track the cause.
  39. ALSOFT_TRAP_ERROR
  40. Set to "true" or "1" to force trapping both ALC and AL errors.
  41. *** Compatibility ***
  42. __ALSOFT_HALF_ANGLE_CONES
  43. Older versions of OpenAL Soft incorrectly calculated the cone angles to range
  44. between 0 and 180 degrees, instead of the expected range of 0 to 360 degrees.
  45. Setting this to "true" or "1" restores the old buggy behavior, for apps that
  46. were written to expect the incorrect range.
  47. __ALSOFT_REVERSE_Z
  48. Applications that don't natively use OpenAL's coordinate system have to convert
  49. to it before passing in 3D coordinates. Depending on how exactly this is done,
  50. it can cause correct output for stereo but incorrect Z panning for surround
  51. sound (i.e., sounds that are supposed to be behind you sound like they're in
  52. front, and vice-versa). Setting this to "true" or "1" will negate the localized
  53. Z coordinate to flip front/back panning for 3D sources.
  54. __ALSOFT_REVERSE_Y
  55. Same as for __ALSOFT_REVERSE_Z, but for Y (up/down) panning.
  56. __ALSOFT_REVERSE_X
  57. Same as for __ALSOFT_REVERSE_Z, but for X (left/right) panning.
  58. __ALSOFT_SUSPEND_CONTEXT
  59. Due to the OpenAL spec not being very clear about them, behavior of the
  60. alcSuspendContext and alcProcessContext methods has varied, and because of
  61. that, previous versions of OpenAL Soft had them no-op. Creative's hardware
  62. drivers and the Rapture3D driver, however, use these methods to batch changes,
  63. which some applications make use of to protect against partial updates. In an
  64. attempt to standardize on that behavior, OpenAL Soft has changed those methods
  65. accordingly. Setting this to "ignore" restores the previous no-op behavior for
  66. applications that interact poorly with the new behavior.