Difference between revisions of "Media Directors"
Perspectoff (Talk | contribs) |
Perspectoff (Talk | contribs) |
||
| Line 9: | Line 9: | ||
While a dedicated core can be hidden in a closet or somewhere, each Media Director is generally attached to a TV or entertainment center. As such, it has requirements similar to a [http://en.wikipedia.org/wiki/Home_theater_PC Home Theater PC] (stylish case, good graphics and sound cards, low noise, low heat production). | While a dedicated core can be hidden in a closet or somewhere, each Media Director is generally attached to a TV or entertainment center. As such, it has requirements similar to a [http://en.wikipedia.org/wiki/Home_theater_PC Home Theater PC] (stylish case, good graphics and sound cards, low noise, low heat production). | ||
| − | Unlike a Home Theater PC, however, the Media Director does not require a large storage capacity, nor an extremely powerful processor | + | Unlike a Home Theater PC, however, the Media Director does not require a large storage capacity, nor an extremely powerful processor. Most storage and processing functions are provided by the Core (or hybrid), not the Media Director. A lot of the functions performed by a standalone home theater PC are performed by the Core, for the entire LinuxMCE system. Since a Media Director does not have to do all of these functions, it does not need all the hardware and capabilities that a standalone home theater PC has. |
| − | A Media Director, for example, does not need a large hard drive. (The Core does the PVR functions and all network media storage functions for the entire system | + | A Media Director, for example, does not need a large hard drive. (The Core does the PVR functions, and all network media storage functions, for the entire system. Only the Core needs a large hard drive storage capacity.) The Core also generally has the TV video card for the entire system. A Media Director does not typically need one. Also, because Media Directors can netboot from the Core (and therefore essentially act as thin clients), they do not even require an OS. |
| − | A Media Director does need a good (nVidia) graphics card and a good sound card, however. Outputs to TV and stereo are directly from a Media Director. | + | A Media Director does need a good (nVidia) graphics card and a good sound card, however. Outputs to TV and stereo are directly from a Media Director, so quality output cards are needed. |
| − | A Media Director also provides the interface for input devices. Remote controls (USB-UIRTs, bluetooth devices, etc.) are | + | A Media Director also provides the interface for input devices. Remote controls (USB-UIRTs, bluetooth devices, etc.) in general are connected to a Media Director. |
| − | Therefore, choosing a PC | + | Therefore, choosing or building a PC that will be used as a Media Director must be done carefully with respect to the input and output capabilities of that PC. |
| − | + | A Media Director usually sits next to your TV. It therefore must have a stylish case, must be whisper-quiet (either with very quiet fans or a fanless heat sink), have low heat emission (which usually implies low power consumption), and be small and unobtrusive. | |
| − | These demands are more easily met with a Media Director than with a Home Theater PC, since many of the functions of a HTPC | + | These demands are more easily met with a Media Director than with a Home Theater PC, since many of the functions of a standalone HTPC have been moved to the Core of a LinuxMCE system, reducing the hardware requirements of each Media Director. A typical Media Director therefore is much less expensive than is a typical Home Theater PC. |
| + | |||
| + | 'Thin client nature of a Media Director' | ||
Although the [[AV devices]] are connected to the Media Director(s), they are nevertheless administered by the Core. In the LinuxMCE admin panel, A/V devices settings are specified separately from the settings of the media directors to which they are connected. This is done because the Core keeps track of the controls and settings of every device on the system. Because it is possible to netboot Media Directors from the Core, all settings for all Media Directors and all devices must centrally be stored in the Core. | Although the [[AV devices]] are connected to the Media Director(s), they are nevertheless administered by the Core. In the LinuxMCE admin panel, A/V devices settings are specified separately from the settings of the media directors to which they are connected. This is done because the Core keeps track of the controls and settings of every device on the system. Because it is possible to netboot Media Directors from the Core, all settings for all Media Directors and all devices must centrally be stored in the Core. | ||
Revision as of 03:26, 27 April 2008
A Media Director is a PC which channels the audio and video content managed by the LinuxMCE system to the audiovisual devices which are connected to it.
Although a LinuxMCE system can only have one Core (or hybrid Core/Media Director), there can be many Media Directors in the system.
There can be a separate Media Director in each room or entertainment area, for example, each connected directly to the TV, stereo, or other AV devices in that area. Content is output to the AV devices through the graphics and sound card of the local Media Director PC.
Each Media Director is connected to the LinuxMCE Core server through the home automation/multimedia LAN.
While a dedicated core can be hidden in a closet or somewhere, each Media Director is generally attached to a TV or entertainment center. As such, it has requirements similar to a Home Theater PC (stylish case, good graphics and sound cards, low noise, low heat production).
Unlike a Home Theater PC, however, the Media Director does not require a large storage capacity, nor an extremely powerful processor. Most storage and processing functions are provided by the Core (or hybrid), not the Media Director. A lot of the functions performed by a standalone home theater PC are performed by the Core, for the entire LinuxMCE system. Since a Media Director does not have to do all of these functions, it does not need all the hardware and capabilities that a standalone home theater PC has.
A Media Director, for example, does not need a large hard drive. (The Core does the PVR functions, and all network media storage functions, for the entire system. Only the Core needs a large hard drive storage capacity.) The Core also generally has the TV video card for the entire system. A Media Director does not typically need one. Also, because Media Directors can netboot from the Core (and therefore essentially act as thin clients), they do not even require an OS.
A Media Director does need a good (nVidia) graphics card and a good sound card, however. Outputs to TV and stereo are directly from a Media Director, so quality output cards are needed.
A Media Director also provides the interface for input devices. Remote controls (USB-UIRTs, bluetooth devices, etc.) in general are connected to a Media Director.
Therefore, choosing or building a PC that will be used as a Media Director must be done carefully with respect to the input and output capabilities of that PC.
A Media Director usually sits next to your TV. It therefore must have a stylish case, must be whisper-quiet (either with very quiet fans or a fanless heat sink), have low heat emission (which usually implies low power consumption), and be small and unobtrusive.
These demands are more easily met with a Media Director than with a Home Theater PC, since many of the functions of a standalone HTPC have been moved to the Core of a LinuxMCE system, reducing the hardware requirements of each Media Director. A typical Media Director therefore is much less expensive than is a typical Home Theater PC.
'Thin client nature of a Media Director'
Although the AV devices are connected to the Media Director(s), they are nevertheless administered by the Core. In the LinuxMCE admin panel, A/V devices settings are specified separately from the settings of the media directors to which they are connected. This is done because the Core keeps track of the controls and settings of every device on the system. Because it is possible to netboot Media Directors from the Core, all settings for all Media Directors and all devices must centrally be stored in the Core.
| Generic PC | Other Media Directors |
