Basic overview of a home digital music system

[DYohn]

There has been a lot of discussion about how to set up a digital music system and plenty of confusion on this forum, so I wrote the following (LONG) introduction. I don't claim to be an expert in all variations and there are plenty of options and ideas I have left out, but I have been doing this for ten or so years now and understand the basics. So, here it is:

The basic pieces of a network music system are as follows:
1) The server
2) The router
3) Your home network
4) The player(s)
5) Controllers


1) The server. This can be any type of PC you wish to use. It performs the following functions:

a. It runs server software, which forms the backbone of your ability to easily stream various file formats, sample rates, etc. in an efficient fashion. Examples of server software include Roon Core, Logitech Media Server, Sonos, Plex, and many others.

b. For best results this PC should be used for no function other than as a server and should remain on constantly. This means it is in the user’s best interest to use an energy efficient system with as few moving parts as possible. Some NAS devices can also function as server computers. All server computers can be accessed on your home network and used as an NAS device.

c. The server needs to run an OS such as Windows or MacOS or Linux, and then it must run the server software. For best results the OS should be as lean as possible (using few system resources.)

d. Hardware specs for the server should be whatever is required or recommended by the server software, but in general better performance seems to be had with higher performing hardware (faster processor, motherboard, etc.) and plenty of memory. The system should have ethernet capability and USB ports for external drives, keyboard, mouse etc. as required. In general video optout is just used for setup and maintenance so motherboard built-in video is sufficient.
i. If the server is not located in the listening space, any standard PC configuration can be used, with fan cooling etc.
ii. If the server is in or near the listening space, a silent system is preferred, with passive cooling and a silent power supply.
iii. If you intend to rip CDs using the server it must contain an optical drive.

e.The server should have enough storage space for your local media files, meaning the rips of your CDs, your personal downloads, etc. It also needs storage space for the PC operating system and the server software.
i. Best results are generally obtained by using a small drive for the OS and a separate drive or drives for media storage.
ii. Best results are generally obtained by using SSD drives instead of spinning hard drives. This is because SSD has faster access and transfer times, they generate less heat, and since they have no moving parts they are not prone to mechanical failure (plus they are silent.)
iii. Best results are generally obtained using SATA drives instead of external USB drives, again because of access and data transfer times.


2) The router. This can be any appropriate router/switch including cable or DSL modem router that you choose to use. Faster ethernet speeds generally give better results.

a. The router should connect to the Internet to allow access to Internet streaming services, to data bases used by your server for file tagging, etc.


3) Your home network. This is the ethernet network installed in your house and is the transmission method for the server output.

a. Network speeds can affect streaming quality, so at least a 100baseT system is preferred.

b. For best performance your server should be connected to the router using an Ethernet cable, not via wireless.

c. If possible, your entire network should be hard wired, meaning running Ethernet cables to every desired location for music. Wireless may be used and is generally appropriate for all but the most intense use. Wireless is more prone to drop outs and other artifacts than is a wired system.

d. Wireless access points are a preferred method for wireless distribution, meaning a WPS connection to the main router and then wired connections to the players.


4) The players. Network audio players are computers that run specialized software to receive files from the server and output them to your music system.

a. Players can be specialized devices, either purchased off the shelf or DIY, that run the player software for your chosen server software. For example, Roon requires what is called a Roon Ready player for best results, LMS requires a Squeeze compliant player, Sonos requires Sonos players. Many of these can be used across multiple servers, check with the manufacturer to be sure.

b. Players can also reside on other devices on your network, like PC, tablets or phones. If it can run the required player software, it can be used.

c. Player output is connected to your music system, either to a DAC or preamp via USB or S/PDIF, or in some cases players have analog outputs that connect via RCA or output directly to headphones. iOS devices may connect to the music system via Airplay, and there are many other options depending on the hardware you use.


5) Controllers. There are two types of control interfaces, sources used to rip files to the server, and devices used to remote control players.

a. Source controllers are generally PCs on your network that are used to rip CDs or other content on the server storage. These machines may run your choice of ripping software (iTunes, JRiver, dBPowerAmp, etc.) and they also provide interface with the server for remote administration.

b. Source controllers often also run custom player software such as the Roon App. These can also be used as remote controllers for other players on the network.

c. Source controllers are used to edit or correct file tags if necessary.

d. Remote control devices may also include tablets and phones that connect to players on your network and allow you to control what they are doing.

[brubacca]

Great Synopsis.

[DYohn]

Nov 2, 2019 14:28:09 GMT -5 brubacca said:

Great Synopsis.

Thank you, I know I left plenty out so if anyone wants to add more... that would be great!

[Priapulus]

