Sorry you misunderstand and by this your "shitstorm" goes into the wrong direction.
This is not a driver problem or a problem of RME or something where RME could workaround in their driver.

Its a problem of the TI chipset itself ! It does not issue reliable an Interrupt after the transmission of data. Which is required to tell the RME driver to pick up some new data that just arrived and hand it over to the application layer.

Thats far beyond the influence of RME or any other company.

TI communicated this by telling on their web site in a more general way:
"Not Recommended for New Designs (NRND)"
http://www.ti.com/product/XIO2200A?keyM … =Search-EN

Relax, you are not the only one who stumbled over this .. I had here approx 5 cards with this chipset until I heard about this.

> I'm still confused, is this ALL 2200/2213 etc.. or just 2200A?

You only need to read ... the yellow box

"Not Recommended for New Designs (NRND)

Replaced By XIO2213B– The device has SIMILAR FUNCTIONALITY but is not functionally equivalent to the compared device. The XIO2213B is feature upgrade to the XIO2200A that supports 1394b in addition to 1394a.

TI does not recommend using this part in a new design. This product continues to be in production to support existing customers."

So XIO2200A is the bogus one and has been replaced by a newer one  XIO2213B.

For some systems this seems to be important, in some cases it doesnt matter.

Your recording Interface gets the power from its own power supply so you do not need this.

Simply try it out, thats the best that you can do.

Thanks,I guess I'll find out when it gets here.

Look at the connectors / pinout of the card. This is most likely nothing for you.

As from the product description
"Compatible with 3.3V/5V, 32/64-bit PCI or PCI-X slots"

This would only be useable if your mainboard has a PCI slot which is nowadays rare to find.

And this is not the classic PCI anymore, as this will be connected by a bridge chip on the mainboard to PCIe.
PCI was a bus system with parallel data lines (32bits) and interrupt lines of its own.

PCIe is now since years the more modern serial bus allowing for higher bandwidths

https://www.naplestech.com/bus-speeds.html

What mainboard do you have ? Manufacturer, model ?

Your mainboard has PCI sockets, but I have made no experience with PCI-X cards in PCI sockets.
Shall be theoretical possible according to product description at Amazon, then you would only use the
1st 32bit PCI connector of the card, but this looks to me like a too "exotic" combination.

64bit PCI was available for some time, but from my perspective never really "hit the market"
and has been replaced by PCIe.

So better 1st try only the card which you bought.

https://www.heise.de/preisvergleich/asu … 71650.html

Formfaktor: ATX • Chipsatz: Intel Z77 • RAM: 4x DDR3 DIMM, dual PC3-19200U/DDR3-2400 (OC), max. 32GB (UDIMM) • Erweiterungsslots: 2x PCIe 3.0 x16 (1x x16, 1x x8), 1x PCIe 2.0 x16 (x4), 2x PCIe 2.0 x1, 2x PCI • Anschlüsse extern: 1x VGA, 1x DVI, 1x HDMI 1.4, 1x DisplayPort 1.1, 4x USB-A 3.0 (Z77/ASM1042), 2x USB-A 2.0, 1x Gb LAN (Realtek RTL8111F), 6x Klinke, 1x Toslink, 1x PS/2 Combo • Anschlüsse intern: 2x USB 3.0 (Z77), 8x USB 2.0, 2x SATA 6Gb/s (Z77), 4x SATA 3Gb/s (Z77), 1x seriell • Header Kühlung: 1x CPU-Lüfter 4-Pin, 3x Lüfter 4-Pin • Header Beleuchtung: N/A • Audio: 7.1 (Realtek ALC892) • RAID-Level: 0/1/5/10 (Z77) • Multi-GPU: NVIDIA 2-Way-SLI (x8/x8), AMD 3-Way-CrossFireX (x8/x8/x4), Lucidlogix Virtu MVP • Stromanschlüsse: 1x 24-Pin ATX, 1x 8-Pin EPS12V • Grafik: IGP (via CPU/APU) • Beleuchtung: N/A • Besonderheiten: All solid capacitors • Herstellergarantie: drei Jahre (Abwicklung nur über Händler)

