Topic: Madiface XT or HDSPe Madi FX connection
I have a problem with finding the best current use and yet future proof solution for using one of these two interfaces. Currently, I have a 2009 (upgraded) Mac Pro that still suits my needs as a main machine, as I use two slave computers to offload virtual instruments. As I want low latency, I am even looking at the possibility to use two Madi FX on the main machine, as I want to loop back several channels, use multiple hardware devices via madi (two ADI 8 QS) and connect the slave PCs with one madi port each, but I might use VEpro for routing the Slaves audio, so I might be fine with one Madi FX.
However, I want to be able to connect the Madi FX unit to any possibly upcoming new Mac Pro. Also, in the current Mac Pro, I don't have enough PCIe slots, as the Madi FX occupies two slots, even though it only need one PCIe connector. Therefor my questions:
1) How could the Madi FX be connected to the Mac Pro via an external enclosure? Is there a PCIe card that would allow me to do that? If that is possible, would it even be possible to connect two madi FX cards via one PCIe slot or does each card need a dedicated slot?
2) The Madiface XT has USB3 and external PCIe connectivity. Is one of the two preferable?
3) Could I connect the Madiface XT via PCIe external to the 2009 Mac Pro? Is there a PCIe card with an moles apdapter?
4) For any new Mac Pro models, it seems there will certainly be only Tundernolt 3/USB type C connections like the current MacBook Pro uses. What about enclosures for these connectors with Madi FX cards? Are there any experiences in using these? And what about adaptors from TB3 to Madiface XT via external PCIe?
5) For the Madiface XT, it would be great to have the unit in the rack and be able to acces it. But I need at least 4 to 5 meters of cable length to be able to do that. Is that supported and reliable via USB 3? And is it possible via external PCIe molex cables?
There are many options, but I am just unsure which ones are safe to use, reliable and low latency. Thanks!