April 2007
Copyright (C) 2007, Motama GmbH, Saarbruecken, Germany http://www.motama.com Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with the Invariant Sections being all sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license can be found in the file COPYING.FDL. THE DOCUMENT IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE DOCUMENT BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE DOCUMENT OR THE USE OR OTHER DEALINGS IN THE DOCUMENT. |
NMM can be used for locally running multimedia applications and for networked multimedia applications. For running networked multimedia applications, properly synchronized clocks of all participating systems are often required, e.g. if you want to achieve lip-synchronous audio and video rendering on different distributed systems. We are using NTP, the network time protocol, for establishing a global time within the network. This document describes how to set up NTP for NMM. We only discuss a simple setup, for further information, please see the official NTP documentation.
When synchronizing the clocks of two systems, one system acts as the server, the other as client. The clock of the client is synchronized to the clock of the server. Optionally, the server can be configured to be synchronized to an NTP server in the Internet. Additional clients can be added easily be performing the same steps as for the first client.
| Next | ||
| NTP Packages for different Operating Systems |