FGCOM Testing: Difference between revisions

Jump to navigation Jump to search
3,022 bytes added ,  18 October 2009
→‎Tips and Tricks: merge problem descriptions from FGCOM to here
(→‎Tips and Tricks: merge problem descriptions from FGCOM to here)
Line 200: Line 200:


=== Tips and Tricks ===
=== Tips and Tricks ===
====Typical Problems====
<ol><li>Microphone not plugged: It sounds stupid – but most technical problems are due to such “cannot bee”s – please: Always spend the 2 sec. to check this first!
<ol><li>Microphone not plugged: It sounds stupid – but most technical problems are due to such “cannot bee”s – please: Always spend the 2 sec. to check this first!
</li><br><li>Plug/Jack connections are often the cause for trouble: Try to re-seat your plugs and (if possible) try to use another jack (after cleaning the plug!).
</li><br><li>Plug/Jack connections are often the cause for trouble: Try to re-seat your plugs and (if possible) try to use another jack (after cleaning the plug!).
Line 217: Line 218:
*try routing your Mic/Speaker cables away from electro-smog (Fans, AC/DC modules, motors, lamps, etc.)  
*try routing your Mic/Speaker cables away from electro-smog (Fans, AC/DC modules, motors, lamps, etc.)  
*even placing your sound-card into another plug-position may help
*even placing your sound-card into another plug-position may help
*a (digital) USB-headset may help avoiding noise and feedback problems
*if stereomix is enabled on your sound-card - try to disable it
</li><br><li>Most PC's are set up that you need to keep your PTT (PushToTalk) button pushed as long as you talk. But there are also sound-cards which open for talk with the first push/release and close it with the second push/release. Test your system how it works (may be while trying to record something or while testing according to the [[Adjust the Microphone and Speaker volumes|above]]).
</li><br><li>Most PC's are set up that you need to keep your PTT (PushToTalk) button pushed as long as you talk. But there are also sound-cards which open for talk with the first push/release and close it with the second push/release. Test your system how it works (may be while trying to record something or while testing according to the [[Adjust the Microphone and Speaker volumes|above]]).
</li><br><li>If the FGFS sound-volume does not match your FGCOM-volume:  
</li><br><li>If the FGFS sound-volume does not match your FGCOM-volume:  
Line 226: Line 229:
Try to keep in mind: FGCOM is proven to work! So if there are problems look also for surrounding PC-features like unique hardware, software, etc.
Try to keep in mind: FGCOM is proven to work! So if there are problems look also for surrounding PC-features like unique hardware, software, etc.
<br><br>
<br><br>
====High Quality Sound-Cards====
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 (.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.
<br><br>
====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>
====Festival====
*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)
=== Where to find the volume controls ===
=== Where to find the volume controls ===
Please be aware that FGCOM is used on many very different PC's, Notebooks, etc. under very different Operating-Systems and with very different Sound-Cards. So the following basic concepts may not fit your actual system 100%. In addition you may have to check your actual System and/or unique Sound-Card manuals!
Please be aware that FGCOM is used on many very different PC's, Notebooks, etc. under very different Operating-Systems and with very different Sound-Cards. So the following basic concepts may not fit your actual system 100%. In addition you may have to check your actual System and/or unique Sound-Card manuals!
652

edits

Navigation menu