FGCom (before 3.0): Difference between revisions

Jump to navigation Jump to search
→‎Solving Audio-Problems: adding this chapter
m (Taking off the "Major Revision Flag" and corrected some wording + links)
(→‎Solving Audio-Problems: adding this chapter)
Line 571: Line 571:


===Solving Audio-Problems===
===Solving Audio-Problems===
Before you start, make sure that your headset is (or speakers and microphone are) working and tested to sensible volumes. Headsets are strongly recommended in order to avoid feedback resonances, which could affect not only you but all fellow listeners with awful or even painful noises.  
The following assumes that you have problems even after you did set up your system as described in [[Verifying your Audio-System]].<br><br>
You may test your Audio-Devices using the basically installed Utilities of your operating system. e.g.: type into a command line for:
'''Poor Audio Quality'''
#Linux: "gnome-sound-recorder", (you may also check on: Linux software audio mixing with FlightGear)
*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.).
#Windows: "audiorecorder"
*It even may help to place your sound-card into a different slot
#Mac: ???
*A (digital) USB-headset helps in avoiding noise and feedback problems
'''Background noise raising with time'''<br>
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>
*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.


more Tests / TestSetups etc. ToBeDefined
'''Unexpected behavior'''<br>
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)
*during reboot or restart they may initiate with values out of a special profile instead of reusing the “last used” values
*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>
So know your standard settings and check if they have changed (without your written permission!)<br><br>
'''Special for Linux'''
(ref [[Linux software audio mixing with FlightGear]]) <br>
check your Home-directory (“~/”) for a file "'''.alsoftrc'''"
(remember that the “show hidden files” must be enabled!)
*if ".alsoftrc" does not exist
**Check if there is a (old version) ".openalrc"
***if yes: rename that to ".alsoftrc"
***if not crate a new  ".alsoftrc"
*If not already done so insert into the file “.alsoftrc” the following :
(define devices '(alsa))
(define alsa-out-device "plug:dmix")


===Using FGCom===
===Using FGCom===
652

edits

Navigation menu