Thoughts on this Rubicon DAC with DLNA wireless push protocol

0 Members and 1 Guest are viewing this topic. Read 2012 times.

claytontstanley

Steve,

A friend of my sent me link to this DAC: http://uncrate.com/stuff/rubicon-atomic-preamp I know nothing about the company, but they mentioned using top-shelf clocks in the main description, and that caught my attention. They also mentioned using a wireless network-based push technology called DLNA, and that really caught my attention.

This is the first time I've heard of DLNA. I'm curious about your thoughts on the protocol. I glanced at a white paper: http://www.allegrosoft.com/UPnP_DLNA_White_Paper.pdf. It seems the protocol uses TCP, which (at least to me) seems like the better choice over UDP and Apple's Airplay protocol.

Much appreciated if you have time to provide any comments,
-Clayton

srb

Antelope Audio manufactures DACs, ADCs and Master Clocks for the pro recording industry segment, and in 2011 introduced the Zodiac DAC line for home use ($1895 - $4495).
 
The Rubicon Preamp/Phonostage/DAC/ADC is a statement piece for home use and includes their rubidium master clock that they have been manufacturing in their pro line.  Although I don't think the exact price has been released, it is supposed to be in the $40,000 range.  Not sure how much of that goes toward the machined art deco enclosure (compared to their normal flat aluminum panel components), but is that something you would be interested in?
 
Steve

audioengr

Steve,

A friend of my sent me link to this DAC: http://uncrate.com/stuff/rubicon-atomic-preamp I know nothing about the company, but they mentioned using top-shelf clocks in the main description, and that caught my attention. They also mentioned using a wireless network-based push technology called DLNA, and that really caught my attention.

This is the first time I've heard of DLNA. I'm curious about your thoughts on the protocol. I glanced at a white paper: http://www.allegrosoft.com/UPnP_DLNA_White_Paper.pdf. It seems the protocol uses TCP, which (at least to me) seems like the better choice over UDP and Apple's Airplay protocol.

Much appreciated if you have time to provide any comments,
-Clayton

I know of DLNA.  I submitted a proposal to Microsoft last year using DLNA to do multi-channel synchronized streams.  They were too busy doing Win8.....

DLNA is interesting and Win8 supports DLNA playback.  It is superior to most other methods.

I would like to design a Module to replace my USB module eventually that will support DLNA.  I will need software/firmware help or licensing for this work.

There are some receivers from consumer audio companies that already have this DLNA capability.

Another method is AVB.  There are reference design/development boards available from XMOS that can evidently do this:

http://www.labxtechnologies.com/avb-you/why-avb/

Not sure which one will become ubiquitous.

At this point in time, I am more concerned about getting a USB interface that is Linux compatible.

Antipodes server guys are really close to getting a linux driver working for the Off-Ramp 5.

I am also looking at designing an XMOS USB interface module.  I'll probably do the XMOS anyway.

Steve N.

claytontstanley

Thanks Steve for the informative response. AVB looks interesting, although I'm not sure how I feel about the word 'timing' being mentioned in the transfer protocol. If that means that there is no buffer on the receiving end, I'd be a bit concerned, as this means that the final timing consistency of the signal has been coupled with the transfer protocol. And this is precisely what (I would think) should be avoided. If there's still a buffer at the DAC end, and the timing stuff in the protocol helps to better guarantee a more consistent stream of data, then that's all good.

It may be the case that the transfer protocol chosen is independent of using AVB, as it seems that AVB works at a much lower level on the TCP/IP stack (the physical and link layers). So it might make sense to say things like DLNA over AVB.

Although an alternative case for just using straight TCP/IP (and a healthy dose of buffering) is the fact that the internet actually works.

audioengr

Its not totally clear to me how AVB works, but if it really attempts to create a master clock in the source, it is not interesting for high-end audio applications.

Steve N.