On 7/30/06, <b class="gmail_sendername">Mike Miller</b> <<a href="mailto:mbmiller@taxa.epi.umn.edu">mbmiller@taxa.epi.umn.edu</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'm probably missing some info here because I just skimmed the thread, but<br>I would think that a good plan would be to have a central server that<br>smaller computers can read files from. I can't envision one server<br>
sending out many video and audio outputs simultaneously, but I can see it<br>serving many files at once to smaller machines that then display the files<br>on their default audio and video outputs.<br><br>I ripped all my CDs to MP3 and put them on one machine, then I put a small
<br>computer on my stereo system, and I have several other computers. When I<br>want to play a song, I can play it from where I am (computer or stereo) by<br>grabbing the file from the server. I can also connect remotely from out
<br>of town and download MP3s. A couple of weeks ago I was out of town with a<br>rental car. I had forgotten to bring some CDs, so from the hotel room, I<br>downloaded some of my songs, burned a CD and listened to it in the car the
<br>next day.<br><br>Mike<br></blockquote></div><br>One of my design goals is to avoid having a computer in every room where I want to listen to music or watch video. I would much rather run A/V cables from a central server out to various wall jacks, where I can simply plug in speakers and/or a TV.
<br clear="all"><br>-- <br>Dave Sherman<br>MCSA, MCSE, CCNA<br>Linux: Because rebooting is for adding new hardware.