FGCom (before 3.0): Difference between revisions

Jump to navigation Jump to search

FGCom (before 3.0) (view source)

Revision as of 09:36, 18 October 2009

4,350 bytes removed ,  18 October 2009
→‎Solving Audio-Problems: moved that chapter to "FGCOM_Testing"
m (just beaty operations)
(→‎Solving Audio-Problems: moved that chapter to "FGCOM_Testing")
Line 489: Line 489:




====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]].
=====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.).
*It may help to place your sound-card into a different slot
*A (digital) USB-headset helps in avoiding noise and feedback problems
* stereomix on your soundcard enabled? Disable it
=====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.
*'''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.
=====Unexpected behavior=====
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!)
=====Special for Linux (.alsoftrc)=====
(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: Check if you really use the old OpenAL library and not the newer OpenAL-soft library. If still have the old you put something like this in ".openalrc":
(define devices '(alsa))
(define alsa-out-device "plug:dmix")
**if not, create a new ".alsoftrc" file and insert something like the following into it:
format = AL_FORMAT_STEREO16
cf_level = 1
drivers = alsa
[alsa]  # ALSA backend stuff
device = plug:dmix
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.
=====USB-Headsets-Problems with Linux (Ubuntu)=====
The following is based/verified on Ubuntu, but should be similar on other distributions:
*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.:
$ cat /proc/asound/modules
  0 snd_usb_audio
  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.:
"sudo gedit /etc/modprobe.d/alsa-base.conf"
**add as last line into that file, e.g.:
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====
Jomo
652

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/16454"

Navigation menu