• Computer Audiophile Pocket Server - C.A.P.S.

    Over the last several months I've researched different combinations of motherboards, computer cases, audio cards, and accessories that go along with these components. The goal of all this research was to put together a hardware and software music server solution that I would actually use and the Computer Audiophile readers could actually use. I would do the leg work, test & listen to everything, and provide the information for CA readers to put together the exact same music server. This sounds somewhat simple until one considers all the requirements that go into such an audiophile solution. Great sound, great looking, no moving parts, silent, fairly inexpensive, and 100% of the components must be available today. Along the way this server was named the Pocket Server by a colleague who was very surprise at its small size when I pulled it out of my carry-on luggage. The server is a bit larger today than it was at that time but the name hasn't changed. What follows is the story of the Computer Audiophile Pocket Server and all the information required to recreate the $1,500 C.A.P.S solution.


    Jack of All Trades Master of None

    Like many audiophiles I am never satisfied with the status quo. The status quo in computer based audio is to purchase a Windows based PC or a Macintosh, plug it in, and let 'er rip. That type of a solution works wonderful for the vast majority of the world's population and it's one I recommend frequently when the situation arises. Moving beyond the status quo many audiophiles including myself customize standard Macs and PCs until they're satisfied with the sound quality. This customization still does not address many of the issues inherent in a machine built for general computing and is often like polishing a turd. The CA Pocket Server Project began with a completely blank whiteboard. This way I had no turds to polish or in audiophile terms I had no jitter to clean up from the start. It's always better to build a fanless system rather than install inches of acoustical foam, fight with noise, and worry about other issues related to fans. That's the general thought process I used to approach this project. Plus, the always pertinent acronym K.I.S.S. Keep It Simple Stupid.



    The Computer Audiophile Pocket Server requirements were non-negotiable. I had to satisfy these requirements or the project would be a failure. I also elected to use many components that I haven't already discussed. I didn't want to rehash The Zalman or hFX based music servers I wrote about in 2008 and 2009. Those servers are still great, but don't meet all the C.A.P.S. requirements.

    01. Absolutely silent.
    02. Capable of great sound.
    03. Great looking.
    04. No moving parts.
    05. Fairly inexpensive.
    06. No legacy components.
    07. Easy to operate.
        a.Directly or
    08. Easy to assemble / install
        a.Assembly / installation by one's self or
        b.Assembly / installation by local computer shop, son, daughter, neighbor, or friend.
    09. Small size.
    10. Low power consumption.
    11. Low heat.
    12. Accept an add-in card for audio or additional capabilities. Hardware & Software must accept appropriate add-in cards.
    13. Play 16/44.1, 24/44.1, 24/88.2, 24/96, 24/176.4, and 24/192 all bit perfect.


    Operating System

    The first step in the process was to test different operating systems. I rules out previous versions of Windows, including the apparent audiophile standard XP, because they were not current. Copies of Windows XP (OEM) are still floating around some of the online shops, but I was ready to retire XP anyway. That left Windows 7 as the Microsoft based candidate. Building a Mac OS X based machine (Hackintosh) is of no interest to me as it violates the Terms Of Service of OS X and is more of a tweaker's system than most audiophiles are willing to accept. Beyond the mainstream consumer operating systems I used used a variant of Berkeley Unix called FreeBSD in addition to a few distributions of Linux. I ruled out FreeBSD fairly quickly. After using it for a few hours as a music server I concluded FreeBSD was better left to host web servers and other business type applications. I am very fond of FreeBSD and I really wanted to like it as a music server OS but squeezing a square peg in a round hole wasn't a goal of the CA Pocket Server Project. I spent much more time researching and using Linux based operating systems than all the others combined. As I said at RMAF 2009, and I still believe today, Linux is the future for music servers. The only caveat is Linux requires quite a bit of knowledge to setup as a music server. The amount of knowledge required is a show-stopper for 99% of the Earth's population let alone analog loving audiophiles. However, if I could satisfy the C.A.P.S. requirements I was willing to attempt writing an extremely thorough how-to Linux guide for CA readers to build this music server. The Linux based operating systems I used are Debian Linux, Voyage Linux, Puppy Linux, Arch Linux, openSUSE, Ubuntu Studio, and probably a couple more that I can't remember at this time. The final selection of an operating system for the C.A.P.S. server came down to Windows 7 and Voyage Linux.

    Voyage Linux is an incredibly small operating system. It can fit on a tiny USB memory stick, compact flash drive, or any hard drive currently available. The initial installation requires about 128 Megabytes of disk space, not to be confused with 128 Gigabytes. Voyage installs as a barebones operating system. The user must add or update audio features such as Music Player Daemon (MPD), Advanced Linux Sound Architecture (ALSA), and other tools like NCMPC and Minion. There are countless options when using Linux. This is a great thing for most Linux users but can be overwhelming to those trying it for the first time. I forced myself to use Voyage Linux for many weeks. Without the option to jump over to a Mac or Windows based server one can become very well versed in Linux music servers. On the contrary one can quit using a Linux music server due to frustration if one doesn't have the necessary time and skills to work through problems. The Voyage based system I setup satisfied all but three of the stated C.A.P.S. requirements. Requirements 7,12, and 13 were constant battles. I tried a few different audio cards and had varying levels of success with each of them. I used an ESi MAYA44 and RME 9632 for much of the time. I was unable to pass 24/176.4 digital audio out of the ESi MAYA44. The MAYA44 data sheets proclaim support up to 24/192, but the user manual states clearly on page 34, "Sample rate supports : 32, 44.1, 48, 88.2, 96, (192)kHz *Coaxial Output only." Without 24/176.4 the MAYA44 card failed the requirement. The RME 9632 audio card was a different story. About 100 hours into the configuration nightmare I was able to pass bit perfect audio on all required sample rates. Configuring the RME 9632 in Linux was extremely frustrating. There are bits and pieces of outdated user generated documentation all over the Internet. If there is demand I will create my definitive guide to the RME 9632 on Linux. There are software, firmware, and hardware incompatibilities to work through. I'm really happy I put in the time to make it work on the C.A.P.S. server as I learned quite a bit in the process. Once I had the card working on all the required sample rates I still had problems changing sample rates on the fly when I switched audio tracks. I could not get this to work no matter what I tried. I did create scripts to change sample rates but each one had to be called up via command line before playing a track that required a sample rate change. This mix of problems is what lead me to exclude Linux from the list of possible operating systems. Requirements 12 and 13 combined equate to a system that is not easy to use. Audio cards with Linux support that also support the required sample rates are few and far between. The cards that do exist are not user friendly enough for most people to use on a daily basis. Canned servers, that one can purchase off the shelf, based on Linux and cards such as the RME 9632, RME HDSP AES-32, Lynx AES16 (with OSS drivers), or even the ESi Juli@ card have a bright future. Creating this type of solution at home for one's self is not for the average audiophile seeking to listen to music rather than fiddle with a computer. That said, I continue to use Linux in my listening room next to my other servers.

    Note: The ESi Juli@ card supports all the required sample rates but can be very hard to obtain. I was unable to procure one during the several months of this project. Even with a Juli@ card a Linux based solution still does not meet the C.A.P.S. requirements.

    Windows 7 satisfies all of the software based requirements. It is capable of great sound, it's a current OS, easy to operate and install, works with more hardware than any other OS, and is capable of bit perfect playback at all required sample rates when configured properly. I selected the more efficient 32-bit version of Windows 7 Ultimate as the operating system of choice for the C.A.P.S. server. More than anything the 64-bit version ruled itself out because of the minimum hardware requirements for a 64-bit OS. I could not use the hardware I wanted and still use the 64-bit version of Windows 7. Even if the hardware supported 64-bit Windows 7 I still think I would use the 32-bit version. There are no benefits to using a 64-bit operating system on the C.A.P.S. server. I selected J River Media Center 14 as the playback and library management application for the C.A.P.S. server. MC 14 has become my new go-to Windows based music application because of its features, flexibility, and bit perfect playback.



    The motherboard is the most critical component of the C.A.P.S. server. Without the right motherboard most of the requirements can't met. Readers not schooled in computer hardware should know a motherboard is the main board to which everything in a computer connects. The motherboard dictates what CPU can be used, how much memory can be used, how many and what type of hard drives can be used, and everything else that goes together to build a working computer. The first criterion I used to determine the best motherboard for the C.A.P.S. server was number four, no moving parts. There are many methods to eliminate moving parts from a motherboard such as the addition of passive cooling used in servers based on the Zalman TNN300 or hFX chassis. Adding passive or active cooling only increases complexity. I wanted a motherboard with no moving parts out of the box. Such a motherboard had to include passive cooling as part of the board's design. This requirement reduced the number of qualifying motherboards down to a handful. I had previously built a Linux based music sever using a motherboard from the swiss company PC Engines. These boards are very small, have incredibly low power requirements, but have too many limitations for the C.A.P.S. server. PCI slots, memory slots, hard drive capabilities, and operating system limitations were too much to overcome. One capability I really like using with a current PC Engines board I have is Power over Ethernet (PoE). This board receives all its power via an Ethernet cable. It's a nice bonus in the aesthetics department when one can remove the power cable from a component. After much research and testing I selected the mini-itx Intel D945GSEJT motherboard for the C.A.P.S. server (Photo 1) (Photo 2). This board has a built-in, non-removable, Intel Atom N270 1.6 GHz CPU that is passively cooled with low profile attached heat sinks. No CPU fan required. The Intel D945GSEJT has two SATA hard drive ports. Connecting standard SATA solid state hard drives (SSD) eliminates another source of moving parts from the server. Spinning hard drives are a source for noise, greater power requirements, increased heat, and can limit the computer case options. One feature that elevates the Intel D945GSEJT motherboard above others is the built-in full size PCI slot. This satisfies the requirement for add-in audio cards or additional capabilities. By additional capabilities I am talking about a PCI FireWire card to connect a FireWire DAC or FireWire hard drive for people using USB DACs.

    Power requirement for the Intel D945GSEJT is very flexible. One can use a traditional computer power supply that connects to the board's 2x2 power port. These traditional power supplies are rarely fanless, rarely silent, and can decrease the number of computer case options due to mounting requirements. The Intel D945GSEJT also accepts an external 12 volt power supply similar to most laptops on the market. A silent fanless external power brick was easily my choice to power the C.A.P.S. server.

    Other notable features of the Intel D945GSEJT include on-board S/PDIF digital audio output headers. Header is another term for pins on the motherboard to which one can connect devices. This output supports 16/44.1, 24/48, and 24/96 sample rates. A special cable is required (Photo 1) (Photo 2) to use this S/PDIF output as there are no built-in S/PDIF ports. A full-mini PCI Express slot is available for wireless cards or other devices like a hardware decoder to increase video playback capabilities. One of the USB headers on the D945GSEJT can be used for an eUSB solid state drive. I purchased an eight GB eUSB drive for this server (Photo 1) (Photo 2), but did not use it with the Windows 7 installation. Windows 7 will not install to a USB drive even if it's placed directly on the motherboard. I have installed Linux to this tiny drive without any issues. An underrated feature of small mini-itx motherboards is the network speed capabilities. Many small boards only contain 10/100 Mbps network cards. The Intel D945GSEJT has an on-board 10/100/1000 Mbps card commonly referred to as a gigabit Ethernet card.

    The maximum amount of random access memory (RAM) the Intel D945GSEJT will accept is two GB in its only memory slot. The decision to use two GB of RAM doesn't require any thought or further discussion here. Just add to cart, it's cheap. Selecting a hard drive to meet the no moving parts requirement is easy if one has unlimited funds. Fortunately Solid State Drives (SSD) continue to decrease in price every week. At the time of this writing an OCZ Vertex Turbo 60GB SSD is $219. This is not the exact drive I used in the C.A.P.S. server but it's contains the same amount of disk space as the one I used. If I were putting together the C.A.P.S. server today I would purchase the OCZ drive previously mentioned. There is currently no way store most people's music collections on local solid state hard drives. The available sizes just aren't large enough without spending thousands of dollars on convoluted PCI/e SSD devices. That's why I selected a 60GB SSD. Most music must be stored elsewhere. My music is located on a Network Attached Storage (NAS) device. If an external spinning USB or FireWire drive is necessary then so be it. At least C.A.P.S. server is free from internal moving parts for now. In the future it will be possible to house all one's music locally on solid state storage.

    Audio card selection for the C.A.P.S. server was fairly easy for me, a Lynx AES16. I am a strong supporter of the Lynx AES16 PCI card for its sound quality and its advanced capabilities. The Lynx enables one to use an external clocking device and supports dual wire AES. I used both of these features during the dCS component review. Along with the Lynx AES16 card I also recommend a custom cable from a place like Redco. Redco will make a cable with only one or two AES wires and a clock wire if desired for about $60. That said, there are many more audio cards available. I hesitate to say it but I did use the Merging Technologies Mykerinos card and Pyramix software on the C.A.P.S. server for a few weeks. Wonderful sound, but it doesn't meet many of the requirements of this project. An audio card I would really like to use in the C.A.P.S. server is the ASUS Xonar Essence St. I currently have the STX PCIe version that will not work in the C.A.P.S. server as it doesn't have a PCIe slot. A few weeks ago ASUS provided me a prerelease ASIO driver for the STX card. I was very pleased to see the card now outputting bit perfect audio at 16/44.1, 24/96, and 24/192. According to ASUS 24/88.2 and 24/176.4 support will be part of the final ASIO driver version. The reason I mention all of this about a card that won't work in the C.A.P.S. server is because this driver also works for the ST PCI version of the Xonar Essence card. Since I haven't heard the ST version I can't comment on the sound quality. However if the quality is similar to the STX version with the new ASIO driver I will highly recommend the ASUS Xonar Essence ST card and consider it a great option for the C.A.P.S. server. The ST PCI version of the card is available for around $200 at many online stores.

    During this project I researched a countless number of computer cases. I'm glad I did the research, but I could have saved all that time by selecting the case I originally wanted from day one of the project. The Origenae M10 computer case was clearly the best case for the C.A.P.S. server. Audiophiles not only like great sound, we like excellent build quality and products that look just as good as our audio components. The all aluminum (5mm) Origenae M10 case meets or exceeds all the requirements set out for the C.A.P.S. server. The case ships with a 60mm fan, but it's only required if the internal components need additional air flow. I never took the fan out of the box. The M10 is built for a mini-itx motherboard such as the Intel D945GSEJT. Installation is very simple. Origenae provides the four required screws to attach the board to the bottom of the case. The 2.5" 60GB SSD selected for the C.A.P.S. server screws easily onto the inside panel right next to the SATA power and data cable ports on the motherboard (Photo). Also included is a mountable tray to hold a slim slot-loading CD/DVD drive. I didn't install such a drive as I wanted to keep things very simple and I had no need for an internal CD/DVD drive. I used a USB CD/DVD drive to install Windows and I use a different computer to rip my CDs to the easily accessible NAS device. If I did install a DVD drive I would select the Pioneer DVR-TS08 slim slot-loading SATA drive for under $60. The M10 case features a very nice looking front display and hidden infrared sensor. I was unable to utilize these features because the Intel D945GSEJT motherboard has a power incompatibility with the M10. The M10 ships with its own 150 watt external power supply but I was unable to make it work with the Intel D945GSEJT motherboard. The D945GSEJT would not accept power via the 2x2 connector and the internal case electronics required a 20/24 pin motherboard connection, that the D945GSEJT doesn't have, to function properly. This incompatibility may have a silver lining. Audiophiles are always seeking ways to turn off unneeded features or capabilities and frequently use single purpose components such as a DAC with separate power supply or separate external clock. Turning off a component's display is nothing new to audiophiles either. This time there is no option to turn the display on or use the included remote control. I don't know if the lack of these features reduces any electrical noise inside the case but I'm willing to bet an argument could be made in support of such a reduction. Again, this is strictly because I selected a motherboard that was not 100% compatible with the M10 case. I've read other reports of these features working very well. In fact with a compatible motherboard it would be possible to control applications like J River Media Center via the infrared remote control. The Origenae M10 case supports half-hight PCI cards sitting vertically in the motherboard's PCI slot. I placed an ASUS Xonar HDAV 1.3 Slim card into the PCI slot and it lined up perfectly with the hole to screw the card into place stabilizing it with the unique internal metal frame of the case. The M10 can also accommodate full size PCI cards like the Lynx AES16 and ASUS Xonar Essence ST by use of a PCI riser card (Photo). A PCI riser card simply enables the PCI card to mount horizontally instead of its native vertical placement. I know of no detrimental effects by using such a riser card. I was initially concerned about heat dissipation as most of the motherboard rests underneath the horizontally mounted Lynx AES16 card. Thus far I've yet to experience any heat related issues. I've even listened to four hours straight of 24/176.4 HRx material outputting dual wire AES to a DAC without a single hiccup and the M10 case is cool to the touch. Inside the case the Lynx AES16 card is no hotter than any other installation I've seen. The bottom of the Origenae M10 case features four metal with rubber bottom feet. The feet are tall enough to allow placement of the case on short carpeting and the rubber bottom of the feet enable one to place the case on any surface without scratching. I currently place the M10 case on carpet in my listening room instead of behind a wall where my other music servers reside. The case looks very nice and I have no reason to hide such a component. This placement also allows me to use short AES cables from my Lynx AES16 card to my DAC. Overall I don't consider the power incompatibility an issue. I would purchase this case without the extra features were it available in such a configuration. Plus, I personally user remote desktop for control of the server and wouldn't use the IR receiver or front panel anyway.

    Use of a monitor is not something I normally consider with my music servers. The Intel D945GSEJT does have analog DSUB and digital DVI video outputs. One of these is certainly required for system setup and could continue to be used if necessary. Seeking to add something extra to the C.A.P.S. server I contacted the nice people at Mimo. A few days later an iMo 7" Pivot Touch USB monitor arrived at my door. On paper or computer screen this touchscreen monitor seems too good to be true for only $199. Unfortunately it is too good to be true. I used the iMo 7" Pivot Touch on Windows and Mac system before concluding it wasn't my cup of tea. Connected to the C.A.P.S. server I had nothing but trouble using this little touchscreen. Initial setup wasn't very smooth, but I was eventually able to see my desktop on the iMo. Next I went through all the calibration steps to fine tune the touchscreen. Calibration is pretty simple, but when it came to actual use the iMo was a nonstarter. If I had infant size fingers I would like the monitor about 10% more than I currently like it. I don't have huge fingers but they are too large to click on a single track easily. Forget about navigating a menu. I had to touch the screen about one inch away from my intended target. This was troubling when I had to touch the lower right corner. My finger needed to be an inch off the screen over the non-touchscreen frame of the monitor. The only good thing I can say about the iMo Pivot Touch 7" touchscreen is that it may work as neat display similar to how Jeff Kalt of Resolution Audio used the non-touchscreen version at CES this year. I do not recommend people purchase this monitor before using it themselves. Needless to say the iMo 7" Pivot Touch did not make the cut to be part of the C.A.P.S. server.



    Compared to a Zalman TNN300 based silent music server the C.A.P.S. server comes out very well. The two main benefits of the Zalman baed server are disk space and the ability to use PCI Express cards in addition to PCI cards. The Zalman is also capable of handling more memory. Both servers are absolutely silent with no moving parts. The Origenae M10 based C.A.P.S. server is far more visually appealing than a Zalman TNN300. The Zalman case is no longer manufactured although there are plenty left in the supply chain here in the U.S. The C.A.P.S. server case is $320 and the Zalman TNN300 is $690. Not a single component in the Zalman servers is less expensive than coresponding C.A.P.S. serve component. The C.A.P.S. server (9.5" x 4" x 9.8" w feet, 6.6 lbs.) consumes far less space than a TNN300 (13" x 9" x 18.5" 32.5 lbs.). The CA Pocket Server is an excellent way to use a Lynx card in one's system without planting a huge PC tower next to audio components. I think both the C.A.P.S. and Zalman based servers are capable of similar great sound quality.



    The Computer Audiophile Pocket Server project was frustrating at times but well worth the time, money, and effort. Make no mistake the C.A.P.S. server will never be a commercial product that benefits Computer Audiophile financially. This server was created to be a great solution for myself and CA readers alike. There are an unlimited number of ways to change this configuration or adjust it to one's personal needs. No single configuration is the right configuration for everyone. Despite some technical terms weaved into the article this is a really easy music server to build as a whole or in part. I know many people who like to dig into projects like this and I also know many people who want nothing to do with a computer project. Fortunately the C.A.P.S. server was created with both groups of people in mind. Using off the shelf parts currently available to anyone CA readers can undertake this project themselves or simply call up a local computer shop and have them put it together. Whether one builds it, buys it, or brushes it off is irrelevant. The Computer Audiophile Pocket Server's purpose is to increase one's enjoyment of our wonderful hobby.





    The Computer Audiophile Pocket Server piece by piece


    Power Supply


    Solid State Drive

    PCI Riser

    Digital Audio Card

    Custom AES Cable

    Computer Case

    Music Application


    Other bits and pieces used during the C.A.P.S. Project that did not make the final build.

    Hardware Decoder

    Solid State Drive

    Solid State Drive

    Solid State Drive

    Wireless Card

    Wireless Antenna



    Click To Enlarge Photos

    C.A.P.S. Server in my listening room.

    C.A.P.S 01   C.A.P.S 01   C.A.P.S 01   C.A.P.S 01


    C.A.P.S 01  


    Stock Photos of Origenae M10

    C.A.P.S 01   C.A.P.S 01


    C.A.P.S 01   C.A.P.S 01   C.A.P.S 01   C.A.P.S 01   C.A.P.S 01




    Comments 291 Comments
    1. silverarrows's Avatar
      silverarrows -
      I've been looking at what would be needed to build a Windows 7 based server and this is exactly the type of thing I was looking for. For me I would probably lean towards a Zotac IONITX board with the NVIDIA graphics card. It also has built in s/pdif optical/coax outputs to give some time to eventually put in the Lynx AES. I would also use iTunes as it is bit perfect, from my understanding, with Windows 7 32-bit.<br />
      <br />
      Thanks for this Chris!
    1. IamKirk's Avatar
      IamKirk -
      Can you expand any more on your linux OS experiences. I see Arch Linux there. How did you like it? I tried it once and got it all going, except it had trouble with mounting through fstab.
    1. ldolse's Avatar
      ldolse -
      If you haven't been able to acquire the Juli@ I'd recommend this site:<br />
      http://www.djdeals.com/egosystemsJULI@.htm<br />
      Found via pricegrabber.com, and I'm almost certain I acquired my Juli@ from them a year or so ago. The North American ESI Disti is KaySound - http://www.kaysound.com/.<br />
      <br />
      I'm curious as to why the Linux system would fail your requirements even with the ESI card. With Voyage Linux, were you able to run that on the Intel board? I know it can be difficult to get Voyage running on systems the distribution owners didn't specifically target.<br />
      <br />
      This may sound like a repeat of the complaint with the Peachtree DAC, but I'd really like to hear more about how these different Operating Systems/new hardware combos sound in a shootout, since you have the luxury of listening to them side by side, something quite difficult for the majority of us to duplicate. I'm particularly interested in Linux - despite the shortcomings you highlighted it's of interest to a number of readers, and the extra effort/shortcomings may be worthwhile for some readers if the sound quality is there.
    1. The Computer Audiophile's Avatar
      The Computer Audiophile -
      Hi ldolse - Nice to see you commenting on this article as I know you are a big supporter of Linux and likely understand it as well or better than many readers. I did check every source in the country for Juli@ cards and nobody had them in stock. I couldn't even get one from the distributor because it didn't have them either. <br />
      <br />
      The Linux system with a Juli@ would fail the requirements for the C.A.P.S. because it wasn't user friendly enough. It could certainly be made user friendly enough but not by the average CA reader. I don't think the average reader can setup a NAS connection that references a stored encrypted password file and mounts at boot time without pulling their hair out. This is one of many issues that users would run into and that can't really be novice-proof because they require user specific information a user may not even know. I've been asked what an IP address is many times :~) You and I can do this stuff blind-folded but not most of the CA readers. Plus, a really tweaked Linux system is the topic of a different article. <br />
      <br />
      The sound quality from my Voyage Linux server outputting USB to the dCS system was truly wonderful.
    1. Jammrock's Avatar
      Jammrock -
      Excellent write-up!<br />
      <br />
      You actually can run Win7 from a USB drive, and ergo an eUSB drive, with a little work. Here are some online guides I have seen.<br />
      <br />
      http://kmwoley.com/blog/?p=345<br />
      <br />
    1. The Computer Audiophile's Avatar
      The Computer Audiophile -
      Hi Jammrock - Thanks for the kind words and links. I appears that the links only show how to create a bootable installation USB drive. They don't say it's possible to actually install Windows on a USB drive. Did I misread the links?
    1. Jammrock's Avatar
      Jammrock -
      One of those is definitely an install link. Must have copied the wrong one. The other I have not tested (I lack a big enough USB drive at the moment) but I will try if I can dig up a drive.<br />
      <br />
      There is an option two, and that is boot from a VHD on the USB drive. VHD = Virtual Hard Drive. VHD's are the files used for all Microsoft virtualization from Virtual Server/PC to Hyper-V. It's a bit trickier, but I'm told it works.<br />
      <br />
    1. rudyy's Avatar
      rudyy -
      Very nice, Chris.<br />
      My first post on this forum was to seek information on custom-built computers. regardless of operating systems.<br />
      I really wanted to buy one with Linux.<br />
      I did what I could (for someone who knew little about the numerous so-called Linux distributions), but ultimately could not find a Linux distribution I could work with. <br />
      My notes tell me I tried Ubuntu 9.04 and several others, including at least one that was specific to media applications. (Ubuntu had been recommended to me at some online web site.)<br />
      For a music player I tried acidrip, sound juicer, amarock2, audacity, rythmbox and potamus; none of them did everything I needed.<br />
      I finally gave up on Linux, just as I had done about 7 years ago when I bought a Red Hat version on floppy disk; I couldn't get it to fully load.<br />
      For at least one reason (related to golf) I have to keep a Windows OS computer, so I keep a Vista laptop, but I'd sure like to rid myself of it and just rely on my iMac for everything, despite iTunes' inability to keep my music library organized.
    1. johniboy's Avatar
      johniboy -
      Hi Chris,<br />
      <br />
      Nice setup and thank you for sharing your experience in such detail! A quick question:<br />
      I believe you control the music server using remote desktop / iphone or ipod touch, right? So you need a wireless connection. Does the motherboard have a wlan chip? If not, do you use a wlan usb stick for this purpose?<br />
      <br />
      When I was experimenting with my music server, I first used a single core centrino cpu. This was not satisfying, because the wlan stick / remote desktop application took up too much cpu usage when scrolling though my albums. It resulted in hickups. Then I switched to a dual core and the problem was gone. One cpu for the remote, one for the playback... Did you experience anything similar with the atom cpu??
    1. aps's Avatar
      aps -
      Chris<br />
      <br />
      Thanks for the excellent article. I have, to-date, assumed that my next audio computer would use eithe firewire and/or async USB to get digital audio to an external DAC. This would, seemingly, reduce cost and product great sound. What, then, was the thinking behind using AES16 sound-card (which is, undoubtably, a great piece of kit)?<br />
      <br />
      Regards,<br />
    1. bmckenney's Avatar
      bmckenney -
      I have a serious question. Is there any benefit to this type of server over a Mac Mini with some tweaks like a SSD? It seems to me a Mac Mini (headless) would be cheaper and simpler and still meet all the requirements. Add in an async USB or FW DAC. Anyway, just curious what your thoughts are on the pro's and con's of a custom server like the Pocket Server verus a Mac Mini. Especially interested in sound quality differences but I understand the player software won't be the same.<br />
      <br />
    1. EuroChamp's Avatar
      EuroChamp -
      Hey Chris,<br />
      <br />
      i am entirely of your opinion. Your how-to is perfect!<br />
      <br />
      There is only one question: you do not use the touchscreen, so how are you controlling the system? It is relatively easy to integrate an IR control, but useless without a screen.<br />
      <br />
      THX<br />
      <br />
    1. The Computer Audiophile's Avatar
      The Computer Audiophile -
      Hi johniboy - The motherboard has a mini-PCIe slot that accepts a wireless card. I listed this wireless card at the bottom of the review as a component that didn't make it into the final server build. The card snaps into place right on the board. It's simple to install, but I didn't need it because I have a wired gigabit Ethernet switch close to my system. I'm glad you brought up the remote control & weak processor issue. I originally had the issues you described. Then I disabled or removed many of the programs that run in the background and eat system resources. Right now the server hiccups a tiny bit upon the initial Remote Desktop connection but after than I am able to browse my collection in a controlled manner without issues. I can reproduce the hiccups if I start clicking all over the place and scrolling really fast through all the albums lie a madman. It just takes a little usage to understand how best to operate the server via remote desktop. I don't think it's a problem now or I would never have published such a system.<br />
      <br />
      Hi APS - Good question about why I use an internal sound card. Right now this card allows playback of all critical sample rates into 99% of the DACs on the market. It also has advanced features that allow me to externally clock the card and use dual wire AES into a DAC like a dCS Debussy pictured in the article. I am a big fan of Async USB and FireWire DACs. Either would work great with this server. However, the FireWire DAC options are somewhat limited. I highly recommend products from Daniel Weiss and the Sonic Studio Model Four. Both have FireWire inputs. Also, the Async DACs I've review and listened to over the years are really wonderful. Right now support for 176.4 and 192 isn't widely available. If a reader wants this capability he is limited to very few DACs that may not meet his sonic quality standards or price point.<br />
      <br />
      Hi Bryan - Oh no a "Serious Question!" Only joking of course. Thanks for the Mac Mini related question. There are many benefits to this system over a Mac Mini, but most of them are subjective. The objective benefits are a totally fanless / no moving parts design, 100% silent from any distance, support for internal audio cards, and it doesn't set off those Mac allergies in many audiophiles :~) Also, as I touched on above a Mac Mini limits one to USB or FireWire. For many people this is totally acceptable. I wasn't satisfied with that limitation, but I did build in the ability to remove or exclude the Lynx card in favor of a PCI FireWire card. That would bring the cost down close about $600. In terms of sound quality both a Mini and the Pocket Server are capable of great sound. they both sound different that's for sure. <br />
      <br />
      Hi Bernhard - I am controlling via Remote Desktop from another computer. The Pocket Server does have analog DSUB and digital DVI video outputs that allow it to connect to many displays. Running J River in theater Mode with the server connected to a nice display would be a really neat and visually appealing system.<br />
      <br />
    1. Part-Time Audiophile's Avatar
      Part-Time Audiophile -
      How does it sound compared to your reference Audiophile Computer (whatever it was you used in the symposium)? Comparisons, or it didn't happen! Schnell! Schnell!<br />
      <br />
      Also, I have a local dealer working on a similar design. Pretty nifty stuff, and love to see a Lynx card stuffed into such a small form factor.<br />
      <br />
      Based on some other conversations going on elsewhere on this site, I'm guessing that off-board power is/should be a must. But Windows 7? That's tough to take. ;-)<br />
      <br />
      Anyway, I'm also guessing here, but I'm assuming that a wired keyboard and wired monitor will be preferred over a wireless for those persnickety concerns over having a broadband broadcaster sitting in your rack, no?
    1. Valvefan's Avatar
      Valvefan -
      Hi Chris,<br />
      <br />
      Thanks for the awesome article on the C.A.P.S.<br />
      <br />
      I'm using a windows laptop and external HD as a sever. the system is pretty quiet but not silent.<br />
      <br />
      I've never set up a NAS before. Can Vista or Windows 7 be set up to connect directly to a NAS via wired ethernet or is a router required. I might be able to put a NAS in another room to reduce the HD noise. Can jRiver MC14 easily find my music library via the LAN connection?<br />
      <br />
      Thanks for the help<br />
      <br />
      Valvefan<br />
      <br />
      External HD>eSATA >Vista laptop>jRiver MC14>USB>Ayre QB9>Pass Labs X- preamp>Blue Circle BC 204 amp>Cabasse Farella 401 speakers<br />
      <br />
    1. The Computer Audiophile's Avatar
      The Computer Audiophile -
      Hi Scott - Yeah, Windows 7 is tough to swallow for several readers, but for others it's all they want. For this server I wanted an OS that people would purchase anywhere and would be available for a while. You are right about the persnickety concerns and using wired keyboard, mouse, and monitor. The sound compared to other computers used at the Symposium is different. Windows based machines sound different than Mac based machines and XP different from Windows 7. I have confidence that Windows 7 can be made to sound better than XP. Right now my XP, G5, Mac Pro, and MacBook Pro servers are on the sideline. I've gravitated to the C.A.P.S server. <br />
      <br />
      Hi Valvefan - Yes, any current operating system can connect directly to a NAS without a router. J River will automatically find all the music located on the NAS as long as you map a drive to it or point J River to the right folder. The thing to do is connect the NAS directly to the computer with an Ethernet cable. Most likely your computer or NAS will automatically cross-over the cable so a special cable is not required. You will have to assign a manual IP address to the NAS and your computer so the two can talk to each other. If you only have one network port on your computer you won't be able to access the internet or anything other than the NAS drive.
    1. vortecjr's Avatar
      vortecjr -
      at the risk of sounding like a copy cat....I ordered that very Intel D945GSEJT MB, backplate and ram for an unrelated venture. I'm not ready to discuss what that venture is at the moment, but that should be enough to say I like the MB. L.S. told me about the MB and the backplate a few fews weeks ago when I asked them about new MBs with PCI and SATA and minimum 2GB of ram. I don't think that the M10 case is quite ready to except that backplate because the backplate was meant for another case. BTW that case is only $35 bucks, but you loose the cd option. I could be wrong, but the AES16 card looks a bit funny in the M10 case I really like the idea of the fanless design and the external power adapter or power brick as some call them. That junk does not belong inside the music server! I have something very close to this (my personal unit in the pic) with a mini-itx MB with VIA chip, OCZ ssd, fanless case, 4 GB ram, Windows 7 and firewire to my Minerva and I love it! I use M.M. because the iTouch app rocks IMO. Someday we will have WASAPI and I will be golden. <br />
      A side note about Linux with all do respect to your attempt here to try it. My buddy Clay says, "it's a shame about the challenges of Linux." I say it's a shame you did not ask me to help! I understand that my input might spoil the project as a vender, but we should be able to look past that. I agree that Linux poses some challenges moving forward. However, Andrew has been working very hard with me to bridge the gap and make it accessable to anyone willing to try it. For sure you started out with some Linux software distributions that are to hard core for the average Joe. At the same time your building the Windows 7 machine from scratch so installing Andrew's Linux distribution should be on par! Andrew's Linux distribution is also 100% free to use without limitations and it is geared to rip music, store music, and most importantly play music with MPD. My install guide is posted here on CA if anyone is interested. As it stands you need to download the iso, burn the image to a cd and install the software. Then you set the dac from a web gui config page and your ready to go with the on board outputs or a usb dac. Yes, the AES16 card takes a few extra entries at command line and some configuration. The extra entries and config would be a copy and paste exercise. Firewire is still pretty hard, but we are working on it and it is supported.<br />
      <br />
      Jesus R<br />
    1. jbpsrca's Avatar
      jbpsrca -
      Great article chris.<br />
      <br />
      Question - what audio driver do you use with win7 and j river for the lynx card? I'm assuming the asio4all is out of the picture, as it was a legacy version that used to be in favor?<br />
      <br />
    1. The Computer Audiophile's Avatar
      The Computer Audiophile -
      Hi jbpsrca - I've had great luck with the regular ASIO driver and selecting the Lynx card via the config in J River. WASAPI has been a bit troublesome for me with bursts of distortion and some scary noises infrequently. Since you are using the AES16e card things may be a bit different.
    1. IamKirk's Avatar
      IamKirk -
      What was experience like with Arch Linux? Was voyage selected because of the nycparamedic alix project?