Anthony Spagnoletti 133957 Posted November 10, 2015 at 02:42 PM Posted November 10, 2015 at 02:42 PM I seem to be having some issues trying to get my microphone working with Xsquawkbox under Linux. I am using a Logitech G230 headset with X-plane 10 installed via steam. I am running Gentoo Linux. The microphone is functional in the web browser and in the steam settings page. When I try to configure my audio in Xsquawkbox I continually get the message "Background nose is at the same level as the talking volume". When I attempt to play back the recordings X-plane crashes. Audio is set up through ALSA. I am not sure how to move forward from here but would gladly provide any additional information that will help to resolve the problem. Thanks in advance! Link to comment Share on other sites More sharing options...
Daniel Svensson 1348749 Posted February 3, 2016 at 02:13 AM Posted February 3, 2016 at 02:13 AM I am having the same problem getting the microphone working with XSquawkbox on Linux. I can connect to VATSIM and tune the local ATC frequencies. When I tune to the ATIS frequency I can hear the recording the controller has made. I am using a KOSS CS-100 headset and the microphone works great with Mumble. When I go through the set up process for the mic in Xsquawkbox I get the message "Background noise is at the same level as the talking volume" and the recording it plays back is empty. I have selected the PulseAudio Sound Server as the input device, which is the same one I am using in the Mumble configuration which works great. I am also using the PulseAudio Sound Server for the COM1 and COM2 devices which works fine for radio reception. Software in use X-plane Version 10.42 Xsquawkbox version 1.31 Linux Mint 17.2 (64 bit) Thank you. Link to comment Share on other sites More sharing options...
Daniel Svensson 1348749 Posted February 13, 2016 at 02:25 PM Posted February 13, 2016 at 02:25 PM Solution Found! I purchased a USB Audio Stereo Sound Adapter ($5 for the Sabrent brand adapter on Amazon) and plugged my headset into the adapter instead of the on-board sound card jacks on the back of the motherboard. Then went to sound settings in Linux and selected the new equipment as my default. In the Xsquawkbox sound settings I just used the defaults for the microphone and radios. Now everything works as expected! Link to comment Share on other sites More sharing options...
Alejandro Alvarez 1095299 Posted March 19, 2016 at 07:11 PM Posted March 19, 2016 at 07:11 PM Hi, I'm having same problem: The mic is no detected. The input pickup panel shows the same devices listed as outputs. Anyone knows which function is being used to get available input devices? I am using libpulse 8.0.3 in an ArchLinux distro updated to date. May be some API has changed. I will continue trying to figure out the issue and post any kind of advance. Regards. Link to comment Share on other sites More sharing options...
Christopher Collins Posted April 11, 2016 at 12:15 PM Posted April 11, 2016 at 12:15 PM As much as it pains me to say this: at this point in time, XSB Audio problems are entirely the user's problem on Linux unless you're using Ubuntu or Debian. In both of those cases, I might be able to reproduce the problem, bu totherwise I am not able to debug your distro specific problems with XSB. Generally, if you can use Pulse, please do - it'll be far more reliable than anything else by virtue of the fact the ALSA Pulseaudio device is extremely well behaved and does all the sample format conversion. I did rewrite a huge chunk of the sample rate selection and conversion code to address what should have been the bulk of issues with native ALSA support, but if your ALSA driver behaves badly, there's nothing I can do - this is not XSB's fault and you'll need to report the behaviour to the driver author or your distro vendor. If you cannot use Pulse, make sure that you're getting a solid frame-rate (>= 20fps) as there is most likely buffering issues in the audio path that are specific to Linux, and greatly exacerbated by bad frame-rates. My test systems are generally configured for about 30fps, and I will not test with sub-20fps as you really should not be on VATSIM with sub-20fps with X-Plane due to the fact that X-Plane skews simulator time at lower frame-rates. Beyond that, there's not much I can do at this time - the ALSA code-path has been robust throughout all of my testing after I nailed the few big bugs that were sitting there for years - the implementation is, as far as I can tell, correct, if just a bit quirky. (As noted in another thread somewhere, yes, XSB opens the device multiple times hence the need for dmix if you're using ALSA). XSquawkBox - Developer/Maintainer Please post any support related questions to the XSquawkBox support forum rather than private messaging me, thanks. Link to comment Share on other sites More sharing options...
Recommended Posts