Appendix E: Informational Notes393AudioAudio Playback and Capture IssuesFeatures that May Interrupt an Audio ConnectionIf you use any of the following features while connected to an audiodevice, your audio connection may be interrupted. Raritan recommendsyou do not use these features if you are connected to an audio device: Video Auto-Sense Extensive use of the local port Adding usersIssues when Using a Capture Device and Playback DeviceSimultaneously on a TargetOn some targets, the simultaneous connection of capture devices andplayback devices may not work due to the USB hub controller and how itmanages the USB ports. Consider selecting an audio format thatrequires less bandwidth.If this does not resolve the issue, connect the D2CIM-DVUSB CIM'skeyboard and mouse connector to a different port on the target. If thisdoes not solve the problem, connect the device to a USB hub andconnect the hub to the target.Audio in a Linux EnvironmentThe following are known issues when using the audio feature in a Linux®environment. Linux® users, use the default audio device for playback. Sound maynot come through if a non-default sound card is selected. SuSE 11 clients require Javas_1_6_0-sun-alsa (ALSA support forjava-1_6_0-sun) to be installed via YAST. For Logitech® headsets with a built in a mic, only the Mono Captureoption is available. In order to display the device, if you are running SUSE 11 and anALSA driver, log out of KX III, then log back in.Additionally, if you connect and disconnect the audio device anumber of times, the device may be listed several times vs. just onceas it should. Using the audio feature with a Fedora Core® 13 target set to mono16 bit, 44k may cause considerable interference during playback.
