4,400
edits
FGCOM Testing: Difference between revisions
Jump to navigation
Jump to search
m
Robot: Cosmetic changes
m (Bot: Automated text replacement (-FlighGear +FlightGear)) |
m (Robot: Cosmetic changes) |
||
| Line 1: | Line 1: | ||
This "FGCOM_Testing" is intended to support FGCOM-users in debugging their FGCOM-System directly after installation, but also for those who want to verify the basic functionality or want to readjust the audio-system. It covers the following 4 areas in more detail: | This "FGCOM_Testing" is intended to support FGCOM-users in debugging their FGCOM-System directly after installation, but also for those who want to verify the basic functionality or want to readjust the audio-system. It covers the following 4 areas in more detail: | ||
#Testing of the standalone FGCOM Installation | # Testing of the standalone FGCOM Installation | ||
#Testing the FGCOM together with the FlightGear Simulator | # Testing the FGCOM together with the FlightGear Simulator | ||
#Adjusting the Microphone and Speaker volumes</ol> | # Adjusting the Microphone and Speaker volumes</ol> | ||
#In the [[#Appendix|Appendix]] you will find supporting informations | # In the [[#Appendix|Appendix]] you will find supporting informations | ||
Of course the prerequisite for the following is that you have already installed the FGCOM (see the [[FGCOM|FGCOM-main-page]]) ! | Of course the prerequisite for the following is that you have already installed the FGCOM (see the [[FGCOM|FGCOM-main-page]]) ! | ||
<br><br> | <br /><br /> | ||
== '''The Initial test of the standalone FGCOM Installation --> the so called "-f910 Test"''' == | == '''The Initial test of the standalone FGCOM Installation --> the so called "-f910 Test"''' == | ||
| Line 15: | Line 15: | ||
: ''fgcom'' | : ''fgcom'' | ||
:: the command ''(in case you installed by using the [[ | :: the command ''(in case you installed by using the [[Scripted Compilation on Linux Debian/Ubuntu|download_and_compile.sh script]] for LINUX-Systems you have to replace the command "fgcom" with "sh ./run_fgcom.sh". Then the complete command would be: "'''sh ./run_fgcom.sh -f910'''")'' | ||
: ''-Sfgcom.flightgear.org.uk'' | : ''-Sfgcom.flightgear.org.uk'' | ||
:: the central server for FGCOM | :: the central server for FGCOM | ||
| Line 41: | Line 41: | ||
Speak into your microphone and your words should be echoed back with a short delay. e.g. say "one" - and you should notice that the "one" is returned '''after''' you finished speaking it. | Speak into your microphone and your words should be echoed back with a short delay. e.g. say "one" - and you should notice that the "one" is returned '''after''' you finished speaking it. | ||
<br>'''If that was OK''' | <br />'''If that was OK''' | ||
*type <nowiki>ctrl-C</nowiki> to exit this Quick-Test command-window | * type <nowiki>ctrl-C</nowiki> to exit this Quick-Test command-window | ||
*and continue with the next chapter: [[#Test the FGCOM together with the FlightGear Simulator|Test the FGCOM together with the FlightGear Simulator]]. | * and continue with the next chapter: [[#Test the FGCOM together with the FlightGear Simulator|Test the FGCOM together with the FlightGear Simulator]]. | ||
<br>'''In case of trouble''' check the following most probable errors: | <br />'''In case of trouble''' check the following most probable errors: | ||
<br> | <br /> | ||
===Error: FGCOM does not start because of OpenAL-version:=== | === Error: FGCOM does not start because of OpenAL-version: === | ||
If you see a message from the Operating-System similar to the following Windows message: | If you see a message from the Operating-System similar to the following Windows message: | ||
"The procedure entry point alcCaptureSamples could not be located in the dynamic link libary Open AL32.dll." | "The procedure entry point alcCaptureSamples could not be located in the dynamic link libary Open AL32.dll." | ||
| Line 56: | Line 56: | ||
''Be aware that the versions and also the names of the modules may change -- so please always check also the description of the module at the right side on that http-page!'' | ''Be aware that the versions and also the names of the modules may change -- so please always check also the description of the module at the right side on that http-page!'' | ||
<br> | <br /> | ||
===Error: Incorrect Home-Directory specified for FGCOM:=== | === Error: Incorrect Home-Directory specified for FGCOM: === | ||
typical for '''Windows'''-Systems: | typical for '''Windows'''-Systems: | ||
| Line 74: | Line 74: | ||
</pre> | </pre> | ||
*The system is right: I gave it (for testing) a wrong directory! | * The system is right: I gave it (for testing) a wrong directory! | ||
*You better correct yours prior to retrying! | * You better correct yours prior to retrying! | ||
===Error: "TYPO" (mistyped command or option) or Network-problem:=== | === Error: "TYPO" (mistyped command or option) or Network-problem: === | ||
<pre> | <pre> | ||
./fgcom - a communication radio based on VoIP with IAX/Asterisk | ./fgcom - a communication radio based on VoIP with IAX/Asterisk | ||
| Line 103: | Line 103: | ||
most likely you may have | most likely you may have | ||
*defined a wrong Frequency to use or you may have forgotten to define one. You '''must define the option -f910''' | * defined a wrong Frequency to use or you may have forgotten to define one. You '''must define the option -f910''' | ||
*forgotten a "-"sign in front of an option | * forgotten a "-"sign in front of an option | ||
*typed a small "-sfgcom..." instead the capital "-Sfgcom..." | * typed a small "-sfgcom..." instead the capital "-Sfgcom..." | ||
*mistyped the Server-Name or defined a wrong FGCOM-Server | * mistyped the Server-Name or defined a wrong FGCOM-Server | ||
*or you may have created your own unique "typo" (lol). | * or you may have created your own unique "typo" (lol). | ||
*or it may indicate a '''Network-Problem''': | * or it may indicate a '''Network-Problem''': | ||
**Check your network by using some other application (e.g. your file browser to look up an usually not used http-address - if you use a recently used address the answer might be out of your locally saved copies - even so the network is not connected! (e.g. use "http://mainz.de/" to test) | ** Check your network by using some other application (e.g. your file browser to look up an usually not used http-address - if you use a recently used address the answer might be out of your locally saved copies - even so the network is not connected! (e.g. use "http://mainz.de/" to test) | ||
*If you use a firewall (what you should - out of general safety reasons!) make sure the ports below are enabled for your PC. | * If you use a firewall (what you should - out of general safety reasons!) make sure the ports below are enabled for your PC. | ||
<pre> | <pre> | ||
| Line 119: | Line 119: | ||
</pre> | </pre> | ||
===Error: "Phone-book" and/or "positions" cannot be found and/or are corrupted:=== | === Error: "Phone-book" and/or "positions" cannot be found and/or are corrupted: === | ||
<pre> | <pre> | ||
./fgcom - a communication radio based on VoIP with IAX/Asterisk | ./fgcom - a communication radio based on VoIP with IAX/Asterisk | ||
| Line 132: | Line 132: | ||
(etc) | (etc) | ||
</pre> | </pre> | ||
*check the directory in which the FGCOM is installed for the files "phonebook.txt" and "positions.txt". These are normal text-files in which you can add missing informations with a standard editor, for Windows you should use the "WordPad" (not the "Editor"). Replacing a complete "Windows" position.txt with a "Linux" one can lead to errors, although lines of both files may be exchanged/added. | * check the directory in which the FGCOM is installed for the files "phonebook.txt" and "positions.txt". These are normal text-files in which you can add missing informations with a standard editor, for Windows you should use the "WordPad" (not the "Editor"). Replacing a complete "Windows" position.txt with a "Linux" one can lead to errors, although lines of both files may be exchanged/added. | ||
===Error: The Sound-Card is not fully compatible:=== | === Error: The Sound-Card is not fully compatible: === | ||
<pre> | <pre> | ||
./fgcom - a communication radio based on VoIP with IAX/Asterisk | ./fgcom - a communication radio based on VoIP with IAX/Asterisk | ||
| Line 148: | Line 148: | ||
Call 0 answered | Call 0 answered | ||
</pre> | </pre> | ||
*Continue checking/adjusting: | * Continue checking/adjusting: | ||
**If everything else works out OK forget this problem (but be aware: The Audio might not function perfectly!) | ** If everything else works out OK forget this problem (but be aware: The Audio might not function perfectly!) | ||
**otherwise check the Internet for new drivers for your sound-card or other fixes. | ** otherwise check the Internet for new drivers for your sound-card or other fixes. | ||
<br> | <br /> | ||
== Test the FGCOM together with the FlightGear Simulator == | == Test the FGCOM together with the FlightGear Simulator == | ||
In the forgoing chapter you checked the FGCOM as a standalone application. Now we will test whether the '''FGFS''' (FlightGear Flight-Simulator) itself and the FGCOM work together, inclusive the PTT-button (PushToTalk, usually the space-bar) and the internal connections via the assigned ports. | In the forgoing chapter you checked the FGCOM as a standalone application. Now we will test whether the '''FGFS''' (FlightGear Flight-Simulator) itself and the FGCOM work together, inclusive the PTT-button (PushToTalk, usually the space-bar) and the internal connections via the assigned ports. | ||
<br> | <br /> | ||
For this test | For this test | ||
<ol><li>start the FGFS with any plane at any airport you like | <ol><li>start the FGFS with any plane at any airport you like | ||
| Line 163: | Line 163: | ||
<li>click in the FGFS menu-bar onto "Equipment" --> "Radio Settings" | <li>click in the FGFS menu-bar onto "Equipment" --> "Radio Settings" | ||
*into the field "COM1" enter the frequency "910.00" then click "Apply" (and "OK" if you want to close the Pop-up.) | * into the field "COM1" enter the frequency "910.00" then click "Apply" (and "OK" if you want to close the Pop-up.) | ||
* '''Ensure the FGFS is the active window''': if something does not work out as expected click with the mouse somewhere into the Main-FGFS-window (that will activate the window) and then retry the last action(s)!!! | * '''Ensure the FGFS is the active window''': if something does not work out as expected click with the mouse somewhere into the Main-FGFS-window (that will activate the window) and then retry the last action(s)!!! | ||
| Line 176: | Line 176: | ||
:anyhow make sure all these 3 places contain the same Port-number !!! | :anyhow make sure all these 3 places contain the same Port-number !!! | ||
<br> | <br /> | ||
<li>Push the PTT ''(normally the Space-Bar (if you reassigned the PTT to another key - use that one!))'' and speak into your microphone: | <li>Push the PTT ''(normally the Space-Bar (if you reassigned the PTT to another key - use that one!))'' and speak into your microphone: | ||
"your words should be echoed back with a short delay. e.g. say "one" - and you should notice that the "one" is returned after you finished speaking it. | "your words should be echoed back with a short delay. e.g. say "one" - and you should notice that the "one" is returned after you finished speaking it. | ||
| Line 187: | Line 187: | ||
:::When pushing the PTT they should switch between ''[SPEAK] unmute mic'' followed by ''[LISTEN] mute mic'' | :::When pushing the PTT they should switch between ''[SPEAK] unmute mic'' followed by ''[LISTEN] mute mic'' | ||
:::If they did not switch you probably use an airplane model that has reassigned the Space-bar to another function: | :::If they did not switch you probably use an airplane model that has reassigned the Space-bar to another function: | ||
:: Otherwise check the “''YourPlane''-set.xml” file in your FGFS/data/Aircraft/YourPlane directory: If you find a line ''<key n="32">'' then this plane is intentionally | :: Otherwise check the “''YourPlane''-set.xml” file in your FGFS/data/Aircraft/YourPlane directory: If you find a line ''<key n="32">'' then this plane is intentionally using "key 32" (Space) for something other than the PTT. Known planes that do that as of Feb. 2009 are: an2, bluebird-base, ogel, OV10.., seafireIIc, spitfireIIa, ufo. There could be others. | ||
<br><br> | <br /><br /> | ||
== Adjust the Microphone and Speaker volumes == | == Adjust the Microphone and Speaker volumes == | ||
Finally we will adjust the Microphone and Loudspeaker volumes to an optimum, as well for yourself as also for your fellow players. | Finally we will adjust the Microphone and Loudspeaker volumes to an optimum, as well for yourself as also for your fellow players. | ||
<br>''(You could perform this test also with the "f910-test" in chapter 1, but with the test-setup in chapter 2 it becomes more realistic!)'' | <br />''(You could perform this test also with the "f910-test" in chapter 1, but with the test-setup in chapter 2 it becomes more realistic!)'' | ||
# Start your FGFS and FGCOM as described in the forgoing chapter(s), the COM1 must be switched to 910.00 and be the active one. | # Start your FGFS and FGCOM as described in the forgoing chapter(s), the COM1 must be switched to 910.00 and be the active one. | ||
| Line 202: | Line 202: | ||
# After the microphone is set, '''adjust the loudspeaker''' volume to a level you prefer. | # After the microphone is set, '''adjust the loudspeaker''' volume to a level you prefer. | ||
# Finally verify both settings by keeping the PTT pressed for about 10 seconds without talking and/or feeding any other sounds into the microphone. | # Finally verify both settings by keeping the PTT pressed for about 10 seconds without talking and/or feeding any other sounds into the microphone. | ||
#*listen for "funny noises" building up over time (hard to describe: some "unverified whoosh" and maybe additional even some sound like "air in a water-pipe" - actually: Whenever you hear anything --> it is no good!!!. | #* listen for "funny noises" building up over time (hard to describe: some "unverified whoosh" and maybe additional even some sound like "air in a water-pipe" - actually: Whenever you hear anything --> it is no good!!!. | ||
#*Mostly these "build up sounds with time" are due to an active microphone booster. Try to keep that booster to an absolute minimum (even better try to switch it off completely if not really needed!) while instead increasing the microphone volume | #* Mostly these "build up sounds with time" are due to an active microphone booster. Try to keep that booster to an absolute minimum (even better try to switch it off completely if not really needed!) while instead increasing the microphone volume | ||
#* but also a rather high adjusted speaker-volume may cause such "funny noises" - try reducing the loudspeaker volume if you cannot solve the problem by adjusting the microphone and/or booster. | #* but also a rather high adjusted speaker-volume may cause such "funny noises" - try reducing the loudspeaker volume if you cannot solve the problem by adjusting the microphone and/or booster. | ||
#*then you might readjust as described in the forgoing items. | #* then you might readjust as described in the forgoing items. | ||
#Now you are ready to talk to others, e.g. set your COM1 to the desired frequency and let your co-players praise you for that "absolute brilliant voice you have"! | # Now you are ready to talk to others, e.g. set your COM1 to the desired frequency and let your co-players praise you for that "absolute brilliant voice you have"! | ||
<br /> | <br /> | ||
| Line 212: | Line 212: | ||
PLEASE: While "on Air" in MP keep the PTT pressed only while actually talking - and never longer than about 20 sec. After some time you will be timed out anyhow - but even before that drastic cutoff you might give your co-players a chance to reply/say something! | PLEASE: While "on Air" in MP keep the PTT pressed only while actually talking - and never longer than about 20 sec. After some time you will be timed out anyhow - but even before that drastic cutoff you might give your co-players a chance to reply/say something! | ||
<br><br> | <br /><br /> | ||
== Appendix == | == Appendix == | ||
=== Tips and Tricks === | === Tips and Tricks === | ||
====Typical Problems==== | ==== Typical Problems ==== | ||
<ol><li>Microphone not plugged or Mute-Key activated: It sounds stupid – but most technical problems are due to such “cannot bee”s – please: Always spend the 2 sec. to check this first! Also some Microphones do have an own "Mute-Key", which sometimes is not obviously to see - check your handbook if your Mic has such a switch. | <ol><li>Microphone not plugged or Mute-Key activated: It sounds stupid – but most technical problems are due to such “cannot bee”s – please: Always spend the 2 sec. to check this first! Also some Microphones do have an own "Mute-Key", which sometimes is not obviously to see - check your handbook if your Mic has such a switch. | ||
</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!). | ||
</li><br><li>Multiple Microphones and/or Loudspeakers plugged to your PC: Be aware that most PC's do have Jack-mechanisms that prevent more than one input and/or output per PC. Try using only one (at best the major one - mostly at the back of the PC) | </li><br /><li>Multiple Microphones and/or Loudspeakers plugged to your PC: Be aware that most PC's do have Jack-mechanisms that prevent more than one input and/or output per PC. Try using only one (at best the major one - mostly at the back of the PC) | ||
</li><br><li>If you changed your Mic/Loudspeaker setup or did plug them into anther jack, it is advisable to restart your PC – just to make sure the system knows what you did! (For Windows-Systems this is usually not necessary - but: It cannot hurt to reassure!) | </li><br /><li>If you changed your Mic/Loudspeaker setup or did plug them into anther jack, it is advisable to restart your PC – just to make sure the system knows what you did! (For Windows-Systems this is usually not necessary - but: It cannot hurt to reassure!) | ||
*If you use USB-headsets you might first try to get FGCOM running with standard Input/output devices – and go back to USB after that. If nothing else it helps to narrow down into the trouble-area! | * If you use USB-headsets you might first try to get FGCOM running with standard Input/output devices – and go back to USB after that. If nothing else it helps to narrow down into the trouble-area! | ||
</li><br><li>Check that none of your Sound-system Inputs/Outputs are set to “Mute”: | </li><br /><li>Check that none of your Sound-system Inputs/Outputs are set to “Mute”: | ||
*For basic systems you might use a '''right''' mouse-click onto the loudspeaker-symbol in the upper or lower position of you screen. | * For basic systems you might use a '''right''' mouse-click onto the loudspeaker-symbol in the upper or lower position of you screen. | ||
**For WIndows-Systems: If that symbol is not there: | ** For WIndows-Systems: If that symbol is not there: | ||
***'''for Vista''': Left mouse-click onto “Start”, type “SndVol.exe” into the line just above the Start-button | *** '''for Vista''': Left mouse-click onto “Start”, type “SndVol.exe” into the line just above the Start-button | ||
***'''for XP:''' | *** '''for XP:''' Left mouse-click onto “Start” then on “Run”, type “SndVol32.exe” into the appearing input-field. | ||
*For some “highly sophisticated (and expensive)” sound-cards you might need to use their unique descriptions. | * For some “highly sophisticated (and expensive)” sound-cards you might need to use their unique descriptions. | ||
*FGCOM does not require a “better” sound-card like e.g. for Music or so – it is all Telephone/TCP-IP talking only – (except some people I know like to play country-music while pushing the PTT – that sounds nice - but still is not really high fidelity!) | * FGCOM does not require a “better” sound-card like e.g. for Music or so – it is all Telephone/TCP-IP talking only – (except some people I know like to play country-music while pushing the PTT – that sounds nice - but still is not really high fidelity!) | ||
</li><br><li>Always make sure that you can record and playback something you talk into the microphone with your basic system tools, completely independent of the FlightGear and/or the “OpenAL”. (See your handbooks for testing your unique system and/or the chapter [[#Where to find the volume controls|Where to find the volume controls]]) | </li><br /><li>Always make sure that you can record and playback something you talk into the microphone with your basic system tools, completely independent of the FlightGear and/or the “OpenAL”. (See your handbooks for testing your unique system and/or the chapter [[#Where to find the volume controls|Where to find the volume controls]]) | ||
</li><br><li>If the connection is noisy or poor quality: | </li><br /><li>If the connection is noisy or poor quality: | ||
*First retest your sound-setup as described [[#Adjust the Microphone and Speaker volumes|above]] | * First retest your sound-setup as described [[#Adjust the Microphone and Speaker volumes|above]] | ||
*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 | * a (digital) USB-headset may help avoiding noise and feedback problems | ||
*if stereomix is enabled on your sound-card - try to disable it | * 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: | ||
*After starting the FGFS click onto “File” in the FGFS menu-bar, then onto “Sound Configuration”: Adjust the upper slide-control to a proper volume. Be aware that this setting will get lost when you exit via “X” - always exit via “File” → “Exit/Quit”. | * After starting the FGFS click onto “File” in the FGFS menu-bar, then onto “Sound Configuration”: Adjust the upper slide-control to a proper volume. Be aware that this setting will get lost when you exit via “X” - always exit via “File” → “Exit/Quit”. | ||
*To the opposite you may adjust the volume of your FGCOM by changing the “-o” and/or “-i” options to values between 0 and 1 (see the [[#The Initial test of the standalone FGCOM Installation --> the so called "-f910 Test"|FGOM command at the beginning of this wiki-page]]). | * To the opposite you may adjust the volume of your FGCOM by changing the “-o” and/or “-i” options to values between 0 and 1 (see the [[#The Initial test of the standalone FGCOM Installation --> the so called "-f910 Test"|FGOM command at the beginning of this wiki-page]]). | ||
</li><br><li>It is known that the AirToAir frequency 123.45 does not yet work - reason unknown and fix-date unknown. (This affects all Operating Systems!) | </li><br /><li>It is known that the AirToAir frequency 123.45 does not yet work - reason unknown and fix-date unknown. (This affects all Operating Systems!) | ||
</li><br><li>Did you know? If no Tower-frequency is in range, you also can use the VOR-frequencies - just put them into your COM1 or COM2. | </li><br /><li>Did you know? If no Tower-frequency is in range, you also can use the VOR-frequencies - just put them into your COM1 or COM2. | ||
</li></ol><br> | </li></ol><br /> | ||
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==== | ==== High Quality Sound-Cards ==== | ||
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) | ||
*during reboot or restart they may initiate with values out of a special profile instead of reusing the “last used” values | * 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) | * 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!) | So know your standard settings and check if they have changed (without your written permission!) | ||
<br><br> | <br /><br /> | ||
====Special for Linux (.alsoftrc)==== | ==== Special for Linux (.alsoftrc) ==== | ||
(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'''" | ||
(remember that the “show hidden files” must be enabled!) | (remember that the “show hidden files” must be enabled!) | ||
*if ".alsoftrc" does not exist | * if ".alsoftrc" does not exist | ||
**Check if there is a (old version) ".openalrc" | ** 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": | *** 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 devices '(alsa)) | ||
(define alsa-out-device "plug:dmix") | (define alsa-out-device "plug:dmix") | ||
**if not, create a new ".alsoftrc" file and insert something like the following into it: | ** if not, create a new ".alsoftrc" file and insert something like the following into it: | ||
format = AL_FORMAT_STEREO16 | format = AL_FORMAT_STEREO16 | ||
cf_level = 1 | cf_level = 1 | ||
| Line 272: | Line 272: | ||
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. | ||
<br><br> | <br /><br /> | ||
====USB-Headsets-Problems with Linux (Ubuntu)==== | ==== USB-Headsets-Problems with Linux (Ubuntu) ==== | ||
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 Recording is ok '''and''' the f910-Test looks alright in the window, '''but''' there is no delayed response: | * 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.conf" | "sudo gedit /etc/modprobe.d/alsa-base.conf" | ||
**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> | <br /> | ||
====Festival==== | ==== Festival ==== | ||
*If you use '''Festival''' (the Text/Speech AddOn) | * If you use '''Festival''' (the Text/Speech AddOn) | ||
**and | ** and | ||
*** it works OK when running alone | *** it works OK when running alone | ||
*** but runs int error "can't open /dev/dsp" when running with FGFS (and/or other applications) | *** but runs int error "can't open /dev/dsp" when running with FGFS (and/or other applications) | ||
| Line 293: | Line 293: | ||
(Parameter.set 'Audio_Command "aplay -q -c 1 -t raw -f s16 -r $SR $FILE") | (Parameter.set 'Audio_Command "aplay -q -c 1 -t raw -f s16 -r $SR $FILE") | ||
(Parameter.set 'Audio_Method 'Audio_Command) | (Parameter.set 'Audio_Method 'Audio_Command) | ||
</ol><br><br> | </ol><br /><br /> | ||
=== 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! | ||
| Line 307: | Line 307: | ||
|- | |- | ||
|width=300|Enter [[Command line|command]]: ''gnome-sound-properties'' | |width=300|Enter [[Command line|command]]: ''gnome-sound-properties'' | ||
[[ | [[File: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 first try setting all to "Autodetect". Then click onto the green "Test"-button. If you need to make changes, reboot the PC after each change! | 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 first try setting all to "Autodetect". Then click onto the green "Test"-button. If you need to make changes, reboot the PC after each change! | ||
|width=300|<br>Click right onto the audio-icon → Preferences → Audio-tab: | |width=300|<br />Click right onto the audio-icon → Preferences → Audio-tab: | ||
[[ | [[File:FGCOM-W-Audio.jpg|thumb|center|250px|set devices]] | ||
See the two Tabs (in the picture) '''Audio''' and '''Stimme''' (voice), you need to change in both! | See the two Tabs (in the picture) '''Audio''' and '''Stimme''' (voice), you need to change in both! | ||
|width=300|Open with Menu --> System-preferences: | |width=300|Open with Menu --> System-preferences: | ||
[[ | [[File:FGCOM-OVol.jpg|thumb|center|250px|set devices]] | ||
Switch between "Output" and "Input" and select the wanted device('s) in the field "Chose a device...". | Switch between "Output" and "Input" and select the wanted device('s) in the field "Chose a device...". | ||
|} | |} | ||
If you did change these device-settings, it is a good idea to reboot the PC and retest the settings prior to continue. | If you did change these device-settings, it is a good idea to reboot the PC and retest the settings prior to continue. | ||
<br><br> | <br /><br /> | ||
'''<li>Adjust volumes and switch boosters''' | '''<li>Adjust volumes and switch boosters''' (for the first loudspeaker-adjustments you should switch off the Mic.!) | ||
{| border="1" | {| border="1" | ||
|- | |- | ||
|width=300|Click right on Audio-Icon → Open Vol. Ctrl: | |width=300|Click right on Audio-Icon → Open Vol. Ctrl: | ||
[[ | [[File:FGCOM-UVolCtrl.jpg|thumb|center|250px|Volume Control]] | ||
The amount of the slider-controls vary depending on the capabilities of the sound-card or the usage of USB-headsets. | The amount of the slider-controls vary depending on the capabilities of the sound-card or the usage of USB-headsets. | ||
The “booster” is available under “Switches” (you may have to activate it first under "Preferences"). | The “booster” is available under “Switches” (you may have to activate it first under "Preferences"). | ||
|width=300|Click right on the Audio-Icon → Volume-Ctrl. (or type command: sndvol32) | |width=300|Click right on the Audio-Icon → Volume-Ctrl. (or type command: sndvol32) | ||
[[ | [[File:FGCOM-W-VolCtrl.jpg|thumb|center|250px|set devices]] | ||
In this example the card overrides the std. Microsoft “Mic.” with “Rear Pink In”. Be aware of such changes caused by usually “high expense” devices! | In this example the card overrides the std. Microsoft “Mic.” with “Rear Pink In”. Be aware of such changes caused by usually “high expense” devices! | ||
The “booster” is available under options. | The “booster” is available under options. | ||
|width=300|Use the above shown window to adjust. | |width=300|Use the above shown window to adjust. | ||
|} | |} | ||
<br><br> | <br /><br /> | ||
'''<li>Verify the basic Mic/Loudspeaker functionality:''' | '''<li>Verify the basic Mic/Loudspeaker functionality:''' | ||
<br>Use the volume-control-panels to enable the microphone for this test. Then: | <br />Use the volume-control-panels to enable the microphone for this test. Then: | ||
{| border="1" | {| border="1" | ||
|- | |- | ||
|width=300|Open the recorder with the [[Command line|command]]: ''gnome-sound-recorder'' | |width=300|Open the recorder with the [[Command line|command]]: ''gnome-sound-recorder'' | ||
[[ | [[File:FGCOM-U-sndctrl.jpg|thumb|center|250px|Recording-test]] | ||
*Record | * Record | ||
*Stop | * Stop | ||
*Play | * Play | ||
|width|Open the Recorder with [[Command line|command]]: ''sndrec32'' | |width|Open the Recorder with [[Command line|command]]: ''sndrec32'' | ||
[[ | [[File:FGCOM-W-sndrec.jpg|thumb|center|250px|Recording-test]] | ||
*Start recording (click red point) | * Start recording (click red point) | ||
*talk some words into the mic | * talk some words into the mic | ||
*stop (rectangel) | * stop (rectangel) | ||
*spool back ( < < ) | * spool back ( < < ) | ||
*listen (>) | * listen (>) | ||
|width=300|There is no basic recording program available with OSX. | |width=300|There is no basic recording program available with OSX. | ||
|} | |} | ||
[[de: | [[de:FGCOM Testing]] | ||