Filter
Top Products
Appendix A: Informational Notes
199
Audio in a Linux Environment
The following are known issues when using the audio feature in a Linux
®
environment.
Linux
®
users, use the default audio device for playback. Sound may
not come through if a non-default sound card is selected.
SuSE 11 clients require Javas_1_6_0-sun-alsa (ALSA support for
java-1_6_0-sun) to be installed via YAST.
For Logitech headsets with a built in a mic, only the Mono Capture
option is available.
If you are running SUSE 11 and using an ALSA driver, log out of KX
II and then log back in in order to display the device. Additionally, if
you connect and disconnect the audio device a number of times, the
device may be listed several times vs. just once as it should.
Using the audio feature with a Fedora Core 13 target set to mono 16
bit, 44k may cause considerable interference during playback.
Note: This feature is available with the KX II 2.4.0 (and later).
Audio in a Mac Environment
Following are known issues in a Mac
®
environment.
On Mac clients, only one playback device is listed on the Connect
Audio panel when accessing the device through the Virtual KVM
Client (VKC) and Multi-Platform Client (MPC). The device listed is
the default and is displayed on the Connect Audio panel as Java
Sound Audio Engine.
Using audio on a Mac target through Skype
®
may cause the audio to
be corrupted.
Note: This feature is available with the KX II 2.4.0 (and later).
Audio in a Windows Environment
On Windows
®
64-bit clients, only one playback device is listed on the
Connect Audio panel when accessing the device through the Virtual
KVM Client (VKC) and Multi-Platform Client (MPC). The audio device is
the default device and is listed on the Connect Audio panel as Java
Sound Audio Engine.
Note: This feature is available with the KX II 2.4.0 (and later).