24
edits
FGCom 3.0: Difference between revisions
Jump to navigation
Jump to search
→FGCom builtin: Added Linux ALSA Sound and elevated topic headings to appropriate levels
mNo edit summary |
(→FGCom builtin: Added Linux ALSA Sound and elevated topic headings to appropriate levels) |
||
| Line 26: | Line 26: | ||
* If you are not using FlightGear 3.0 or higher you have to read the [[FGCom_3.0#FGCom_standalone|FGCom standalone section]] and follow "If FlightGear is not installed" instructions. | * If you are not using FlightGear 3.0 or higher you have to read the [[FGCom_3.0#FGCom_standalone|FGCom standalone section]] and follow "If FlightGear is not installed" instructions. | ||
= FGCom | = FGCom 3.0 Builtin = | ||
This is concerning the now accepted internal FGCom within FlightGear-3.0 versions and later versions of FlightGear. | |||
== Installation == | |||
The good news here is that FlightGear has now an FGCom client built in the software. That means there is no additional installation step. If you have installed FlightGear you can immediately use FGCom. | The good news here is that FlightGear has now an FGCom client built in the software. That means there is no additional installation step. If you have installed FlightGear you can immediately use FGCom. | ||
=== How to start FGCom builtin ? | === Linux ALSA Sound === | ||
(Reference [[Linux software audio mixing with FlightGear]]) <br /> | |||
Check your Home-directory (“~/” or $HOME) for a file "'''.alsoftrc'''" | |||
(Remember that the “show hidden files” must be enabled!) | |||
Copied over from [[FGCOM Testing]] or FGCOM Testing Wiki page. | |||
==== If using Creative Labs' OpenAL library (or older OpenAL version) ==== | |||
Check if you are using the old Creative Labs OpenAL library (or old version) which uses the ".openalrc" configuration file. If so, you can put something like this within ".openalrc": | |||
$HOME/.openalrc | |||
<pre> | |||
(define devices '(alsa)) | |||
(define alsa-out-device "plug:dmix") | |||
(device alsa-in-device "plug:dsnoop") | |||
</pre> | |||
==== If using OpenAL Soft (or newer OpenAL version) ==== | |||
It is more likely users of more recent Linux distributions are using this newer OpenAL Soft package, instead of the previously mentioned older Create Labs' OpenAL. (Hence, the likely rational for renaming the default configuration file to something other than the more common previous naming format.) | |||
Copy either the be /etc/openal/alsoft.conf, /usr/share/doc/openal-1.15.1-r2/alsoftrc.sample.bz2, or create a new $HOME/.alsoftrc file and insert the following: | |||
<pre><nowiki> | |||
format = AL_FORMAT_STEREO16 | |||
cf_level = 1 | |||
drivers = alsa | |||
[alsa] | |||
device = plug:dmix | |||
capture = plug:dsnoop | |||
</nowiki></pre> | |||
[NOTE: format is now "sample-type = uint16", and cf_level would appear not needed for typical users, or only desired for headphone users.] | |||
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 /> | |||
==== Linux ALSA Audiophiles avoiding Dmix ==== | |||
For audiophiles using Linux ALSA and with their custom $HOME/.asoundrc file preventing DMix usage, make sure you have both specified "device = plug:dmix" as well as "capture = plug:dsnoop". Per ALSA's page, "dsnoop is the equivalent of the dmix plugin, but for recording sound." Without specifying using dsnoop for the capture device alongside your $HOME/.asoundrc file preventing DMix usage, you will likely only get silence played back when usage FGCom. FGCom is not working at this point, as the sound device is likely still locked by your $HOME/.asoundrc file and only recording silence or playing back silence during the echo test! | |||
==== Using ALSA Custom "plug:" Filters ==== | |||
The OpenAL Soft (or the newer version of OpenAL) $HOME/.alsoftrc file also accepts using other $HOME/.asoundrc "plug:" incanatations, such as sections containing Dmix - alsa.opensrc.org's "pcm.dmixs51" customization for using DMix with 5.1 Surround Sound, and called as: | |||
<pre>$ aplay -D "plug:dmixs51" Some_PCM_WAV_File.wav </pre> | |||
$HOME/.alsoftrc | |||
<pre> | |||
"device = plug:dmixs51" | |||
</pre> | |||
Just remember to also uncomment layout_surround51, and note the likely fact FlightGear is still only using Stereo sound (or two channel audio) and is only set here for an example! | |||
= How to start FGCom builtin ? = | |||
# Start FlightGear | # Start FlightGear | ||
# Open the dialog located in "Multiplayer > FGCom Settings" | # Open the dialog located in "Multiplayer > FGCom Settings" | ||
| Line 42: | Line 96: | ||
FGCom will be automatically enabled for your future sessions until you uncheck the "Enable" checkbox. | FGCom will be automatically enabled for your future sessions until you uncheck the "Enable" checkbox. | ||
= How to test your setup ? = | |||
In order to check that your microphone and speakers are correctly connected and functional you can test it with the following steps: | In order to check that your microphone and speakers are correctly connected and functional you can test it with the following steps: | ||
| Line 53: | Line 107: | ||
# Close the dialog | # Close the dialog | ||
= How to use FGCom builtin ? = | |||
Once you started FGCom from the [[FGCom_3.0#How_to_start_FGCom_builtin_.3F|How to start FGCom builtin]] procedure, you can simply use your radio stack like it done in real life. | Once you started FGCom from the [[FGCom_3.0#How_to_start_FGCom_builtin_.3F|How to start FGCom builtin]] procedure, you can simply use your radio stack like it done in real life. | ||
| Line 62: | Line 116: | ||
[[File:FGCom dialog.png|thumb|FGCom dialog]] | [[File:FGCom dialog.png|thumb|FGCom dialog]] | ||
= Dialog details = | |||
The dialog located in "Multiplayer > FGCom Settings" provide some features described here: | The dialog located in "Multiplayer > FGCom Settings" provide some features described here: | ||