An update on XSquawkBox 2.0beta3… (updated 26 Nov)

The audio interface rewrite to fix the Mac issues is mostly complete now and the basic output tests passed this evening. This update should happen in the next few days.

(Update 26-Nov) Got caught up with a bug in the new audio-driver, however, as a fortuitous benefit, the pulseaudio bug appears to have been related, so pulseaudio is back on the cards for the Linux users.

Anticipated changes in the beta3 release:

  • AFV-Native: changed from portaudio to libsoundio in order to fix the issues with macOS 10.14/10.15 audio and macOS device enumeration. (Should also fix any other audio device enumeration related crashes).
  • Put back the config-file options to disable voice support in XSquawkBox for use on secondary rendering systems.

Anticipated issues in the beta3 release:

  • Linux: pulseaudio still doesn’t work due to buffering/latency-compensation issues in libsoundio when coupled with pulseaudio and is disabled in the build. Uncertain if I can even fix this without adding unwanted latency.
  • macOS 10.15: There’s nothing I can do about gatekeeper rejecting the plugin at this time. I’ve researched (and tested) this now, and the issue is unless Laminar updates X-Plane to disable Library Validation, my developer signature on the plugin will still be rejected (as I’m not part of Laminar’s “team”). Users will need to manually approve it in System Preferences (Security) or disable gatekeeper globally.
  • All Platforms: We no longer track the “default device” – you must manually select a suitable device in audio setup.
  • All Platforms: In the XSB config file, we’re now use a device ID for the audio devices, rather than their display names. You will need to set up your audio settings again after upgrading.
  • (Update) All Platforms: Audio Playback devices that do not support a native 1.0 or 2.0 channel mapping won’t be available for playback. Unfortunately, on Windows at least, this means that some PC-managed surround (5.1 / 7.1) configurations may not be usable as a voice playback device.

2 Replies to “An update on XSquawkBox 2.0beta3… (updated 26 Nov)”

  1. Hello Chris,

    I appreciate your efforts on correcting these issues. I run an old Mac Pro 5,1 and sure hope it works with Mojave.


Comments are closed.