FGCom (before 3.0): Difference between revisions

Jump to navigation Jump to search
(→‎Solving Audio-Problems: OpenAL-soft uses a different configuration file format.)
Line 644: Line 644:


====Solving Audio-Problems====
====Solving Audio-Problems====
The following assumes that you have problems even after you did set up your system as described in [[Verifying your Audio-System]].<br><br>
The following assumes that you have problems even after you did set up your system as described in [[Verifying your Audio-System]].
'''Poor Audio Quality'''
=====Poor Audio Quality=====
*Check especially your microphone-cables for a good quality shielding and root them as far away as possible from electromagnetic noise emitters (motors, blowers, AC-cabling, lamps, etc.).
*Check especially your microphone-cables for a good quality shielding and root them as far away as possible from electromagnetic noise emitters (motors, blowers, AC-cabling, lamps, etc.).
*It even may help to place your sound-card into a different slot
*It may help to place your sound-card into a different slot
*A (digital) USB-headset helps in avoiding noise and feedback problems
*A (digital) USB-headset helps in avoiding noise and feedback problems
'''Background noise raising with time'''<br>
=====Background noise raising with time=====
This is typical for an active automatic “Boost”, “Gain”, or “Amplifier” device, or a microphone set too sensible. i.e. while there is no “real sound” the devices will try to “boost” the “background noise” to a real sound level – and that may hurt your ears.
This is typical for an active automatic “Boost”, “Gain”, or “Amplifier” device, or a microphone set too sensible. i.e. while there is no “real sound” the devices will try to “boost” the “background noise” to a real sound level – and that may hurt your ears.
*'''Basically:''' Do not keep the PTT pushed longer than absolutely necessary,  before and after speaking!<br>  
*'''Basically:''' Do not keep the PTT pushed longer than absolutely necessary,  before and after speaking!<br>  
*Try to say something and the sound-system should adjust to that – but the problem will reappear after a short while. '''You should always switch off your microphone if you are not really talking – and keep the microphone level as low as possible!'''
*Try to say something and the sound-system should adjust to that – but the problem will reappear after a short while. '''You should always switch off your microphone if you are not really talking – and keep the microphone level as low as possible!'''
*If anyhow possible, do not use automatic boosters. If your microphone does  need such a support, keep it to a minimum. Especially in the FGCom application the microphone output needs less power because the central server does equalize the loudness of all users.
*If anyhow possible, do not use automatic boosters. If your microphone does  need such a support, keep it to a minimum. Especially in the FGCom application the microphone output needs less power because the central server does equalize the loudness of all users.
 
=====Unexpected behavior=====
'''Unexpected behavior'''<br>
Especially “high quality” sound-cards may get you into trouble, because e.g.:  
Especially “high quality” sound-cards may get you into trouble, because e.g.:  
*they may monitor how long the microphone was not used and switch it off after some timespan (without you noticing it)
*they may monitor how long the microphone was not used and switch it off after some timespan (without you noticing it)
Line 661: Line 660:
*or they may set some slide controls to “0” (especially microphone sliders)
*or they may set some slide controls to “0” (especially microphone sliders)
*some do switch the microphone only after pushing '''and''' releasing the space-bar – while we want to change the microphone-status only while the space-bar is pushed down! (This may not affect a PTT asigned to a joystick)<br>
*some do switch the microphone only after pushing '''and''' releasing the space-bar – while we want to change the microphone-status only while the space-bar is pushed down! (This may not affect a PTT asigned to a joystick)<br>
So know your standard settings and check if they have changed (without your written permission!)<br><br>
So know your standard settings and check if they have changed (without your written permission!)
 
=====Special for Linux (.alsoftrc)=====
'''Special for Linux'''
(ref [[Linux software audio mixing with FlightGear]]) <br>
(ref [[Linux software audio mixing with FlightGear]]) <br>
check your Home-directory (“~/”) for a file "'''.alsoftrc'''"
check your Home-directory (“~/”) for a file "'''.alsoftrc'''"
Line 680: Line 678:
  capture = plug:dsnoop
  capture = plug:dsnoop
The system wide OpenAL-soft configuration file may be /etc/openal/alsoft.conf or similar. It usually contains comments describing all possible configuration options.
The system wide OpenAL-soft configuration file may be /etc/openal/alsoft.conf or similar. It usually contains comments describing all possible configuration options.
 
=====USB-Headsets-Problems with Linux (Ubuntu)=====
'''USB-Headsets-Problems with Linux (Ubuntu)'''<br>
The following is based/verified on Ubuntu, but should be similar on other distributions:
The following is based/verified on Ubuntu, but should be similar on other distributions:
*If you cannot hear and/or record with your USB-Headset, try to disable the PulseAudio:
*If Recording is ok '''and''' the f910-Test looks alright in the window, '''but''' there is no delayed response:
**see http://linuxowns.wordpress.com/2008/07/08/how-i-got-my-usb-headset-to-work/
 
*If Recording is ok and the f910-Test looks alright in the window, but there is no delayed response:
**type "cat /proc/asound/modules" into the command window, e.g.:
**type "cat /proc/asound/modules" into the command window, e.g.:
  $ cat /proc/asound/modules
  $ cat /proc/asound/modules
   0 snd_usb_audio
   0 snd_usb_audio
   1 snd_hda_intel
   1 snd_hda_intel
If that displays multiple devices (as shown in the above list, which is the result '''after''' doing the following!), then the USB-Headset should be in the "0" position. If this is not the case, notice the name of your USB-device and edit it. e.g.:  
**If that displays multiple devices (as shown in the above list, which is the result '''after''' doing the following!), then the USB-Headset should be in the "0" position. If this is not the case, notice the name of your USB-device and edit it. e.g.:  
  "sudo gedit /etc/modprobe.d/alsa-base"
  "sudo gedit /etc/modprobe.d/alsa-base"
add as last line into that file, e.g.:
**add as last line into that file, e.g.:
  options snd_usb_audio index=0
  options snd_usb_audio index=0
<br>
*If you use '''Festival''' (the Text/Speech AddOn)
**and
*** it works OK when running alone
*** but runs int error "can't open /dev/dsp" when running with FGFS (and/or other applications)
** then add a TextFile ".festivalrc" into your home-directory, containing:
(Parameter.set 'Audio_Command "aplay -q -c 1 -t raw -f s16 -r $SR $FILE")
(Parameter.set 'Audio_Method 'Audio_Command)


====Helpfull INTERNET Adresses====
====Helpfull INTERNET Adresses====
652

edits

Navigation menu