09-Aug-2017, 13:34
(09-Aug-2017, 11:48)thumb5 Wrote:(09-Aug-2017, 09:57)Axel Wrote:(09-Aug-2017, 07:11)thumb5 Wrote: That seems to make sense, as the AES/EBU connection is an input only. So if it's used for the master-companion link, there is no way to for the companion to send data from its inputs back to the master.
But if you use AES/EBU, you can't use the trigger cable, so it must be two way.
I hope we're not busy agreeing with each other...but: yes, since the companion can't send data (from its inputs) to the master via its AES/EBU connector, the trigger cable has no purpose when the master-companion link is via the companion's AES/EBU. (That's my interpretation of why the configurator automatically greys out the trigger cable connectors on the companion when the link comes into its AES/EBU input, anyway.)
Agreed!
Project Eperience X Pack with Ortofon Rondo Red MC, Oppo BDP 105D, 2 x Sonos Connect, QNAP HS251+ NAS with 2 X 6TB Western Digital Red, Mac 5K 32GB running Lifetime Roon, iPad Pro 12.9" for remote control. Etalon Ethernet Isolator, Devialet 440 Pro CI, Sonus faber Olympica ll with Isoacoustics Gaia ll feet, Auralic Taurus Mkll headphone amp., Denon AH-D5000, Sennheiser HD600 and HD800 with Cardas cable, Van Den Hul The First Ultimate and Crystal interconnects, Furutech power cables, GSP Audio Spatia speaker cable.
South Coast England
