FGCom 3.0: Difference between revisions

Jump to navigation Jump to search

FGCom 3.0 (view source)

Revision as of 19:10, 22 April 2014

9 bytes removed ,  22 April 2014
Moved Linux Installation to FAQ per page owner's (F-JJTH) suggestion
(Undo revision 69844 by Rogerx (talk) This is not related to FGCom but "How to use radio", this page is designed to explain "How to use FGCom")
(Moved Linux Installation to FAQ per page owner's (F-JJTH) suggestion)
Line 31: Line 31:
== Installation ==
== 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.
=== Linux ALSA Sound ===
By defaults, most Linux ALSA systems should just work.  This is because by default Linux ALSA utilizes the DMix plugin when there is no $HOME/.asoundrc file.  Linux ALSA also, by default when using DMix unless further customized, resamples all audio to 48000hz.  If this is not the case, or if you speculate customizations have been performed by your Linux distribution, you may need to read further below on how to ensure ALSA's DMix and DSnoop plugins are used with FlightGear & FGCom.  The common side effect of possible customizations, FGCom does not playback (or record) 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 ? =
= How to start FGCom builtin ? =
Line 272: Line 218:


Be sure the slider "ATC" from the File > Sound configuration dialog is at full right.
Be sure the slider "ATC" from the File > Sound configuration dialog is at full right.
== Linux ALSA Sound ==
By defaults, most Linux ALSA systems should just work.  This is because by default Linux ALSA utilizes the DMix plugin when there is no $HOME/.asoundrc file.  Linux ALSA also, by default when using DMix unless further customized, resamples all audio to 48000hz.  If this is not the case, or if you speculate customizations have been performed by your Linux distribution, you may need to read further below on how to ensure ALSA's DMix and DSnoop plugins are used with FlightGear & FGCom.  The common side effect of possible customizations, FGCom does not playback (or record) 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!




[[fr:FGCom 3.0]]
[[fr:FGCom 3.0]]
[[Category:FGCom]]
[[Category:FGCom]]
Rogerx
24

edits

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

Navigation menu