Sorry Multiple times edited .... pls reread.
Some other ideas:
1. Maybe its not required to buy a different device, as the MADIface driver recognizes already automatically,
when the device is being plugged into an USB2 port.
Then the driver automatically switches to USB2 transfer mode and reduces the amount of channels by not
transferring the 2x64 MADI channels.
I think this would be then pretty much the same situation as connecting an UFX or UFX II to the computer.
1.1 Maybe this lowers the "load" a little on the computer side.
1.2 Maybe it turns out by this test that something other is defective if even this smaller amount of channels cant be transferred.
2. Would it be possible to add a configuration option to the MADIface driver to i.e. exclude the MADI channels from this USB3 isochronous instant transfer ? Comparable to what existed i.e. in the UFX firewire driver ? USB3 full-duplex operation would still be a nice feature to keep even if not really required for less amount of channels.
3. Cool would be a feature to activate different transfer modes with USB3 isochronouse transfer mode.
To select to strip 0, 25, 50, 75, 100% of MADI channels to be able to reduce the USB3 load in increments and as most people do not require all MADI channels. Would that be possible to integrate such a features into the driver ?
4. Dont know Core Audio much, but would it maybe save CPU load and audio driver load for him, to select in the application which of the channels he wants to work with ?
5. To put an example: I question myself whether its a wise decision for me to put all of the I/O channels of the UFX+ into my Cubase projects. In cubase I can select, with which input and output channels I want to work with.
Would it reduce CPU and/or ASIO load if I would choose only the required channels ?
If yes: could something like this help him to reduce load a little bit, shall his application also allow for this ?
EDIT3:
6. Did you open driver settings dialog, which has an integrated USB diagnosis, to ensure that no data transfer errors happen due to bad USB port or cabling ? This you could eventually to proactively during the next gig to see whether in another case of bad look crc failures are to be seen.
7. Depending on the result, can you try other USB ports and eventually also cables ?
8. Which USB3 cable do you use and what is its length ? Maybe try a Lindy Premium cable of max 2m ?
BR Ramses - UFX III, 12Mic, XTC, ADI-2 Pro FS R BE, RayDAT, X10SRi-F, E5-1680v4, Win10Pro22H2, Cub13