The topic is even trickier, there seems to be a driver / device / chipset dependend component in it.
Tests: MusicBee Playback with RME MADIface driver 0.9700, ASIO Buffersize: 256, MMCSS: enabled
During audio playback in Firefox: loaded 100+ URLs in new tabs in batches of 10 with the aim
to create a heavy system load, in fact a mix of CPU, Memory, i/o, network-, interrupt load.
My Xeon E5-1650v3 CPU was sometimes loaded up to 80% by this.
I listened to the music and had the RME driver settings window up and running to observe USB Transport/CRC errors.
Energy Profile: Bitsum High Performance, Performance mode enganged
I tested the 7.5m cable now also with the ADI-2 Pro
- with the Sonnet Allegro Pro (old card with 4xFL1100 USB3 chipset): doesn't work at all, "stop and go"
- with the Intel C612 Chipset of my Supermicro X10SRi-F: works !!!
Same with the UFX+
- with the Sonnet Allegro Pro (old card with 4xFL1100 USB3 chipset): now it works
Why now ? Maybe because I installed the FL own driver 3.8.35514 meanwhile.
But this didn't help with the ADI-2 Pro, Win10 native and FL's own driver failed to work.
This I mean with, there is a device dependend component ...
The number of channels it can not be .. The UFX+ has 30 channels and works, the ADI-2 Pro only 2ch and doesnt work
- with the Intel C612 Chipset of my Supermicro X10SRi-F: works
All this testing has a lot of variables in it, it would be a nightmare to test all combinations.
But I think its obvious now, that in some cases you can have luck and in some cases it fails.
I think the best strategy is what KaiS suggests, to stick to standards as good as possible.
Because if something doesn't work you can at least be sure, its not a cable problematic, if you got a good cable with a length that fulfills the requirements of the USB standard.
Otherwise you would be forced to even put these tests again onto your agenda, which of course makes more work to iron out what it is. ... So playing it save should be simpler over all in terms of operation and reliability.
I personally learned from this
- thanks Microsoft for Windows 10 ... with Windows 7 I didn't have all these issues, the Sonnet card ran fabulous with its own FL driver ...
- maybe I will swap back to my initial setup and connect my UFX+ to the USB3 port of my mainboard (C612) Chipset
Then I will connect all the rest to the sonnet card.
Because ... since I moved to Win10 I have rare audio drops .. tha happen sometimes after 15 min .. sometimes after an hour, and up to now I didn't find out how to get rid of it ...
Thanks to this thread I got new ideas and maybe it solves my issues.
New strategy:
UFX+ -> connected again to USB3 port of chipset, 3m USB3 cable, Lindy
ADI-2 Pro -> connected again to USB2 port of chipset, 3m USB2 cable, Lindy
Sonnet Allegro Pro Card: am using the FL driver now instead of M$ Win10 native driver for
1: USB keyboard/mouse switcher
2: Startech external case for USB backup disk #1
3: Startech external case for USB backup disk #2
4: free
EDIT: got again a CRC error
So my theory that the C612 chipset would cure the issues goes nada nada to /dev/null....
Ok so thanks again to M$, I have no other idea... *sigh*
BR Ramses - UFX III, 12Mic, XTC, ADI-2 Pro FS R BE, RayDAT, X10SRi-F, E5-1680v4, Win10Pro22H2, Cub13