You do not require ASIO4ALL, because you have a real ASIO driver for your RME recording interfaces.

Why did you install ASIO4ALL at all ? I think its good that you deinstalled it,
as using ASIO4ALL is IMHO
- not a good thing and
- not "best practises" to build a reliable and professional solution.

The rationale behind ASIO is, that you have an highly optimized audio driver between DAW and your audio hardware with nothing disturbing in between. And under Windows a true ASIO driver like the RME one bypasses i.e. completely the Windows Sound system which is a good thing, as in the windows sound system you have a quality degradation of audio data and increased latencies, etc ...

But ASIO4ALL is an additional layer between the application (DAW) and ASIO and WDM drivers.

ASIO4ALL only became kind of "famous" as kind of a workaround for some folks...
As a DAW can only work with one audio driver this enables you to
- to use an ASIO driver and multiple USB based micros
- different ASIO drivers or
- both in combination

But its an additional layer, which
- adds kind of complexity
- most likely adds latencies
- most likely results in audio data not arriving at the same time in the DAW (as i.e. an USB mic can't be clock synched to other audio interfaces
- results in potentially less quality as the windows sound system is being used along with WDM AFAIR

So ASIO4ALL I personally regard as a "workaround", if somebody did not do a proper planning/design, what recording interface he requires. Its not a professional solution, I would expect a quality degration, but some people are happy with it when it works, as it safes them some money, instead of having to upgrade their solution...

The far better solution is to get the recording interface which satisfies your demands in terms of the amount of required channels.
Or - what is possible with RME and what you did now and should do - to stack up to 2 or 3 of the same recording interface (see manual if and how many RME interfaces in parallel are possible) and leave out ASIO4ALL.

To put another example what could be done nowadays: RMEs new MADIface driver enables me for example to operate 2 UFX+ and an ADI-2 Pro in parallel. As all these interfaces use the same MADIface driver. So when I select in the DAW (i.e. Cubase) the RME MADIface driver, then I have direct access to all the channels of the 3 audio interfaces. They need to have then the same ASIO buffersize configured (easy to do) and of course need to be clock synchronized (I did this by using ADAT and AES channels, WC is not required).

Maybe hire an expert to built this setup?

1. One of the objectives to get a new card was that the red light goes off, where MC mentioned that this doesnt look good.
Is at least this red light problem solved ?
I dont remember that you commented on this ....

2. And then an additional idea .. why do you need 2 FF800 anyway ?
FF800 has 2 ADAT ports IN and OUT !
So you could connect IMHO both mix consoles to one FF800.
This way you do not need the additional complexity/requirement to clock sync the 2 FF800.
Then you could also test both FF800 whether both work as expected.
Theoretically all is possible, maybe one unit slightly damaged.

Or you did mistakes somewhere ...
Therefore it would not be a bad idea to call an expert.
Its easier to do troubleshooting when being directly in front of the devices.
Tthis might even enable you to keep the current HW which is not bad and save you some money in terms of HW.

Sorry, but you didnt answer my 1st question.

BTW .. This shows me again that you are loosing overview about this case.

Get an expert in. maybe he can better find the key issue when being in front of the devices.

BTW .. why do you think the Motu would solve any issues ? Maybe by using USB.
But in terms of the channels it doesnt help you.
It also has only 2 ADAT ports in and out like the FF800.
So you would require 2 new devices.
And then you have again to sync the devices...

You could also get a RME RayDAT (PCIe card).
4 x ADAT IN and OUT.
Optional WC card if you prefer WC (should not be required).
Definitively cheaper compared to 2 new Motus.

But should you require symmetric analog outputs you would require additionally a D/A converter
as the RayDAT has only digital ports.

This was solved by a later BIOS update from Asus. So the card itself is not so much to blame. Still look out for possible issues with certain mainboards.

Yes, I noticed. Just made sure to get the information over to anyone who read my Lindy (LSI/Agere) remark before.