Use the one I use for UFX .. see signature.

https://www.amazon.de/Exsys-15-06-2257- … s=EX-16415

https://www.amazon.co.uk/Exsys-EX-16415 … S+EX-16415

Or how about this one ?

https://www.amazon.de/Exsys-EX-16450-EX … ords=EXSYS

The Delock 89121 I've ordered, has the TI TSB43AB23  chipset.
I'm waiting for it to arrive.
I'll try it and I'll share my experience.
I hope it will work.

Thank you very much!

Is it an option for you to switch to USB ?
Maybe you could sell your RME 400 for €~480 and get UC for € ~600-650 used ?

Oh no!
If it is so, do I have to switch to another motherboard???
That would be a pain...
What kind of motherboard would be trouble free for this setup?

It was mentioned in the gearsluts thread, that he brought it to work with this card:

https://www.amazon.de/Kalea-Informatiqu … g=rfm07-21

And it has the same chipset which I recommended, but where Nordcore said, it can also cause issues.

If I were you I would try the Firewire cards with TI XIO2213B chip 1st, and then draw another decision. EXSYS cards are at least known to have a solid platine board = good manufacturiing quality. Dont know about Kalea, never heard of this company.

Received my Firewire interface EXSYS EX-16415 with XIO2213 chip yesterday.

I had once, for a few seconds, something looking like input signals in DigiCheck.

Beside that, the Fireface 400 is recognized by the system, and properly displayed in the device manager.
But the tray programs do not come up, DigiCheck reports error 4 (->F3: Fireface 400 is displayed/selected).

Strange (and not expected): I can use the Fireface audio output in windows (foobar2000 ...).
Not sure if that is stable, but it runs for a while.

Used driver is "OHCI 1394 Texas instruments" = what is installed automatically.
(The other two (generic, legacy) do not perform any better. )

... to be continued

Make a clean deinstallation of RME drivers and re-install.

I confirm troubles with this setup on W10 x64:

Asus Z170-A
Intel i7 6700K
Kingston HyperX Fury Kit 16 GB
RME Fireface 800 (connected thru fw400 port)
Exsys EX-16450 (Pci-e to firewire card) with TI XIO2200A chipset

FF800 only works if bandwidth is limited to its 8 analog I/O
adding spdif or even the 2 adat expansions causes crashes (irql not less or equal and BSOD)

just ordered this card with XIO2213B
https://www.amazon.it/gp/product/B0167M … &psc=1

will try fw800 connection too eventually and will report the result

crossing fingers

Search this thread for comments on RME on that.

RME pointed me to TI home page where even TI claims that this chip shall not be used in new designs anymore. Of course they didn't tell that this chip is bugged.

I can't tell exactly what is bugged in particular with this chip. I only can describe from application / user perspective that it was impossible to run all possible combinations of sample frequency and ASIO buffer size without RME UFX firewire driver's error counter increasing by a rate of ~8 errors per second and having crackles and audio drops.

The reason why this is undetected by all the people using it .. at 44.1 and 88.1 if I remember right all ASIO buffersizes worked satisfactory. But as I said not at all sample freqzencies/buffersizes.

> That might be the case

For me personally it doesn't matter whether you believe me or not. Its an offer for others not to enter this pitfall.

> There is just *absolutely no reason* to take the NRFND state of the part as confirmation for that.

My comment to the NRFND state is not meant generally, only in regards to this chip in particular.

Well, the delock 89121 has arrived.
It has the TI XIO2200A chipset and I can confirm, that it doesn't work at all, even with MP3 playback, or youtube, with my setup(RME Fireface 400, Windows 10, I7 6700, Gigabyte Z170...etc).
Several blue screens and restarts, no sound at all, though the fireface 400 is recognised and powered up.
It's going back and I'm waiting for the EXSYS EX 16415, you suggested.
If this doesn't work also, I guess that I'll have to buy another audio interface with usb.
I'm hoping that it will work...

Ramses do you mean, that even with the exsys ex 16415 you suggested, I will still have problems due to windows 10?

With my UCX, the SIIG NN-E20012-S2 would work flawlessly under Win 7 pro 64 bit.
I didn't even have to use the UCX power supply, I would bus power it.

Now under Win 10,  I must first turn on the UCX for the computer to recognize it.
It still works, but I am not too happy especially after reading this and other threads.

I purchased a NN-FW0012-S1this morning along with the proper cable. It has a TI XIO2213BZAY chip.
I'll see if it performs any differently.

