It’s a full blown switch, using a switch controller, we‘re only using 2 ports on it though.
All I care about is that you plug it all in as recommended and you push play and everything works. I really could care less as to semantics and proper definitions. If Taiko has given all this information as update , I take it as gospel but that’s just me.Can you point me to one of those that has only one in and one out?
Maybe you're not breaking new ground but it is new to me. I'd love to see an example.
Thx
So is the customized QoS rule of the router important?
FYI guys- seems it is both a media converter and a switch, no need to disagree
That’s the only thing that makes sense to me- how else is the router supposed to be powered by the BPS? Surely very very few people have their main router near enough to the extreme to be powered by the BPS, but for a second router that’s possible
Christiaan,
will there be licensing costs for adapting TACDD for DAC manufacturers or will Taiko support DAC manufacturers to get market penetration?
Thx
Matt
Hi Christian, what output voltage will the RCA outputs of the DAC card have?
You are making the assumption that the router does everything the switch does, and more, and I am not sure that is true.
I could absolutely see this happening with a new MSB input module. Many of us switched from the Renderer/Ethernet module to the Pro-USB at home, a few years ago.
"Sure it may outperform 10-20k DACs" That would suit a lot of people! would you consider releasing to non Extreme owners?
Question about TACDA. Will it have any Digital Input(s) to take advantage of its capabilities?
A two port switch is quite unusual implementation of a switch, and probably deserves a network device category of its own, but since one does not exist, I guess “switch” is the closest available category we can pick from. It's certainly much more than a media converter, and so I would not call it a media converter.
For MSB it can be „very easy“ to implement. There are several parts in play here.
- The controller, for USB the vast majority uses an XMOS controller, this controller is USB in and I2S out.
- The transport between devices, this can be:
1) using a USB cable where the XMOS controller is located inside the DAC, like Lampizator and most other DACs really, the I2S signal is then generated inside the DAC.
2) using a separate external box in which the XMOS controller is located with an USB input and AES output (Totaldac reclocker) , or an USB input and I2S output, like the MSB Pro/ISL module, though that‘s a proprietary implementation of an I2S transport, if you’re interested in the specifics read up on the MSB website.
3) placing the XMOS controller inside the server, convert USB to I2S internally, and then transport over a different link to the DAC, like Wadax for example.
What we‘re doing is replacing that XMOS controller to rid ourselves of USB entirely.
For MSB we could provide direct PRO ISL out from the server, that is the easiest way.
For other DACS we could provide direct I2S out but transporting I2S over a distance is very problematic. That is why MSB went through the trouble of designing PRO ISL in the first place. So it would be better to take it further and add a new interconnect design, which we‘re aiming to have ready in May. This would require placing a small module inside the DAC, in a Lampizator DAC it could replace the JLsounds USB module for example and it would not need a high level of expertise to mount, we could probably find local people to do that about everywhere..
…”For MSB we could provide direct PRO ISL out from the server, that is the easiest way.“…expand...
Hi Emile,For other DACS we could provide direct I2S out but transporting I2S over a distance is very problematic. That is why MSB went through the trouble of designing PRO ISL in the first place. So it would be better to take it further and add a new interconnect design, which we‘re aiming to have ready in May. This would require placing a small module inside the DAC, in a Lampizator DAC it could replace the JLsounds USB module for example and it would not need a high level of expertise to mount, we could probably find local people to do that about everywhere..
Hi Emile,
what about the clock? Via USB the signal is clocked in the DAC close to the DAC chip. Will you send a synchronous signal from the Extreme to the DAC and/or will there be some feedback from the DAC clock to the Extreme like the ZEROLINK project of Soulnote and Sforzato in Japan?
Thx
Matt
EmileI‘d go for a link not sensitive to clocking, atleast not in hardware, but that’s about everything I‘d share about it at this stage.
Emile
Is there a digital interface (I2S?) that is essentially Immune to Jitter/reclocking artifacts yet? Or in the near future?
In my experience, the fairly heroic MUTEC 'stack' that I still employ:
(2 cascaded MUTEC MC3+ USBs, each fed master clock signals from a MUTEC REF10 120SE).
part 1: nah@Steve Williams Steve, I'm no expert either. Perhaps, this is one of those instances of being better off knowing less.
I do understand the value from isolating the segmented sub-network, filtering, etc. and keeping it to an 'n' of 1.