Signal type mismatch "???" in cable report

[Ross McLee]

Hi All,

I realise this is a known 'thing', but I was curious to know what plans there are to rectify/accommodate it...

 

Example:

In the case of a microphone connected to a DSP you could have a MIC signal going into a MIC/LINE signal type input socket. The signal here is MIC but the report (and error check) will display an error/??? .

 

This scenario gets even more 'interesting' when we connect the likes of LAN, LAN (PoE), Dante, AES67, video streams etc over ETHERNET and all the devices are connected to a switch with signal type LAN. Same goes for LowZ and 100V line speaker levels. And many more!

 

Without wanting to spend a lot of time maintaining matched signal types at both ends, is there something in the pipeline to allow for some sort of multilevel signal type matching (based on signal/level protocol, or something like that!).

 

Cheers,

R

[Conrad Preen]

Hi Ross,

 

You can force the signal type to be whatever you like by entering the signal type in the Object Info Palette when a circuit is selected. Signal type is only calculated when the circuit is placed or moved so it becomes reconnected. So that takes care of it in practical terms I think.

 

Having the software "know" which signal types are compatible is a bigger step than it might at first seem. It could introduce complexity. Always worth thinking about though.

 

Thanks!

 

Conrad