FGCom (before 3.0): Difference between revisions

Jump to navigation Jump to search

FGCom (before 3.0) (view source)

Revision as of 12:28, 18 March 2009

6,464 bytes added ,  18 March 2009
→‎Testing: add chapter "Verifying your Audio-system"
m (→‎Functional Test + User Briefing: correct Win-Explorer dependencies)
(→‎Testing: add chapter "Verifying your Audio-system")
Line 144: Line 144:


===Testing===
===Testing===
====Test the basic function====  
''If in the following some pictures seem to small to read on your screen, click on it and it will enlarge. Then return with the left arrow at the top of your screen.''<br><br>
''(The often so called "-f910 test")''
====Test the basic function====  
Prior to your first FGCom-tests you should verify your audio-system, because the FGCom-installation relies heavily on a good performance of it. If you had already used microphone-recordings or VoIP and thus “trust” your system, then you may pass this chapter and continue with the “-f910”-test. But be sure to return here just as soon as the audio system is not performing as you expected!
(--> [[The "-f910"-Test]])
 
=====Verifying your Audio-System=====
Keep the audio-tools easily accessible for adjustments. Please be aware that, due to the different Operating-Systems multiplied by the different Sound-Cards, there are thousands of different tools available for the following tasks. If you cannot recognize the tools by the sample-pictures, please see your system and/or sound-card documentation for the tools you can use for the following basic tasks:
#Make sure you have '''easy access to your audio-controls''' – and know them.
#From the devices available '''define the audio-devices''' you want to use. You may have an audio-module on your motherboard, and multiple sound-cards,  and headsets, and Dolby-surround, etc. etc. We strongly recommend to use a headset (at least not to use loudspeakers) in order to reduce the very possible problem of feedback noise. A further reduction in noise can be achieved by using USB-headsets.
#'''Adjust''' your master '''volume-control''' and possible sub-controls to please your ears. Check your volume-control-panel for all controls that may influence your sound output. At least there is one master-control affecting all outputs. In addition there may be several outputs with individual adjustments. You may switch all regulators and switches off – and then switch them on one by one to find out which ones you need. You may also look into all tabs of your volume-control-panel, to see if there are features which may not have been used yet (if e.g. you never yet used a microphone, or VoIP, etc.)
#'''Adjust the Microphone''' and “Boost” devices. All modern Operating-Systems do have an integrated audio-recorder for such adjustments – you should be able to make an acceptable speech-recording. Most microphones do need a “boost” device-driver or extra amplifier. It is nice that all systems do provide this capability, but you have to activate it manually (if needed)! Also be aware that some of the devices may be switched off automatically if the system gets rebooted or an application gets closed.
#Finally '''find the “best fit”''' between your hardware, the network, and the FGCom-server response.
 
See the following examples:
 
'''1) Easy access to your audio-controls:''' You may need those controls often, so they should be placed easily accessible. Check if you have the Audio-Icon in your Task-bar:  e.g.
[[image:FGCOM-Audio-Icon.jpg|thumb|center|400px|Audio-Icon]]
If there is no such Icon anywhere on the screen do:
{| align=center width=900 border="1"
|+
|width=300|typical for '''Linux'''
|width=300|typical for '''Windows'''
|width=300|typical for '''MAC'''
|-
|<br>To my knowledge the icon is shown on all graphical systems of all Linux-Distributions. Thus there is no action required.
|Click on Start → Control Panel → Sounds and Audio:
[[image:FGCOM-W-Volume.jpg|thumb|center|250px|Enabel Audio-Icon]]
|}
<br>'''2) Define the audio-devices to use:'''
{| align=center width=900 border="1"
|-
|width=300|Enter [[Command line|command]]: ''gnome-sound-properties''
[[image:FGCOM-U-Prefs.jpg|thumb|center|250px|test devices]]
For each task you can open a selection-menu (on the right the downward arrow) in order to select the wanted device. I suggest to set all the same:
* for a USB-headset you must select the USB-device
* for all others you might first try “Autodetect”
|width=300|Click right onto the audio-icon → Preferences → Audio-tab:
[[image:FGCOM-W-Audio.jpg|thumb|center|250px|set devices]]
Select your Devices for Playback and Mic.
|width=300|
|}
If you did change these device-settings, it is a good idea to reboot the system prior to continue.
<br><br>
'''3) Adjust volume-control'''  (for theses first adjustments you should switch the Mic. off!)
{| align=center width=900 border="1"
|-
|width=300|Click right on Audio-Icon → Open Vol. Ctrl:
[[image:FGCOM-UVolCtrl.jpg|thumb|center|250px|Volume Control]]
The amount of the slider-controls may vary depending on the capabilities of the sound-card or the usage of USB-headsets.
 
The “booster” is available under “Switches”.
|width=300|Click right on the Audio-Icon → Volume-Ctrl. (or type command:  sndvol32)
[[image:FGCOM-W-VolCtrl.jpg|thumb|center|250px|set devices]]
In this example the card overrides the std. Microsoft “Mic.” with “Rear Pink In” because all jacks can accept whatever you like!) - in this case it is the Mic. Be aware of such changes caused by usually “high expense” devices!
 
