tecknot
 
Hi Jim.  I'm not trying to pick a fight, but some of the points you made above are inaccurate (knowing you have much more experience on computers than I do).  First, a 64bit driver wouldn't make a difference, a 32bit driver would work just as well in Windows 10. Next, switching from a FW PCIe card to a TB one would be beneficial because it eliminates the conflict of TI vs DICE etc. controllers.  Further, the adapter I was referring to was one that you would use to connect a FW device to a TB port.  There was no suggestion that an adapter would "out-perform" in any fashion.  It's all about the connection, that's all.  Although some interfaces may not be compatible in this scenario, I am talking about a Saffire interface which is compatible as verified by Focusrite and by myself as this is the way I have my Saffire interface working with my PC (via the TB card).  So, I just want to clarify that.
 

No intention of arguing on this side... but where are you getting this information?
It's absolutely wrong...  
 
Have you ever tried loading a 32Bit driver when using 64Bit Windows?
The driver won't install/load/operate...
 
Regarding running Firewire protocol via Thunderbolt>Firewire adapter:
There are compatibility issues with certain combinations of audio interfaces and TB>Firewire adapters.
There are zero issues when using a quality PCIe TI chipset Firewire controller.
At best, you'd have performance equal to using a PCIe TI chipset Firewire controller.
At worst, you'd be trading one set of (incompatibility) variables for another... with the same result.
 
DICE-II is the Firewire chipset on certain audio interfaces.
Cheaper to integrate than chipsets used by MOTU and RME, but has significantly higher round-trip latency (requires larger "safety-buffer" to avoid glitches).
 
When it comes to a Firewire audio interface, there are varying degrees of "incompatibility" with certain Firewire controllers. 
Incompatibility with the Firewire controller could cause anything from diminished performance, flaky behavior/symptoms, to full on crashes. 
 
MOTU and RME units are typically more "forgiving" about the Firewire controller.
They'll work fine with many VIA chipset Firewire controllers.
 
M-Audio units would typically not work with non-TI chipset Firewire controllers.
 
Some audio interfaces (Apollo, Tascam, Mackie - mostly older units) are finicky about the specific TI chipset controller.  SIIG PCIe TI chipset Firewire controller works with these and every other popular Firewire audio interface.  These units typically won't work at all with non-TI chipset Firewire controllers.
 
 
Without a 64Bit driver for the audio interface, there's no way to make it work (with 64Bit version of Windows 10).
Any further discussion/details are absolutely (unfortunately for the OP) moot.
 
 

Hi Jim.  With all those considerations, it would seem that my configuration would unlikely work, but I do have a TB card and no FW card in my PC with a 64bit CPU and 64bit Windows 10 .  I am using a Focusrite Saffire interface via FW to TB.  Focusrite has only one driver from what I can tell, so I had no reason to believe that the driver was 64bit and knowing that anything 64bit is not going to work in a x86/32bit system it would seem obvious that Focusrite is providing a 32bit driver for dual compatibility.  In an effort to save the OP's interface, it would make more sense to purchase and install a TB card and to buy a new interface.  It's working here, why not give it a shot?
 
Kind regards,
 
tecknot

Not all motherboards support Thunderbolt, even with a PCIe Thunderbolt card.  I have a Z170 ASUS motherboard that will support Thunderbolt but I need a special interface adapter.

tecknot
Hi Jim.  With all those considerations, it would seem that my configuration would unlikely work, but I do have a TB card and no FW card in my PC with a 64bit CPU and 64bit Windows 10 .  I am using a Focusrite Saffire interface via FW to TB.  Focusrite has only one driver from what I can tell, so I had no reason to believe that the driver was 64bit and knowing that anything 64bit is not going to work in a x86/32bit system it would seem obvious that Focusrite is providing a 32bit driver for dual compatibility.  In an effort to save the OP's interface, it would make more sense to purchase and install a TB card and to buy a new interface.  It's working here, why not give it a shot?
 

You're using a newer audio interface that has a 64Bit driver.
The OP's audio interface (ever though it's the same brand) was created prior to 64Bit Windows Vista.
It doesn't have a 64Bit driver.
Thus, there's **zero** chance that it'll work.
Doesn't matter if you connect via PCIe TI chipset Firewire, Thunderbolt>Firewire, etc.
Without a 64Bit driver, there's no way for the hardware/OS to communicate/function with the audio interface.
 
It's unfortunate for the OP... but there's no moving forward with that particular audio interface.
For those who go all the way back to the beginning of PC DAW recording; it would be like trying to use the Digital Audio Labs CardD+.  
 
 

Thanks, everyone who responded.
Like death and taxes, upgrading is certain in this life.
 

57Gregy
I just think it's strange that the FW card was seen by Windows when I first installed it, but never again.
 

Whelp, this one is a day late and a dollar short (I have not tracked much since I got this Win10 machine a few months ago, and my Saffire got flaky as well), but I recently found that Win10 does cause an issue with the MixControl 3.7. After a couple re-installs and dropping everything possible from the loop, I noticed that Win10 will see the Saffire, but pass no audio to it... playing in the sound card properties, nothing is changed, but any test (using configuration or properties) will move the meters, but no sound out.
 
