Audio Hardware Considerations for a Thin Client
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
This topic discusses considerations for audio hardware for a Windows Embedded CE powered thin client.
Audio Hardware Requirements
Although audio output hardware is not required for thin client devices, we recommend it. Remote Desktop Protocol (RDP) supports audio playback redirection. This enables a server application to stream audio through either the server audio output hardware or the client audio output hardware.
If audio is supported, the thin client must support the playback of 8-bit, monophonic ("mono"), and pulse-coded modulation-formatted audio files. The following list shows the audio output requirements for a thin client:
- The thin client device must have a single-channel, 8-bit digital-to-analog converter (DAC)
- The thin client device must have a 22.05 KHz sampling rate
Note
For better results, upgrade to 16 bits per sample and 44.1 KHz sample rate.
For information about audio playback options, see Windows Media Technologies.
For information about how to develop device drivers for a specific type of device, see Windows Embedded CE Drivers.
See Also
Concepts
Hardware Architecture Diagram for a Thin Client
Other Resources
Core OS Services
Developing a Board Support Package
Developing a Device Driver
Developing an OEM Adaptation Layer
CETK Tests