Roadmap

Clock-free AES50 for additional Ethernet Connection

HI all,

I recently had a look more in detail how AES50 works.
It seems to be based on a standard 100 MBit/s Eth-Connection for audio- & HA- control data (basically using 2 out of 4 diff-wire-pairs of the CAT-cable)… Additionally AES50 uses the other 2 of 4 wire-pairs in the CAT for transporting the audio-clock.
So far so good.

I have now learned, that for example the S-Link protocol from your competitor (which is a similar capable port/protocol) is also based on a 100 MBit/s Ethernet-Link … but compared to AES50 it doesn’t use the other two wire-pairs in the CAT cable for audio-clock-transmission. Instead S-Link seems capable of recovering the audio-clock directly from the Ethernet-Strem itself similar like e.g. Dante/AVB can recover clock from a pure network connection.

My question is now: Obviously it seems technically possible to recover the clock directly from the network stream. Has your R&D team thought about implementing a clock-recovery directly from the Eth-Link? I could imagine that this would be feasable with e.g. an update of the FPGA…
The big advantage would be following: 2 of the 4 wire-pairs in the CAT cable from FOH to stage would be kept free and could be used for a secondary 100M ethernet-connection which could be e.g. used for Art-Net protocol or general networking between FOH and stage.

What are your opinions?