The workaround for this (thank goodness is a simple one) is to open Saffire MixControl when powering on the unit (before connecting any software) and cycling the "Settings...->Firewire Driver Latency" to anything other than what it is at boot. You can move it back, of course, but without that cycling the Saffire MixControl will not pass audio out of the unit. That setting cannot be changed once an application has been given access to the Saffire, so for me, I do not have the Saffire as the default Windows device (my Realtek is default).
 
I haven't dug into this any deeper yet, since I found something relatively simple, but hopefully this can help someone. The above has to be done after every boot on Win10 now
 
Quick Edit - Just for kicks I reloaded ASIO4ALL and rebooted my machine. Doing the above will also "intercept" ASIO4ALL being instantiated if the Saffire is to be used. It seems ASIO4ALL only comes online if a program requiring ASIO doesn't see anything else on start; and it seems those applications can also swap back and forth without issues now (Yay!).

Hello.
As I have found, some systems regardless of the TI or LSI or Nvida chipsets...Firewire has some flaws, and HDMI and other Audio onboard cards, and irq shuffling, cpu issues might come through as noise. crackling and pops, hangs and no response, to blue screens if so finding it becomes ....frustrating As I have .
 
Now if the device is compatible with a Firewire to Thunderbolt adapter, and if using win 7 or 8.1..you might get that to work as I did with my Sapphire Pro 40 on windows...(only Got TB 2 to work well on win 7 and 8)
 
Windows 10 did not like my TB 2 card, at which time was the only Worth While TB card on the market to get for TB..which was supported, and working well enough, and very much so better than Firewire cards of all kinds...Never working proper!.....until...sabotaged By MS updates forced down the pipe!.
 
So, Thunderbolt 3 with the proper adapter should work on win 10 with the drivers for that audio Device...and I believe , if I can do that.....And I did!...Then windows might be changing things...I hope they do not ruin my Asus Board that has TB  built into it running win7 and did work on 8.1 for a bit of bliss!....But, As I know of at this time, win 10 does not support that motherboard, or any add in TB 2 cards.
 
So, Juggling it...as I hope they do not push down the pipe updates for win 7 or 8.1 to ruin the workings of that...
Motu 828x TB also has issues with windows 10 and, Motu told be to try the usb port and connect it to the computer that way....Which did work...but, that is not what I bought the device for...TB works better more tracks and such, no issues.
But with MS...it is not about the user...It is about the money...more sales..more profit...Break the device, makes sales...sell more cables, adapters and hair pulling..(I got idea about making a wi fi remote hair puller)....
 
Seems so?...
 
Just my two cents..saying It does work with the adapter here on win 7 TB2...(at this time)But you have to have A MB that supports it...and TB 3...Depending on which card you get, and your MB...
Input to the card ...TB3 port is best if having one, as TB is faster and wider bussing/lanes depending on CPU ..USB c..Will cut the speed...I was reading into...So a card with ports of more than one option?...Not sure why they made usb c the need?
 
Now as long as it is a Firewire device, you will not see any boost in the Performance of speed sending or returns.
But if it is not working with firewire proper....
 
 
Again to ask...If Jim says...But we find it is not as he claims...I have to ask if TB 3 only has USB C port...Does it reduce the TB3 claimed speeds and wideness of lanes to..slow it down and reduce the functioning of..TB# claims?
 
I guess now, a detector is in between the TB chip, and the USB C chip to divert the processing of each device to the routing of for, if using one or the other kind of device used...Has to be Promoted onto the Card....If so, does this detection cause a issue?
 
And if so having the parts available ...Can Jim Test it?
 
Thanks.
 
.
 
So some old troubleshooting tips.
Read the manuals..
Put the cards in slots not shared if possible.
reduce device loads..(turn off unused devices, In Bios)(I would say before installing any ONBOARD DRIVERS OR OS)So nothing is loaded by Windows as defualt.
 
If your cards do not work..
Go into the device manager.
Unhide the Devices...
Remove all the hidden and uninstall what is set as doubling.
Turn off defender and any anti virus before installing anything.(UAC turn it down if all downloads have been scanned by virus detection apps)
 
Reinstall drivers.
 
Windows sometimes keeps default drivers hidden....And resorts to using.
 
Just something I went through helped get it going.
 
 
 
Not saying that is your issue...But you can check..
 once you find the bliss...if this is for any type of professional studio...I would turn off internet nics, wi fi, once made stable and working...so nothing screws it all up by them ghost who push things down the pipe, and change things seeming while you are not attentive to the machine.
 
 
Cheers!
 
 
 

oh when and if it does work legacy device on..win7 or 8..I believe, you can afford a Hard drive for 32bit os and apps..and drivers...and so on...if so wanting to use it that way with firewire also.
 
Firewire is a legacy device....Right?
 
is it 32 bit?
 
Just saying!