Duffer5,
Looking at your post, I’m trying to get a grasp of the exact nature of the IIS incompatibility. I’m going to give you my understanding which may well be incorrect. Please tell me where I’m incorrect.
IIS is a format which is an agreed upon data protocol meant for internal (inside a device) transmission of digital data. Each data element in IIS is well defined and unchanged from one device to another (for example, LRCK-). However, since this data was never meant to be transmitted outside a single chassis there was no need to define a connector i.e. pin out/in standards so there is no IIC connector pinout standard. As a result, manufacturers who have chosen to provide for IIS outside the chassis have selected their own connector pinouts for the same data elements. This is the sole difference between the various IIS incompatibilities. To fix these pinout incompatibilities it is necessary to change either the connecting cable pinouts on one end or the other or use a device which does it and possibly other things as well. Therefor, it would be possible to connect a Gustard IIS implementation of IIS to a HiFi Rose IIS implementation by mapping the pins correctly on each end of a cable. I grant that isn’t the way it should be and your suggestion of mapping the pinouts through either physical (dip switches) or better yet, electronic pinout switching would be a much more elegant solution. So how far off am I?
TIA.
From Wikipedia: In audio equipment, I²S is sometimes used as an external link between a CD player and an external digital-to-analog converter, as opposed to a purely internal connection within one player box. This may form an alternative to the commonly used AES/EBU, Toslink or S/PDIF standards.
The I²S connection was not intended to be used via cables, and most integrated circuits will not have the correct impedance for coaxial cables. As the impedance adaptation error associated with the different line lengths can cause differences in propagation delay between the clock line and data line, this can result in synchronization problems between the SCK, WS and data signals, mainly at high sampling frequencies and bitrates. As the I²S bus doesn’t have any error detection mechanism, this can cause significant decoding errors.
There is no standard interconnecting cable for this application. Some manufacturers simply provide three BNC connectors, an 8P8C (“RJ45”) socket or a DE-9 connector. Others like Audio Alchemy (now defunct) used DIN connectors. PS Audio, Musica Pristina and Wyred4Sound use an HDMI connector.[7] Dutch manufacturer Van Medevoort has implemented Q-link in some of its equipment, which transfers I²S over 4 RCA connectors (data, MCK, LRCK, BCK).