In about 10 days from now I will be able to test the Fireface 400 through the EXSYS EX 16415 in Windows 10.
If it doesn't work, I'll try switching to Windows 7 and if that doesn't work either, it will mean that Windows 10 isn't the problem.
I have the suspicion that if Windows 10 was the problem then RME would not release firewire drivers for Windows 10 and they would be warning anybody with a firewire only audio interface not to upgrade to the new OS.

Nice to hear and even with Windows 10 ..

test RME card on other PC .. if it works, fine, RME ok

install Windows 7 on other disk on your pc .. if this works, then there is an issue in the area of Windows 10 or RME driver.

If it still not works maybe your mainboard has an issue ... driver / hw ...

Its excluded that something is screwed up with the project, this problem is also with other projects ?

Can you place the Exsys into other PCIe slots?

I've downloaded and installed my motherboards(gigabyte z170x gaming 3) audio and chipset drivers, with no better results.
Is there a chance that RME's drivers for windows 10 are not working good?
Could it be a software problem(Cubase 8.5)?
I will try the windows 7 installation tomorrow.

Well it doesn't work either...
Perhaps you know about other Z170 motherboards and firewire issues, because I read that many people have the same or similar problems, with Z170 motherboards from different manufacturers.
It doesn't seem to be a software problem to me.
Maybe a driver problem, from RME, or the motherboard.
I'm already very frustrated and tired, trying to find a (maybe non existing) solution to my problem.
If I decide to buy a Usb audio interface, wich one do you suggest?
UCX, 802, or wait for a UCX+, that will get rid of the firewire port for good and have a USB3 port?
UFX+ is an ovekill for me.
I don't want to record so many inputs at the same time and I don't want to pay so much for it.
But I see that it has newer preamps, converters and overall upgrades.
On the other hand, I don't want to buy something, that is already 4-5 years old and will soon be out of date, for some reason, like the FF400 I have now.
Buying a new interface was not in my program at all...
I'm very dissapointed with new technology and that kills my creativity as an artist!
Why don't you all build something that works well for a long time?
After all we want to make music, not fight with mysterious issues all the time.

Well listen to this:
I create a new project in cubase 8.5.
I record two guitar parts.
One of them is not playing back.
I delete the project and the audio files and build a new project.
I record a new guitar track.
I push play...
I hear a white noise and after that I hear the guitar part that was not playing back in the project I deleted before!!!
Hahahahahahahaha...
That's something new!
I think I'm gonna sell everything and go back to my 4track cassete recorder!!!
Hahahahahahaha...

Ramses I did my research, before I bought my new computer.
I didn't find anything wrong and nobody told me that it won't be good for music production.
I didn't have these problems in the past with my other computers.
After all it isn't fair that companies stopped supporting firewire, for all of us who have expensive professional firewire equipment and we paid a lot of money for them.
My musical instruments don't go out of date.
My mics don't go out of date.
My preamps don't go out of date.
They all work well for many decades!
That's money well spend.
I thought that it woud be the same at least for expensive audio interfaces.
If newer computers and software don't support them anymore, at least I'm expecting from the manufacturers to warn me and not say "everything works great with windows 10 and newer computers".
We musicians, or most of us, are not rich to throw away our hard earned equipment and buy new every few years.
Technology is supposed to be our friend and not our enemy.
So I suggest to audio equipment and computer manufacturers to at least be honest to us, because they are losing customers...

> It seems like something is wrong either with windows 10, or something in the hardware department.

Yes, could be the case.
I would contact seller and write to RME support to be sure to get support.
This is a user forum, where RME is very active, but to be on the safe side I would go the official way.

Maybe your seller can pro-actively replace the unit just for the case to catch any potential HW error.

I took some time for you and re-inserted my Firewire PCIe card EX-16415 (TI XIO2213B) into my system
and connected the UFX via Firewire under Windows 10 to check whether I get issues as well.

I have a Windows 10 Upgrade installation on a separate Disk from ~2 weeks ago, which I upgraded today.

I used MusicBee to play back FLAC files using the RME ASIO Fw driver (32 Samples Buffersize) no issues.

I also tested my last three Cubase Projects with Cubase 8.5.20.
Changed in the projects to use ASIO Fw driver (before it was set to RayDAT).
Also no issues playing the projects.
2 of them contained only Audio Tracks for mastering purpose.
One contained a mix of Audio Files and VST instruments from Steinberg and 3rd party (Superior Drummer, Trillian, ..).
Also no problems to playback all those projects with lowest settings for Firewire ASIO buffersize (48).

Either your RME unit is broken or your Win installation is screwed up or you have a problem with your mainboard.

You could test your unit on another PC / Laptop.

Maybe also swap cables .. simply try to exclude "all the shit that can happen".

My system specification here: http://www.tonstudio-forum.de/blog/inde … mponenten/