Jump to content
  • The Computer Audiophile
    The Computer Audiophile

    Auraliti PK100 File Player Review

    front_overhead_crop7-thumb.jpgDemian Martin and Ray Burnham of Auraliti must frequently feel like Russel Ziskey teaching Basic English in the movie Stripes <a href="

    ">[Link]</a><a href="
    "><img src="http://images.computeraudiophile.com/ca/icons/ex.png" style="padding: 0pt 0pt 0pt 3pt;" alt="link"></img></a>. Almost everybody mispronounces their company name Auraliti. I admit to mangling the name a few times myself. An easy way to learn and remember the correct pronunciation is to repeat the words Audio and Reality as fast as one can over and over. Soon enough the tongue and lips get lazy and a shortened version of the two words is spoken as Auraliti. The name rhymes with the company's tagline - Welcome to the new audio reality. Auraliti's first product is the PK100. The name is not nearly as creative but mispronunciations will be very limited. The PK100 is an extremely basic yet highly refined purpose built file player. Readers seeking a multi-purpose computer capable of playing music and calculating the monthly grocery budget should look elsewhere. Computer audiophiles seeking a simple user interface, with no user intervention required or allowed, and automatic bit perfect playback of music from 16/44.1 kHz through 24/192 kHz may want to seek a new audio reality with the Auraliti PK100.

    [PRBREAK][/PRBREAK]

     

     

     

     

     

    <b>What is it, What Does it Do, What Doesn't it Do?</b>

     

     

    <b>What is it?</b>

     

    The PK100 file player is a computer underneath it's understated black metal housing. This computer is configured to function like a toaster. When I put bread in my toaster and depress the lever I can guarantee toast will pop up after a few minutes. It's that simple. Insert bread + depress lever = toast every time. The PK100 is a file player that requires no setup. In fact it cannot be setup by the end user. The PK100 arrives from Auraliti pre-configured and set in a read-only state of operation. When I connect music via USB hard drive to the PK100 the music appears in one of the many remote control applications and starts paying when I hit the play button within the app. Connect music + Select music = Play music. It's so easy even a caveman could … oh wait that's been used already. The PK100 design can be described with an analogy to the automobiles used in NASCAR races. The cars are purpose built to drive in an oval turning only to the left at a high rate of speed. For example Dale Earnhardt, Jr. drives a Chevrolet Impala on the track. This Impala would not function as an every day driver because all the modern conveniences such as power locks, windshield wipers, trunk, back seat, and normal tires, to name a few, have been removed. The PK100 is designed to play music and will not function as an every day computer because all the modern conveniences such as printing, office applications, and internet browsers have been removed or excluded from installation. It's not even possible to rip CDs with the PK100. Geeks will be happy to read the PK100 uses Linux with MPD installed to a small solid state flash drive set as read-only on an Intel D945GSEJT Johnstown Mini-ITX motherboard and a completely fanless design. Non-geeks should know that this is a great configuration that's nearly indestructible short of physical damage. The power can be removed and the user can click, the mouse, more times than people speaking the <a href="http://en.wikipedia.org/wiki/Khoisan_languages">Khoisan languages</a><a href="http://en.wikipedia.org/wiki/Khoisan_languages"><img src="http://images.computeraudiophile.com/ca/icons/ex.png" style="padding: 0pt 0pt 0pt 3pt;" alt="link"></img></a> without impacting the file player's configuration or functionality. Astute readers may have already noticed the PK100 is very similar to the Bryston BDP-1. The two players use the same concept of a Linux operating system, MPD, attaching USB drives, and iPhone control. Many of the differences between the PK100 and the BDP-1 are hardware related. The most obvious visible difference being the expensive casework housing the Bryston BDP-1. The PK100 is a very small square running 7.5 x 7.5 x 2.25 in and weighing in at 5 lbs. including power supply.

     

    <center><img src="http://images.computeraudiophile.com/graphics/2011/0228/front_overhead_crop7.jpg"></img></center>

     

     

     

    <b>What Does it Do?</b>

     

    The Auraliti PK100 file player is not a jack of all trades music server. It simply connects to a USB drive full of music, an external DAC, and an Ethernet port. The PK100 supports zero-config or what's commonly called Apple's Bonjour communication protocol that enables configuration free connecting from one device to another. Bonjour allows users of the PK100 to open a web browser and type http://auraliti-player.local into the URL box and be presented with the player's web interface. There is no need to find the player's IP Address on the local area network in order to connect to the unit. The player comes with a <a href="http://images.computeraudiophile.com/graphics/2011/0228/auraliti-player.local.png" class="thickbox" rel="auraliti-01">simplistic web interface</a> that directs users to its pre-installed control software (NeoMPC) and to other sites where users can download other applications to control the PK100. The built-in <a href="http://images.computeraudiophile.com/graphics/2011/0228/mpod-images/original/IMG_0012.PNG" class="thickbox" rel="auraliti-02">NeoMPC interface</a> is text based and allows the user to browse the folders of the attached hard drives. It's very straight forward and doesn't require a training session before the user is well versed in using the player. NeoMPC functions very well on the iPad but is not the best control app for readers using an iPhone. The NeoMPC buttons are very small via the iPhone.

     

    One of the best things about the PK100 is it's only capable of outputting a bit perfect audio signal. Without any configuration options for the user there is no way to screw this one up. Most other players on the market require anywhere from minor to major adjustments before they're capable of bit perfect playback. The PK100 supports FLAC, WAV, AIFF, and MP3 according to Auraliti, but I was able to play some lossy 256 kbps AAC downloads from the iTunes Music Store without an issue. Another very impressive feature of the PK100 is its ability to play all relevant sample rates from 16 bit / 44.1 kHz through 24 bit / 192 kHz without a hiccup. The PK100 automatically changes the sample rate based on music selected for playback assuring the user of bit perfect operation. I like to test manufacturer's claims so this is one of the first items I test when receiving a product for review. The PK100 passed with flying colors.

     

    A feature I did not use is the built-in Digital to Analog Converter (DAC) with modified analog RCA outputs. The DAC is a 24 bit AKM that's capable of sample rates from 16/44.1 through 24/192. I prefer to use an external DAC with volume control and a few other features. The built-in DAC may be very nice for users just entering the computer audio world who don't want to purchase another piece of gear or simply don't have room for another box on their desk or in their living room. This is a great way start with a minimal outlay of cash.

     

     

     

    <b>What doesn't it do?</b>

     

    Understanding what a product does and does not do is key when making a smart purchasing decision. This way there are no surprises when the new product is connected to the audio system. There is nothing worse than purchasing one component and realizing another product of equal or greater value must be purchased in order for the initial product to function as needed. Readers considering the PK100 must know that another computer is required to use this file player. The other computer is not required while playing music rather it's required for housekeeping tasks such as ripping CDs and editing metadata.

     

     

    Here are some important considerations for potential PK100 buyers.

    <ol>

    <li>No physical CD/DVD drive</li>

    <li>No ability to rip CDs</li>

    <li>No Network Attached Storage (NAS) support yet</li>

    <li>No usable onboard hard drive</li>

    <li>No physical buttons or user interface on the actual player chassis</li>

    <li>No USB or FireWire DAC support</li>

    <li>No Squeezebox / SqueezeCenter</li>

    <li>No iTunes music sharing capability</li>

    <li>No UPnP support</li>

    </ol>

     

     

    Some readers will look at this list and consider the PK100 worthless. In fact that's a good thing because these readers are likely not the ideal user for the PK100. Readers seeking all the above features in a single box can immediately rule out this Auraliti unit and move on in their search for a music player or server. Remember the PK100 was created to play music and do it very well. There are many reasons why the PK100 doesn't offer the above features. There is no need for a physical CD/DVD drive since the player does not rip discs. The design decision to not include the CD ripping capability in the PK100 was very smart. Currently there are numerous applications that rip CDs very well and allow the user to edit the metadata. There's no reason for Auraliti to either reinvent the wheel with its own ripping app or to enable one of the open source ripping applications. In fact enabling the PK100 to rip CDs would require enabling many other features that have nothing to do with playing music. For example the PK100 would have to allow access to the attached hard drives over the network, for metadata editing purposes, thus becoming a network file sharing server. There is really no reason to enable features 100% of the time when they are used 1% of the time. The PK100 file player has a very purist design. Support for Network Attached Storage that would allow the PK100 to pull files from a NAS drive would be nice but would also involve more complexity from a design and usability perspective. I believe Auraliti is working on a NAS of its own that will function seamlessly with the PK100. No official release date has been provided as of this writing. The only drive the PK100 ships with is the onboard solid state flash drive. This drive is not usable for music storage as its very small and marked as read only. Auraliti was wise not to include a usable hard drive in this unit. Companies like Seagate, Hitachi, Toshiba, and Samsung are far better at selling and servicing hard drives than Auraliti. Plus, user size requirements are all over the board and advances in storage technology happen very quickly. If Auraliti did ship the PK100 with an internal hard drive I'm wiling to bet many users would replace it with a drive of their choice anyway. One feature the PK100 doesn't offer and the Bryston BDP-1 does is a front panel display with user interface. This type of display can have negative consequences on sound quality. According to Auraliti excluding such a display, <i>"eliminates background processes which induce jitter inducing interrupts and noise from the GPU supplying a graphic interface."</i> Readers who like the ability to see exactly what's happening or the ability to physically press play on an actual audio component may find the PK100's lack of onboard display frustrating. Perhaps the biggest potential show-stopper with the PK100 is its current lack of support for USB and FireWire DACs. Audiophiles with wonderful USB or FireWire DACs will have to think long and hard about replacing their DAC to accommodate the PK100's S/PDIF output. Auraliti did have a <a href="http://images.computeraudiophile.com/graphics/2011/0107/large/IMG_0698.jpg" class="thickbox" rel="Auraliti-00">USB capable unit on display</a> at The Show in Las Vegas this year but there is not scheduled release date yet. Lack of UPnP support, Squeezebox / SqueezeCenter support, and iTunes music sharing support are the three remaining items users should consider before purchasing the PK100. Some servers offer these options as they allow users to access or send music to other devices or rooms in one's house. It's been my experience that these server type features are best run from a NAS device not a high quality file player like the PK100. Again, Auraliti was wise to exclude these and many other features from the PK100. This file player is certainly not for everyone. Understanding what it doesn't offer should be something every potential purchaser considers.

     

     

     

    <b>The Auraliti PK100 In My Listening Room</b>

     

    In my listening room I used the PK100 in a few different systems. I spent a considerable amount of time with the unit connected to a new Peachtree iNova integrated amp with Peachtree D5 loudspeakers. I also used the PK100 connected to my Benchmark DAC1 PRE sitting on my desk with a pair of Sennheiser HD600 headphones. The PK100 produced absolutely no audible noise when placed at arms length on my desk. Originally this was not a configuration I was going to try but for testing purposes I gave it a shot and fell in love with this little system. The PK100 would be a great addition to many office audio systems no matter what components are already in place. Using one's office computer for music playback just doesn't cut it anymore once you've tried the PK100 approach. I highly recommend CA readers give this a shot.

     

    To give readers a better idea of how to use the PK100 I compiled a step by step list of the process I used in my system.

     

    <ol>

    <li>Connected the PK100 to my home network via a single ethernet cable.</li>

    <li>Connected the PK100 to the Peachtree iNova via coaxial S/PDIF cable with a BNC connection on the PK100 end and a BNC with RCA adapter on the iNova end.</li>

    <li>On my OS X 10.6.6 MacBook Pro I formatted my external 750GB Oyen Digital USB hard drive as FAT32. This enabled me to read and write to this drive from my Mac or PC.</li>

    <li>On my Windows 7 PC (MacBook Pro running Boot Camp) I ripped music using dBpoweramp to the 750GB USB drive in FLAC format.</li>

    <li>I also copied AIFF files and other FLAC files from my NAS drive to the 750Gb USB drive.</li>

    <li>I ejected the 750GB USB drive from the MacBook Pro and connected the USB drive to the Auraliti PK100.</li>

    <li>On my MacBook Pro running OS X 10.6.6 I opened my web browser (Google Chrome) and typed http://auraliti-player.local into the URL box. This brings up the PK100 home page.</li>

    <li>Once a USB drive is connected the PK100 can take a few minutes to search the hard drive and create its local database of music contained on the drive. I used the NeoMPC user interface to check on the status of the database building process. This user interface is accessed by clicking a link on the PK100 home page.</li>

    <li>Once the database was fully populated I mainly used the free <a href="http://itunes.apple.com/us/app/mpod/id285063020?mt=8">MPoD</a><a href="http://itunes.apple.com/us/app/mpod/id285063020?mt=8"><img src="http://images.computeraudiophile.com/ca/icons/ex.png" style="padding: 0pt 0pt 0pt 3pt;" alt="link"></img></a> iPhone application to browse and play music straight from the connected 750GB USB drive. I also use NeoMPC from my iPad as there is no iPad version of MPod available at this time. An iPad version currently named MPaD is in development. I briefly used the Mac OS X application Theramin to control the PK100 but the experience was less than enjoyable.</li>

    </ol>

     

     

    <center>Example Configuration Using External dCS Debussy DAC</center>

    <center><img src="http://images.computeraudiophile.com/graphics/2011/0228/Auraliti-01.png"></img></center>

     

     

     

     

     

    <img src="http://images.computeraudiophile.com/graphics/2011/0228/Auraliti-02.png" style="padding: 5pt 10pt 5pt 5pt;" align="left">The process to add music to the 750GB hard drive was very straight forward. I disconnected the drive form the PK100, connected it to my MacBook Pro, ripped a CD to the drive in any folder structure I wanted, ejected the drive from the MacBook Pro, and reconnected the drive to the PK100. While this process is easy I did get tired of moving the drive back and forth to add more music. I purchase three to five CDs per week which required me to go through the hard drive routine fairly often. Whether this is a show-stopper or not can only be answered by each individual. I would much prefer ripping my CDs to a NAS drive and refreshing the library on the PK100 with the click of a mouse or tap of the iPhone screen.

     

     

     

     

    <a href="http://images.computeraudiophile.com/graphics/2011/0228/neompc-with-folder.jpg.png" class="thickbox" rel="Auraliti-03"><img src="http://images.computeraudiophile.com/graphics/2011/0228/neompc-with-folder.jpg-thumb.png" style="padding: 5pt 10pt 5pt 5pt;" align="left"></a>The music I placed on the 750Gb hard drive for use with the PK100 was FLAC and AIFF originally ripped via dBpoweramp. Both types of files had all metadata including cover art embedded into each individual file. Using NeoMPC and MPod I was able to view all the metadata and cover art when paling FLAC files. FLAC is by far the best format for embedded metadata on all platforms except iTunes. MPod also handled AIFF embedded metadata without issue. NeoMPC on the other hand required a picture of the cover art be placed in each album folder and named folder.jpg in order to view AIFF cover art. Thus NeoMPC doesn't support embedded cover art with AIFF files. Ripping with dBpoweramp allows users to embed with cover art and simultaneously place the cover art into a folder.jpg file. This is a great way to cover more bases when ripping a collection. It's impossible to know what platform one will use in the future so this belt and suspenders approach is highly recommended.

     

     

     

     

    <center>

    <a href="http://images.computeraudiophile.com/graphics/2011/0228/mpod-images/original/IMG_0969.PNG" class="thickbox" rel="Auraliti-MPoD"><img src="http://images.computeraudiophile.com/graphics/2011/0228/mpod-images/thumb/IMG_0969.png"></a>   <a href="http://images.computeraudiophile.com/graphics/2011/0228/mpod-images/original/IMG_0970.PNG" class="thickbox" rel="Auraliti-MPoD"><img src="http://images.computeraudiophile.com/graphics/2011/0228/mpod-images/thumb/IMG_0970.png"></a>   <a href="http://images.computeraudiophile.com/graphics/2011/0228/mpod-images/original/IMG_0978.PNG" class="thickbox" rel="Auraliti-MPoD"><img src="http://images.computeraudiophile.com/graphics/2011/0228/mpod-images/thumb/IMG_0978.png"></a>   <a href="http://images.computeraudiophile.com/graphics/2011/0228/mpod-images/original/IMG_0968.PNG" class="thickbox" rel="Auraliti-MPoD"><img src="http://images.computeraudiophile.com/graphics/2011/0228/mpod-images/thumb/IMG_0968.png"></a>   <a href="http://images.computeraudiophile.com/graphics/2011/0228/mpod-images/original/IMG_0971.PNG" class="thickbox" rel="Auraliti-MPoD"><img src="http://images.computeraudiophile.com/graphics/2011/0228/mpod-images/thumb/IMG_0971.png"></a>   <a href="http://images.computeraudiophile.com/graphics/2011/0228/mpod-images/original/IMG_0977.PNG" class="thickbox" rel="Auraliti-MPoD"><img src="http://images.computeraudiophile.com/graphics/2011/0228/mpod-images/thumb/IMG_0977.png"></a>

    </center>

     

     

     

     

    Sonically the PK100 out-punts its coverage or out-performs it's $799 price point by a long shot. The internal Juli@ audio card in combination with the single purpose finely tuned Linux operating system is every bit as good or better than a PC or Mac with Lynx AES16 audio card. It's impossible to compare apples to apples here because the Lynx AES16 cannot be placed into the PK100 chassis. It's very likely the Lynx would benefit from a simplified Linux OS, but I have a hard time believing it would sound better than the stock PK100. No doubt a fair amount of this great sound quality stems from PK100 designer Demian Martin's incredible knowledge and skill. Many Computer Audiophile readers already use components designed by Demian from Spectral Audio, NuForce, and a host of others for which Demian does't take credit publicly. He frequently shares much of his computer audio knowledge here on the CA forums. I'm always surprised when Demian spends his own time to research what may seem like an inconsequential issue raised by a CA reader and share his findings in a detailed response.

     

    Simply because I can I briefly compared the PK100 to my Pyramix machine with a several thousand dollar Mykerinos audio card running into a Berkeley Audio Design Alpha DAC. This is a totally ridiculous comparison on many levels including price and the user unfriendly professional software interface of Pyramix software. To my ears in my system the Pyramix / Mykerinos combination was clearly more resolving. In addition readers should know a very nice feature of the Mykerinios card, and a Lynx card, is the ability to externally clock the card from a DAC with word clock output such as the Weiss DAC202. External clocking is not a feature of the PK100 but I'm pretty positive nearly all PK100 users are thankful for this exclusion as an externally clocked card is quite cumbersome to operate.

     

     

     

    <b>Conclusion</b>

     

    The Auraliti PK100 is a finely tuned well designed computer file player. It's simple user interface that requires no tweaking is a major benefit to many computer audiophiles. The fact that users can't adjust any settings and obtain bit perfect playback automatically cannot be emphasized enough. this is a big deal. In my experience the most common cause of dissatisfaction with computer based sound quality is lack of bit perfect output. The PK100 completely solves this issue. Potential PK100 purchasers should ensure they've considered all the features this player offers and does not offer. This player is not a one size fits all music server and will not help complete one's taxes before April 18, 2011. The PK100 is capable of changing the way one listenings to music with it's highly refined minimalist feature set and simple operation. My tagline for this CA recommended player is, The Auraliti PK100 connect, select, and play.

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

    <b>Product Information</b>

     

    <ul>

    <li>Price - $799</li>

    <li>Product Page - <a href="http://auraliti.com/PK100_Store.html">Link</a><a href="http://auraliti.com/PK100_Store.html"><img src="http://images.computeraudiophile.com/ca/icons/ex.png" style="padding: 0pt 0pt 0pt 3pt;" alt="link"></img></a></li>

    <li>Quick Installation Guide - <a href="http://files.computeraudiophile.com/2011/0228/PK100quickinstallguide.pdf">(PDF)</a></li>

    <li>Auraliti Simplified - <a href="http://files.computeraudiophile.com/2011/0228/Auraliti_Simplified.pdf">(PDF)</a></li>

    </ul>

     

     

    <ul>

    <li>Plays FLAC, WAV, AIFF, and MP3 music files</li>

    <li>44.1, 48, 88.2, 96, 176.4, and 192 KHz</li>

    <li>Automatically selects for correct sample rate</li>

    <li>Remote control from any web browser</li>

    <li>Bit perfect, low jitter, and no resampling</li>

    <li>SPDIF 75 ohm BNC digital</li>

    <li>Internal Digital to Analog converter allows option of RCA output or*balanced*output*over TRS connectors</li>

    </ul>

    <b>Analog output</b>: RCA stereo pair

    <b>Optional Analog output</b>: Balanced differential TRS connections

    <b>Dimensions</b>: 7.5 x 7.5 x 2.25 in; 190 x 190 x 55 mm

    <b>Weight</b>: 5 lbs, 2.27 Kg with power supply

     

     

     

     

     

     

     




    User Feedback

    Recommended Comments



    <br />

    <br />

    "Perhaps an easier solution would be to add FW<br />

    <br />

    then several other FW DACs could easily provide the master clock. Of course for owners with one of the Metro Halo DACs or something similar, syncing to an external clock via S/DIF is no problem."<br />

    <br />

    I agree, this would be great.

    Share this comment


    Link to comment
    Share on other sites

    <br />

    <br />

    "In extensive testing I (and a few others) have been unable to hear a difference between flac and wav on the Auraliti players."<br />

    <br />

    "For what its worth the system load on a 176.4 FLAC is around 30% and a similar WAV is around 3.3% in the Atom based player."<br />

    <br />

    that's very interesting, especially as compared to OS-X based machines which sound different based on miniscule differences in processing (from the music player software).<br />

    <br />

    clay

    Share this comment


    Link to comment
    Share on other sites

    fully, I'd like to ask: have you ever heard a difference between lossless formats, or just not on the Auralitis? If yes, on what platforms did it seem worse? (sorry, promised not to hijack) Thx

    Share this comment


    Link to comment
    Share on other sites

    The BDP-1 has the capability to allow music files to be sent to the usb drive over the network, leaving the drive connected to the player. This mitigates the need to rescan the entire drive upon reconnection and the player needs only to discover the newly added files. USB Drive must be formatted as FAT32. Does the PK100 have such a capability?

    Share this comment


    Link to comment
    Share on other sites

    "Perhaps an easier solution would be to add FW"<br />

    <br />

    I'm not sure adding support for FireWire DACs/Interfaces would be particularly "easy" as you'd also have to create Linux drivers for such devices. Note: Weiss have shown interest in creating drivers for Linux - I believe this may be spurred on by Jesus / Sonore. <br />

    <br />

    That's the beauty of "driverless" USB audio, any DAC using this method *should* work with Linux including the new Class 2.0 USB Audio which supports 24/192. On the other hand DACs such as Wyred4Sound and M2Tech, like the FireWire devices, won't work (via direct USB) unless their manufacturers are prepared to either develop Linux drivers or supply details to Linux coders. <br />

    <br />

    Eloise

    Share this comment


    Link to comment
    Share on other sites

    <br />

    <br />

    "That's the beauty of "driverless" USB audio"<br />

    <br />

    as far as I can see, which may not be far, driverless USB for which software does not have to be written only applies to "adaptive" USB.<br />

    <br />

    For Async USB one needs to use Gordon's code (or similar). I don't see that as much different (read, much "easier") than the issue with needing Firewire drivers, other than that Gordon is probably more reliable/timely than others as regards to the code.<br />

    <br />

    Do you?<br />

    <br />

    clay<br />

    <br />

    <br />

    Share this comment


    Link to comment
    Share on other sites

    <cite>that's very interesting, especially as compared to OS-X based machines which sound different based on miniscule differences in processing (from the music player software).</cite><br />

    <br />

    I don't hear any differences with CPU load either on my Windows and Linux machines.<br />

    <br />

    It is pretty easy to test by watching for example 1080p video on YouTube while listening music and comparing play/pause if it makes any audible difference.<br />

    Share this comment


    Link to comment
    Share on other sites

    Clay...<br />

    <br />

    It depends what you mean by "writing software". <br />

    <br />

    Apart from Gordon; dCS, Audiolab (John Westlake) and Musical Fidelity have all created interfaces USB to DAC which are "driverless" and Asynchronous*. All work on OS X, Windows and Linux without third party drivers - Windows need a driver for Class 2.0 USB Audio for 24/192 but this isn't (afaik) a "custom" driver it just adds USB 2.0 audio support which Microsoft haven't yes added. Yes the DAC needs software / firmware written but on the computer nothing extra needs installing. <br />

    <br />

    On the other hand; FireWire doesnt (IIRC) have an equivilent and each async FireWire implementation requires a custom driver to be installed on the computer. <br />

    <br />

    That was my definition. <br />

    <br />

    Eloise<br />

    <br />

    Note *: I think other manufacturers such as ARC, Antelope and probably others also have an implementation which supports async via USB "driverlessly"

    Share this comment


    Link to comment
    Share on other sites

    <cite>Listening to their rational helped me to understand the Auraliti better. They consider it a GOOD thing to not have any video circuitry, keyboard/mouse circuitry or WiFi working inside their box. From what I can tell the ethernet connection just had to be there to allow remote control with computer/iPhone/iPad, and they prevent ethernet streaming of the music files, and only allow the music to come in via the USB ports, which are not responsible for anything else, at least in the PK100 and BDP-1.</cite><br />

    <br />

    Hi Bones,<br />

    <br />

    I don't disagree with the less is more approach, of course, but there's no qualitative difference between driving an ethernet interface, a USB interface or a firewire interface. It's still something the OS has to handle. Bryston pick out the positives of using USB drives by saying there's no need to maintain a home network, but I haven't read any sound quality claims they make for USB over anything else (which would be far-fetched).<br />

    <br />

    The important thing with the Auraliti is that it's a properly designed piece - you get the impression every component (OS included, which is rare) is thoroughly understood.<br />

    <br />

    ZZ

    Share this comment


    Link to comment
    Share on other sites

    <br />

    "All work on OS X, Windows and Linux without third party drivers"<br />

    <br />

    you seem to be saying that Gordon's streamlength Async USB DACs (such as my Proton) will work fine with a bog standard USB implementation on any Linux box?<br />

    <br />

    If so, yes, that would seem to be an improvement over Firewire implementations, all of which will need drivers written for Linux.<br />

    <br />

    Share this comment


    Link to comment
    Share on other sites

    "You seem to be saying that Gordon's streamlength Async USB DACs (such as my Proton) will work fine with a bog standard USB implementation on any Linux box?"<br />

    <br />

    I believe this is correct. Most (its difficult to say 100%) recent distributions support Class 1 USB audio as used by Streamlength code (and MF, dCS, Audiolab, et al). The most recent ones (e.g. Voyage MPD) also support Class 2.0 USB audio devices such as the (updated) Ayre QB9. <br />

    <br />

    Having said that, from reading I believe the Auraliti has USB Audio removed. <br />

    <br />

    The Auraliti is great; but in terms of SQ I don't see any reason why a Asus / Zotac nettop (or C.A.P.S. machine) running Voyage MPD Linux (http://www.computeraudiophile.com/content/New-Linux-OS-aimed-computer-audiophiles-Voyage-MPD) couldn't be as good if running USB for someone willing to spend time configuring it. (P.S. that's not to say there isn't value in the Auraliti turn-key approach)<br />

    <br />

    Eloise<br />

    <br />

    P.S. Also worth checking out Vortexbox as used by Sonore. Not sure if that supports Class 2.0 USB audio (yet).

    Share this comment


    Link to comment
    Share on other sites

    <cite>The most recent ones (e.g. Voyage MPD) also support Class 2.0 USB audio devices such as the (updated) Ayre QB9.</cite><br />

    <br />

    Ahem, do you call Debian Squeeze -based "recent"? For me it's completely antiquated, as any Debian when it manages to reach release state, even Debian unstable is lagging a lot. AFAIK, that's one of the reasons Ubuntu was born and it is much more recent, but it's quite far from Debian.<br />

    <br />

    But anyway, Linux 2.6.37 kernel and ALSA 1.0.24 combo works fine for those devices I've tested with. Those two are the components that matter for this case.<br />

    Share this comment


    Link to comment
    Share on other sites

    The PK100 can play music from volumes connected to USB ports or from a Server connected over Ethernet. Both work very well. To improve things further we will soon be introducing a Server that is very easy for a customer to add and keep running. In addition to this we will have drive enclosure with a SATA filter that avoids adding noise to the USB bus for those customers that prefer this method of storage.<br />

    <br />

    Share this comment


    Link to comment
    Share on other sites

    That's good to hear. The ability to pull music from a server, NAS, or attached USB drive is a big deal from my perspective.

    Share this comment


    Link to comment
    Share on other sites

    The Auraliti PK 100 has USB audio in it supporting USB audio class 1. We have it disabled in MPD when the PCI interface is on because we found some odd stability problems having them both enabled. There is a routine for switching them. We also found that using the on board USB interface was less than ideal since its shared with every other USB device attached (including a USB storage device). This lead to the PKUSB version with a special USB interface card and updated USB drivers supporting USB audio class 2.<br />

    <br />

    Others have already explained the differences in the non-standard vs. standard USB interfaces. <br />

    <br />

    One of the biggest challenges in Linux is getting current enough stuff that is also stable. These systems are composed of thousands of small programs that need to work together. Changing any one can have effects that are difficult to find but cause problems elsewhere like the instability we noticed.

    Share this comment


    Link to comment
    Share on other sites

    First, I want to say congrats to Demian and Ray on the review! It also was a pleasure chatting with you guys at RMAF last year.<br />

    <br />

    I also would like to chime in on some of the discussion above to offer some additional information. Testing if cpu matters is tricky and I have done some of this on my path to get to the Sonore product line. The results seemed to depend on the load from the OS, the OS type and the horse power behind the cpu just to name a few variables. Testing this kind of stuff on a powerful computer can be hit or miss. What I did is build less powerful computers with the same setup to see where things went south. I remember one case where the mouse tracking could be heard in the music. I remember another case where the coverflow option in one of the players caused all kinds of issues with playback. However, this is all relative to what you are doing.<br />

    <br />

    Class 1.0 USB and Class 2.0 USB support on Linux/MPD servers is a function of the distribution version. Vortexbox and the Sonore spin off both support Class 2.0 USB up to 24/192 playback as of last year. The limitation is driverless capability for the device used. As an example the M2Tech Hi-Face is not supported, because it utilizes a custom driver and M2Tech does not want to open there code for integration. At the end of the day though there are more products supported by Linux distributions than not supported. <br />

    <br />

    Firewire playback on Linux/MPD is a different animal and I would not count on it anytime soon to be easy to do and or stable for the general public. This is not to say that a manufacturer could not implement a solution for a particular product. It's being done right now as a matter of fact.<br />

    <br />

    Jesus R<br />

    www.sonore.us

    Share this comment


    Link to comment
    Share on other sites

    We chose not to enable CIFS (SAMBA) access to the usb devices on the player. It is another chunk of software with configuration and security issues to struggle with plus issues around explaining it to users. We are enabling it in the server we are testing now. <br />

    <br />

    We use NFS to connect between the server and the player. It's a well tested, low overhead, reliable connection that just works. All of the Auraliti Players support it. The BDP-1 can also support it.<br />

    <br />

    Bryston inadvertently confused streaming as in internet radio with "streaming" as in playing content from a NAS. They work differently and would use different protocols for moving data. We are working with them on clarifying the issues and how they impact the different products.<br />

    <br />

    Bryston made a major effort to make the BDP-1 work as much like a virtual CD player as possible with as little need for a network as they could. We chose a different path embracing the network as essential to the device and built on that concept. The underlying framework is the same.<br />

    <br />

    Building a system around Voyage MPD will yield a good result and many many hours of fun learning Linux and computer hardware before getting much musical enjoyment.

    Share this comment


    Link to comment
    Share on other sites

    <em>Ahem, do you call Debian Squeeze -based "recent"?</em><br />

    Well I'm not up on "recent" distributions beyond the fact that Voyage MPD is a recent introduction and works with recently introduced Class 2.0 USB Audio devices :-)<br />

    <br />

    Eloise

    Share this comment


    Link to comment
    Share on other sites

    Linux Firewire support for audio currently requires two layers of software to work. Unlike the USB and the PCI audio devices which we can hook directly to the player through the underlying audio hardware interface Firewire currently requires and additional layer (Jack) to connect everything. There are some drivers available and I believe some Weiss devices are supported. Thats for later if there is enough real demand.<br />

    <br />

    This comes from discussion about locking to a clock from the DAC. With Async USB and Firewire interfaces this is a non issue. For other DAC interfaces there is a desire for the DAC to provide the clock and to lock the player to the clock from the DAC. The big problem is that the DAC doesn't know the sample rate the player is requesting. I would describe the shift from what we do now to this type of operation like switching from a modern automatic transmission to an early non-syncro crash gearbox in a pre WW2 car. Driving can be a fun task but the mistakes can leave a lot of metal on the ground (or fried tweeters) and a traffic jam (mixed sample rate playlist) is very exhausting. <br />

    <br />

    We are focusing on providing very low jitter S/PDIF and AES-EBU streams so the DAC's receiver circuitry doesn't need to work very hard.

    Share this comment


    Link to comment
    Share on other sites

    I have heard the systems that the flac vs. wave issues shows on. I have not had one at my place in years, they just didn't do anything for me. I don't think resolution or ability to hear small things are an issue in my system since many other things are quite evident (power supplies, cables, ambient temperature, LED displays, etc.). <br />

    <br />

    My instinct on this issue is that the interface card, how its clocked and internal noise is managed plus the DAC's ability to work with the signals its sent and reject noise all affect the impact of the OS and its activity on the sound. Too many variables to contemplate to be able to point a finger at a single element and say that is why/why not the system shows flac vs. wave.<br />

    <br />

    FWIW my system uses a variety of DAC's including a first gen Number Cruncher and a prototype Anagram DAC, a Nuforce P9 preamp, a hot rodded Spectral DMA50 and Crosby modified Quads for now.<br />

    Share this comment


    Link to comment
    Share on other sites

    Keeping the OS current is a chore with little return I think. When significant improvements are made that directly affect what you are asking of the system then its worth making a change. We built the kernel from sources and use the latest ALSA since those affect the performance. However we won't update to newer versions of the kernel or ALSA until they have improvements that specifically address the interfaces we use, otherwise its not useful. <br />

    <br />

    We don't include interfaces in ALSA that aren't ones we specifically use, same for MPD. We focus on support for uncompressed and lossless codecs that are free and open source. I can't say that adding support for other interfaces and codecs would degrade anything but they would be unnecessary for our efforts. "If in ain't broke, don't fix it" is an important philosophy dealing with something moving as fast as Linux.

    Share this comment


    Link to comment
    Share on other sites

    Since the first day I understood the factors that make up great digital audio I've been struck at the absurdity of the notion of tying up a full functioning PC/Mac to crunch this data to the DAC. A device such as this represents the future of audio to me. Many of us already have our audio files on a NAS or external hard drive....just looking for something to play them that doesn't entail booting up a full and sluggish OS capable of doing a thousand other things besides play music.

    Share this comment


    Link to comment
    Share on other sites

    Hello, <br />

    <br />

    I am new to this forum but I was just wondering, <br />

    <br />

    1) does anyone use balanced interconnects?<br />

    If so how many of you use XLR? how may use TRS?<br />

    <br />

    The reason I ask is that the Auraliti offers TRS (balanced) outputs. And I do not know any audiophiles who use this type of connection. They are mainly used more in the Pro Audio environment. I would like to see XLR Balanced outputs as an option not TRS.<br />

    <br />

    2) Also guys, please keep in mind that this product (and review position) is for a simple plug and play, all-in-one solution. So that being said, I was wondering why Chris did not listen to the Auraliti analog outputs?<br />

    <br />

    <br />

    ....kuroda

    Share this comment


    Link to comment
    Share on other sites

    Some of us have a mixture of pro and consumer components, and as such<br />

    requires proper interface.<br />

    Example: I have powered pro speakers with xlr inputs and I have an Arcam consumer preamp that have both RCA and XLR outputs so I use XLR to interconnect both, not aware of any sonic diff. though.<br />

    Winston

    Share this comment


    Link to comment
    Share on other sites




    Guest
    This is now closed for further comments




×
×
  • Create New...