The “booster” is available under options.
|-
|width=300|Just click onto the green “Test” marks in the above device-selection and adjust  the volume controls for a good sound.
|width=300|Click on tab. Sounds
[[image:FGCOM-W-Sound.jpg|thumb|center|250px|Sound-test]]
Select one of the longer lasting signals (1), then click on 2 and adjust loudness with above slider-controls.
|width=300|
|}
<br>'''4) Adjust the Microphone:'''
<br>Use the volume-control-panels to enable the microphone for this test. Then:
{| align=center width=900 border="1"
|-
|width=300|Open the recorder with the [[Command line|command]]: ''gnome-sound-recorder''
[[image:FGCOM-U-sndctrl.jpg|thumb|center|250px|Recording-test]]
*Record
*Stop
*Play
|width|Open the Recorder with [[Command line|command]]: ''sndrec32''
[[image:FGCOM-W-sndrec.jpg|thumb|center|250px|Recording-test]]
*Start recording (click red point)
*talk some words into the mic
*stop (rectangel)
*spool back ( < < )
*listen  (>)
|width=300|
|}
Try to find the lowest possible microphone-volume for a reasonable speech-replay, without adjusting the loudness-volume from the above set values. If needed add the “booster” or “gain”. But it would be better if you do not need/use the booster, because that will always try to adjust to a recordable volume – even if there are only some background-noises which nobody really wants to hear.
<br><br>
'''5) Find the “best fit”'''
 
Now perform the following “-f910” test and make final adjustments if needed:


--[[User:Jomo|Jomo]] 08:28, 18 March 2009 (EDT)
<br>
=====The "-f910"-Test=====
Prior to executing the following [[Command line|command]] change into the directory, into which the FGCom was installed. This path will then shown up before the "$" sign.
Prior to executing the following [[Command line|command]] change into the directory, into which the FGCom was installed. This path will then shown up before the "$" sign.
In case of a "cvs" installation you have to replace "fgcom" with "sh ./run_fgcom.sh". Then type:
In case of a "cvs" installation you have to replace "fgcom" with "sh ./run_fgcom.sh". Then type:
Line 172: Line 259:
*'''"Reading list of airports .."''' not successful: Check your file “positions.txt” which should be in the same directory in which you installed the FGCom. This is a normal text-file in which you can add missing informations. (Replacing a complete "Windows" position.txt with a "Linux" one can lead to errors, although lines of both files may be exchanged/added).
*'''"Reading list of airports .."''' not successful: Check your file “positions.txt” which should be in the same directory in which you installed the FGCom. This is a normal text-file in which you can add missing informations. (Replacing a complete "Windows" position.txt with a "Linux" one can lead to errors, although lines of both files may be exchanged/added).
*'''"Initializing IAX client"''' not successful: Check if you defined the right server, it must be "-Sfgcom.flightgear.org.uk”. Watch it: The “S” must be capital in Linux, but small for Windows (“-sfgcom.flightgear.org.uk”)!  
*'''"Initializing IAX client"''' not successful: Check if you defined the right server, it must be "-Sfgcom.flightgear.org.uk”. Watch it: The “S” must be capital in Linux, but small for Windows (“-sfgcom.flightgear.org.uk”)!  
*No response '''"Call 0 accepted"''': Check your network.
*No response '''"Call 0 accepted"''': Check your network, especially your firewall for open ports.
*If you did not hear the '''"delayed response"''' echoed back, check the Chapter [[FGCOM#Solving Audio-Problems|Solving Audio-Problems]].
*If you did not hear the '''"delayed response"''' echoed back, check the Chapter [[FGCOM#Solving Audio-Problems|Solving Audio-Problems]].
--[[User:Jomo|Jomo]] 01:01, 7 March 2009 (EST)
--[[User:Jomo|Jomo]] 01:01, 7 March 2009 (EST)
Line 178: Line 265:
====Functional Test + User Briefing====
====Functional Test + User Briefing====


Experiences pointed out, that the cooperation FGCom/FGFS works more reliable, if the FGFS gets started first. So we will start with setting up a test-environment:
Experiences pointed out, that the cooperation FGCom/FGFS works more reliable, if the FGFS gets started first. So we will start with setting up a flight-test-environment:
=====Start the FGFS=====
=====Start the FGFS=====
''If in the following some pictures seem to small to read on your screen, click on it and it will enlarge. Then return with the left arrow at the top of your screen.''<br><br>
We suggest to use the FGrun ([[FlightGear Launch Control]]) to define required and/or proposed settings, in order to avoid typo-errors etc. If you keep the “Show command line” active (compare item 3 following), you also get the correct writing for all the command-options (in case you later want to start from a command-line and/or out of a script). In the following we will just point out those commands which are significant for the FGCom-operation:
We suggest to use the FGrun ([[FlightGear Launch Control]]) to define required and/or proposed settings, in order to avoid typo-errors etc. If you keep the “Show command line” active (compare item 3 following), you also get the correct writing for all the command-options (in case you later want to start from a command-line and/or out of a script). In the following we will just point out those commands which are significant for the FGCom-operation:


If you don't have an Icon available to start the FGrun, then
If you don't have an Icon available to start the FGrun, then
*use a [[command|command-window]] (like above for the FGCom)
*use a [[command|command-window]]
*change into the directory in which FGFS was installed  
*change into the directory in which FGFS was installed  
*and start the program from there:
*and start the program from there:
Jomo
652

edits

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

Navigation menu