1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.

    Dismiss Notice

Schiit Happened: The Story of the World's Most Improbable Start-Up

Discussion in 'Jason Stoddard' started by jason stoddard, Jan 23, 2014.
  1. winders
    Wow. I had no idea DNLA used HTTP. No wonder it is so bad.
     
  2. saddleup
    Even if it doesn't help destroying her music is a solid idea.
     
  3. jseymour
    I agree with Winders. The stock tubes cannot compete with my 6F8G, 6C8G, 7N7 and early 50's 6SN7.
     
    the finisher and CAPT Deadpool like this.
  4. Pietro Cozzi Tinin
    Does that mean that when ripping a song you're kind of recording the crap from the source with it?
    That would mean a good transport is always the better choice if even only for ripping.
    And how about the whole electronic song to rip chain?
     
  5. earnmyturns
    Many home streaming systems use UPnP/DLNA to connect a server (PC, NAS) to endpoints (Streamers, DACs). For example, NAD or Naim network-enabled integrated amps (like the Naim UnitiQute I used to own) connect to any DLNA server to get tracks to play, under the control of some appropriate app. UPnP/DLNA are also very common for open-source setups, such as a Linux NUC as server, and Pi endpoints with Volumio. In a DLNA setup, the endpoint draws tracks from the server by sending the server an HTTP request, and receiving the track (encoded appropriately) as an HTTP response. Of course all of this goes on top of a TCP/IP stack for error-free communication.

    Other common home media distribution protocols include Apple's AirPlay, the Chromecast protocol suite, the Squeezebox/SlimDevices protocol, and Roon's RAAT. AirPlay runs on top of UDP, Squeezebox and RAAT on TCP/IP (RAAT used to be on UDP). Chromecast supports multiple streaming protocols, which I'm not as familiar with.
     
    rdaneel, thebmc, TheTimeSink and 2 others like this.
  6. valiant66
     
  7. winders
    No, of course not. The ripped tracks are digital so they are stored on the storage medium in a digital file (zeroes and ones). The electrical crap comes along with the digital data as it is transferred to the DAC. It is not part of the file or the data.
     
    golfbravobravo likes this.
  8. earnmyturns
    Ripping gets the exact bits, unless your ripping drive/software have problems. Once you have the bits, they have to travel to your DAC represented as electrical (or optical) signals. That's a physical process that can convey unwanted analog interference as well as the original bits. The magic of pure digital communication is that it can be made arbitrarily resistant to analog noise (Claude Shannon proved this when working to Bell Labs in the 30s and 40s; technical details simplified for the purposes of this forum). However, a DAC lives in the dangerous space between digital and analog. The digital transmission into the DAC may be bit-perfect -- it can be made so with the appropriate engineering based on Shannon's fundamental discoveries -- but the physical process of reconstructing the analog waveform is susceptible to analog noise and interference. Some of that arrives through the hardware that conveyed the digital signal to the DAC.
     
  9. earnmyturns
    Bullseye!
     
    golfbravobravo and winders like this.
  10. Pietro Cozzi Tinin
    I'm just a doctor seeking the knowledge of a specialist.
    OK, so that strengthens the claim that a superior music transport (for digital files) is as important as a superior CD-spinner.
    That I can understand.
     
    RCBinTN and Ableza like this.
  11. winders
    We both know that you did not need to test me.

    Absolutely! Both a CD transport and digital files need quality hardware and firmware/software to sound their best.
     
    RCBinTN likes this.
  12. Pietro Cozzi Tinin
    Well that's exactly the experience I have in all this years of listening to music.
     
    motberg and RCBinTN like this.
  13. golfbravobravo

    Thanks for that excellent précise! Does RAAT use the DLNA stack in its entirety? I had imagined that using http for commands to e.g. the web server but the results of the command, i.e. the music was sent as blocks over TCP.

    Cheers
     
  14. golfbravobravo
    I am a happy bunny.

    I have my Freya is back [don't ask me why it was to be delivered on Wednesday, on Thursday, on Friday, and finally arrived on Saturday - thanks FEDEX] coupled up with proper tubes and I have the preferred music back in the living room and the Modi3/Magni3 back in my office.

    I see you @winders and @jseymour trying to lead me down the white smoke path again. :) Perhaps, in due course.

    I want to give a big shoutout to @jasonstoddard and his whole team at Schiit, especially in light of the recent comments wrt support from Schiit. My experience? The Freya was sent to CA, Schiit fully tested it, and returned it, all under warranty and my only cost was to ship it to California. In view of the fact that it was my idiocy that created the problem in the first place, that seems to be service of the highest order. It would have been more than reasonable for me to have to pay.

    I shall now see if I can get to the task of encasing the Rpi to match the rest and then properly securing cables so that the system looks like less of a mare's nest than it does now. Then, and only then, may pictures be forthcoming.

    Cheers
     
  15. winders
    Roon does not use DLNA. RAAT is a protocol that sits on top of TCP.

    https://kb.roonlabs.com/RAAT
     

Share This Page