I have a HTPC that is quiet and powerful, with 24 Tb of harddrive filled with movies and music. Can I add something like Plex so it can also be my whole-house server? Which software would be appropriate?

I used to have a dedicated fileserver, but now that 8 Tb drives are available, it was redundant.

Sincerely
/b

[DYohn]

Nov 2, 2019 14:44:11 GMT -5 Priapulus said:

I have a HTPC that is quiet and powerful, with 24 Tb of harddrive filled with movies and music. Can I add something like Plex so it can also be my whole-house server? Which software would be appropriate?

I used to have a dedicated fileserver, but now that 8 Tb drives are available, it was redundant.

Sincerely
/b

You should be able to, sure.

[mshump]

Nice write up !! Thanks

Mark

[petew]

Nice writeup!

Sonos does not use a server, except as a place to store music files. Sonos will search your network looking for any media and ask if you want to add it to the system. Sonos keeps the index, playlists, and settings on the various playback devices. In fact, if you're streaming from an online source Sonos will function even if it's the only device on your network (no computers at all).

[DYohn]

Nov 3, 2019 11:41:16 GMT -5 petew said:

Nice writeup!

Sonos does not use a server, except as a place to store music files. Sonos will search your network looking for any media and ask if you want to add it to the system. Sonos keeps the index, playlists, and settings on the various playback devices. In fact, if you're streaming from an online source Sonos will function even if it's the only device on your network (no computers at all).

Cool, I did not know that. Thanks.

[Gary Cook]

I guess mine would be classified as "less than basic", I have a MacMini 2012 version (3TB EHDD) connected via wifi to an ATV4k that is plugged into an XMC-1 via a very short (.75 metre) HDMI cable.


Cheers
Gary

[Bonzo]

Nov 2, 2019 12:40:55 GMT -5 DYohn said:

There has been a lot of discussion about how to set up a digital music system and plenty of confusion on this forum, so I wrote the following (LONG) introduction. I don't claim to be an expert in all variations and there are plenty of options and ideas I have left out, but I have been doing this for ten or so years now and understand the basics. So, here it is:

The basic pieces of a network music system are as follows:
1) The server
2) The router
3) Your home network
4) The player(s)
5) Controllers


1) The server. This can be any type of PC you wish to use. It performs the following functions:

a. It runs server software, which forms the backbone of your ability to easily stream various file formats, sample rates, etc. in an efficient fashion. Examples of server software include Roon Core, Logitech Media Server, Sonos, Plex, and many others.

b. For best results this PC should be used for no function other than as a server and should remain on constantly. This means it is in the user’s best interest to use an energy efficient system with as few moving parts as possible. Some NAS devices can also function as server computers. All server computers can be accessed on your home network and used as an NAS device.

c. The server needs to run an OS such as Windows or MacOS or Linux, and then it must run the server software. For best results the OS should be as lean as possible (using few system resources.)

d. Hardware specs for the server should be whatever is required or recommended by the server software, but in general better performance seems to be had with higher performing hardware (faster processor, motherboard, etc.) and plenty of memory. The system should have ethernet capability and USB ports for external drives, keyboard, mouse etc. as required. In general video optout is just used for setup and maintenance so motherboard built-in video is sufficient.
i. If the server is not located in the listening space, any standard PC configuration can be used, with fan cooling etc.
ii. If the server is in or near the listening space, a silent system is preferred, with passive cooling and a silent power supply.
iii. If you intend to rip CDs using the server it must contain an optical drive.

e.The server should have enough storage space for your local media files, meaning the rips of your CDs, your personal downloads, etc. It also needs storage space for the PC operating system and the server software.
i. Best results are generally obtained by using a small drive for the OS and a separate drive or drives for media storage.
ii. Best results are generally obtained by using SSD drives instead of spinning hard drives. This is because SSD has faster assess and transfer times, they generate less heat, and since they have no moving parts they are not prone to mechanical failure (plus they are silent.)
iii. Best results are generally obtained using SATA drives instead of external USB drives, again because of access and data transfer times.


2) The router. This can be any appropriate router/switch including cable or DSL modem router that you choose to use. Faster ethernet speeds generally give better results.

a. The router should connect to the Internet to allow access to Internet streaming services, to data bases used by your server for file tagging, etc.


3) Your home network. This is the ethernet network installed in your house and is the transmission method for the server output.

a. Network speeds can affect streaming quality, so at least a 100baseT system is preferred.

b. For best performance your server should be connected to the router using an Ethernet cable, not via wireless.

c. If possible, your entire network should be hard wired, meaning running Ethernet cables to every desired location for music. Wireless may be used and is generally appropriate for all but the most intense use. Wireless is more prone to drop outs and other artifacts than is a wired system.

