Then you need to check for concurrent network traffic and/or optimise the settings of your NIC for low latency. In the beginning of this thread there have been quite a number of posts on how to optimise for low latency.

Ome possible cause is.latency in tour netwerk connection. Did you check the latent monitor in RedNet Control for any peaks in latency?

They look to be technically the same. I would go for a 10ft length of your original brand that did work. I'm running a 60 ft cable without issues, but than multi mode fibre optics should be able to run 1000s of feet without issues.

You did use the proper type of fibre cable, single mode vs multi mode, and suitable for the wave lenth of your transeivers?

https://www.head-fi.org/f/threads/the-diyrs-cookbook.781268/page-76#post-13531120

No, it is of no use to add a Reference clock to the CC1. On the site of Grimm Audio there are some interesting white papers, including 1 or 2 explaining the situation when Ref-clocks are and are not usefull. It all depends on the quality of the oscillator circuit and the signal locking...

There is a component for foobar called ASIO Support foo_out_asio. http://www.foobar2000.org/components/view/foo_out_asio

No problem at all. it is in the list of output devices as an ASIO device.

The clock isn't part of the audio chain. The external clock supports the D16. So it is PC-->ethernet-->D16-->AES-->DAC ________________^ ________________| ________________| ________________Clock

Nothing on the Mutec I would say. It shows it is receiving and sending an audio signal.

Does the DB25-XLR cable have a Tascam or a Yamaha wiring scheme on the DB25 connector?

The second blue light comes on when using an external clock and there is a lock on that signal, not when using the internal clock.   Just wondering if the D25 to AES cable has the proper wiring scheme? Rednet3 uses the Tascam pin-out and not the Yamaha pin-out. Maybe the cable used is wired...

  The picture shows that it has a lock on the incoming audio signal. The mutec cannot be 'set' to a certain frequency, what's coming in, is what is sent out. The settings are just fine now: "reclocking the audio signal using the internal clock", input selected is the AES-input. There is an...

Its is now set to use the USB input and apply automatic DOP to PCM conversion on the USB input. Just change the setting of the reference column to the input you have your audio signal on.

Yep, best place is after the Rednet to reclock the SPDIF, not as a master clock to the RedNet. During the time Rob was still posting here, he also found that there are better Word clocks than Mutec.

AOIP technology has been designed to be used with switches. It is only a matter of convenience that you can also do a direct connection.

MC3+usb is suposed to be quite an improvement over the MC3 A chain of 3 MC3's was bettered by a single MC3+USB. Also MC3 is no longer upgraded while MC3+USB does receive new firmware upgrades. MC3 is not compatible with MC3+USB firmware.

Me too, just plain GUI modus a no optimisation software. I did otimise some NIC settings though, to improve stability and latency to the D16

And what about this one: http://www.ebay.com/itm/Ultra-Low-noise-0-8uVrms-10Hz-100KHz-5VDC-power-supply-board-assembled-/321884601058?hash=item4af1d13ae2:g:S0QAAOSw0HVWEf10

Could you show a picture of how you made the connection to the RN3 internally? I have a few LPS-rails available (dedicated or part of a multi-rail) and am curious of what the connection actually consists of.   Cheers

I would go with 1.5m, then you satisfy both.

I believe drives with high rotation speeds are very bad for sound quality. Creates a lot of electro-magnetic disturbances, best to to SsD or slow spinning disks. Disk transfer speeds are irrelevant IMO for music playback.

No, completely different technology. AOIP is a realtime protocol. Regular streamers are a kind of file transfer protocol. Its main difference is in what the receiving end still has to do to create an audio signal.

It is a listener just like a RN3 or D16 from Focusrite. You need somerhing to play Dante into the network like the Virtual Soundcard from Audinate on a PC. This piece of kit does not use Audinate Brooklyn or Via hardware, I wonder if they are free to use/interpret the Dante protocol or whether...

Internet connection is not required for RedNet playback. The RedNet is 'just' an interface between your PC and DAC and doesn't use or require an internet connection for normal playback usage.   The only time a an internet connection is required is when doing an update of RedNet software and...