d. Wireless access points are a preferred method for wireless distribution, meaning a WPS connection to the main router and then wired connections to the players.


4) The players. Network audio players are computers that run specialized software to receive files from the server and output them to your music system.

a. Players can be specialized devices, either purchased off the shelf or DIY, that run the player software for your chosen server software. For example, Roon requires what is called a Roon Ready player for best results, LMS requires a Squeeze compliant player, Sonos requires Sonos players. Many of these can be used across multiple servers, check with the manufacturer to be sure.

b. Players can also reside on other devices on your network, like PC, tablets or phones. If it can run the required player software, it can be used.

c. Player output is connected to your music system, either to a DAC or preamp via USB or S/PDIF, or in some cases players have analog outputs that connect via RCA or output directly to headphones. iOS devices may connect to the music system via Airplay, and there are many other options depending on the hardware you use.


5) Controllers. There are two types of control interfaces, sources used to rip files to the server, and devices used to remote control players.

a. Source controllers are generally PCs on your network that are used to rip CDs or other content on the server storage. These machines may run your choice of ripping software (iTunes, JRiver, dBPowerAmp, etc.) and they also provide interface with the server for remote administration.

b. Source controllers often also run custom player software such as the Roon App. These can also be used as remote controllers for other players on the network.

c. Source controllers are used to edit or correct file tags if necessary.

d. Remote control devices may also include tablets and phones that connect to players on your network and allow you to control what they are doing.

Consider this thread bookmarked. 2020 marks the year I'm finally going to get time to do this Schiit properly. Tired of having $7000 worth of stuff sitting around doing nothing.

Thank you for starting this thread. 👍

[klinemj]

Nov 3, 2019 11:50:31 GMT -5 DYohn said:

Nov 3, 2019 11:41:16 GMT -5 petew said:

Nice writeup!

Sonos does not use a server, except as a place to store music files. Sonos will search your network looking for any media and ask if you want to add it to the system. Sonos keeps the index, playlists, and settings on the various playback devices. In fact, if you're streaming from an online source Sonos will function even if it's the only device on your network (no computers at all).

Cool, I did not know that. Thanks.

The easiest way I have described Sonos to my non-techie friends is that it's like an "internet receiver" in that it will pull in just about any internet music option (Spotify, Pandora, Tidal, Amazon Music - now even Unlimited, and internet radio stations) + any music I have stored within my house on hard drives. And, while I have liked Sonos for its simplicity (even my kids when they were pre-teen could use it), it's pretty pricey per piece. If I started over, I'd go a different route.

I generally like Roon the best as it's closest to what Sonos can do for multi-room ease of use and it has all the amazing metadata brought in. The only thing I don't like is that it's limited in what sources it draws from (for example, it doesn't have Amazon Unlimited yet, and there's no word yet if or when it will).

But, overall - a GREAT primer on this topic!

Mark

[Boomzilla]

Thanks for the clarifications, DYohn.

1. As I understand you, the "source controller" (used to rip CDs, etc.) can actually reside on the server. Is there any advantage or disadvantage to this?

2. In 1b, you claim that the server should remain on constantly. If one desires immediate music access from the server 24-7, I can understand this. But if listening sessions are to be only occasional, it seems wasteful to allow the server to remain online when not in use?

3. In section 4, you state that the player is typically a computer. But in many (most?) systems, the player need not be a computer, but only a device suitable as a destination to the server software? In other words, and using Roon as an example, any device recognized by Roon as a certified "Roon destination" can become the player. In my case my Oppo UDP-205 would be considered the player?

4. Provided their speed rating is sufficiently high, are all Ethernet switches in the system considered "transparent" to the network? In other words, my server connects via Ethernet to a 16-port gigabit Ethernet switch in my computer room. The cable modem/router is also connected to that switch, but is not used by the server except when accessing the internet. There is an additional 8-port gigabit Ethernet switch in my listening room (connected to the computer room switch via Ethernet cable) that serves all the equipment there (cable TV-box, AirPort Express wireless router, Oppo player, TV, etc.). So the Ethernet connection between the server and the player has no intermediate router - only switches. Is there any inherent advantage or disadvantage in this setup?

Thanks - Boom

[DYohn]

Nov 5, 2019 4:17:29 GMT -5 Boomzilla said:

Thanks for the clarifications, DYohn.

1. As I understand you, the "source controller" (used to rip CDs, etc.) can actually reside on the server. Is there any advantage or disadvantage to this?

2. In 1b, you claim that the server should remain on constantly. If one desires immediate music access from the server 24-7, I can understand this. But if listening sessions are to be only occasional, it seems wasteful to allow the server to remain online when not in use?

3. In section 4, you state that the player is typically a computer. But in many (most?) systems, the player need not be a computer, but only a device suitable as a destination to the server software? In other words, and using Roon as an example, any device recognized by Roon as a certified "Roon destination" can become the player. In my case my Oppo UDP-205 would be considered the player?

4. Provided their speed rating is sufficiently high, are all Ethernet switches in the system considered "transparent" to the network? In other words, my server connects via Ethernet to a 16-port gigabit Ethernet switch in my computer room. The cable modem/router is also connected to that switch, but is not used by the server except when accessing the internet. There is an additional 8-port gigabit Ethernet switch in my listening room (connected to the computer room switch via Ethernet cable) that serves all the equipment there (cable TV-box, AirPort Express wireless router, Oppo player, TV, etc.). So the Ethernet connection between the server and the player has no intermediate router - only switches. Is there any inherent advantage or disadvantage in this setup?

Thanks - Boom

1) For best results the server should not run any other software except perhaps for a player if you choose to play directly from the server. Ripping CDs on the server is common. My server has auto-ripping capability. Again, could you do everything on one machine? Yes. SHould you? Not unless you have to, in my opinion.
2) It should be left on just like an NAS or a router or any other network resource. Could you turn it on and off? Sure. But I say you should set it up and leave it, especially since one purpose of network audio is remote listening.
3) All players are computers. Your oppo is a computer. The player function is software that it can run.
4) The only issue that can be caused by the network is speed for streaming (higher bit rate material requires higher bandwidth) and dropouts due to packet errors or wireless disconnects. If you have a good solid connection it should not matter.

[fbczar]

I know this is resurrecting an old thread, but I though some of you could offer some advice. I am interested in a streamer like the Lumin U1 mini or the Lumin D2. I want to use the streamer with my XMC-2. I do not plan on an outboard DAC. Any comments on the Lumin streamers or comments on competitive models would be appreciated.

[DYohn]

Lumin is a (rather expensive) network music player. It's an internet or server playback device. There are many units like it on the market at various price points. The D2 has a DAC built in, the U1 mini does not. If you use the D2 you could connect the analog outputs to analog inputs on teh XMC-2 OR use the digital out to a digital input on teh XMC-2. If you use the U1 mini you will connect the digital output to a digital input on the XMC-2.

[LuisV]

Nice intro write up! 1000% agreed, wireless is very convenient, but a hardwired ethernet connection is always preferred; wiring a home with a 1GB or 10GB network is relatively easy and inexpensive to do this days.

The server in your analogy, in my humble opinion, if your server or NAS is powerful enough, then no need to worry. I would shy away from Windows and use Ubuntu or similar variant. For a DIY NAS / application server I would use Unraid or FreeNAS; I choose Unraid for my build. Roon Core is running on a Ubuntu VM and my NAS still has plenty of horsepower to do everything else I need it to do.

I wouldn't consider media devices, Oppo in your example, as a computer. I would classify it as a media endpoint as these devices typically run firmware that a manufacturer provides predefined functions in order to use the device; buttons for playback, volume, LCD / LED screen for visual output, etc. etc.

[DYohn]

Thanks for the comments. Yes, my mention of Oppo was in responise to Boomzilla and yes, it is a player not a server. It is a computer, by the way, as are most modern multidisc players and all network players. But it is not a server.

[LuisV]

Aug 16, 2020 8:32:04 GMT -5 LuisV said:

I wouldn't consider media devices, Oppo in your example, as a computer. I would classify it as a media endpoint as these devices typically run firmware that a manufacturer provides predefined functions in order to use the device; buttons for playback, volume, LCD / LED screen for visual output, etc. etc.

Aug 16, 2020 8:40:17 GMT -5 DYohn said:

Thanks for the comments. Yes, my mention of Oppo was in responise to Boomzilla and yes, it is a player not a server. It is a computer, by the way, as are most modern multidisc players and all network players. But it is not a server.

Glad you didn't take my comments negatively DYohn.   Just to confirm, I was referring to computer... I feel a computer is a system that the user can interact with as well as change it's functionality to suit the end users requirements.   A user can't change the function of the, in your example, an Oppo player.  The manufacturer determines the functionality of the device and only they can extend its functionality via updated firmware; however, the end user can't not change the functionality as the firmware is not open to them to change.  It's a closed system to the end user and that I why I would refer to it as a media end point and not a computer... again, just my humble opinion.  

[DYohn]

Semantics, I suppose. I maintain that any device that includes an operating system and that runs aps is a computer. My Oppo does exactly that. A closed system with specialized, limited functions is absolutely still a computer. My company makes such things and sells them buy the thousands to other companies.