SAFFIRE MIXCONTROL LOOPBACK AUDIO LOSS DRIVERS
The Saffire Mix Control was then able to detect the saffire without any issues and I was able to record instantly.įirewire is quite old and I guess since windows already provides the drivers for firewire, the PCI card manufacturer relied on windows for matching it's chipset signature to the necessary driver. I selected the non VIA version, installed it and that fixed my problem. OHCI compliant VIA 1394 Host Controller.Windows insisted it was a generic VIA chipset so I right clicked onto it, went to settings/properties, picked the "driver" tab, selected "Update driver" then selected the "locate driver on my machine", then clicked "pick one from a list" and got basically two different options: Seems to work and looking good but then I said "wait, wasn't my firewire chipset's brand Texas Instruments and not VIA?" Looking at the device manager for the firewire card I noticed something strange: I knew from the past that the interface was working on Windows 7 and cannot remember whether it did on 10.Īfter testing all of those focusrite articles and some threads on various forums I found an issue with microsofts driver selection in the device manager for my firewire card. The device appeared to be there but only as a non working zombie. I was lucky because I had the Texas Instruments chipset and also the card was rated for 400 mbps, just like my saffire needed. The brand is not important, important was the fact that Focusrite supports only VIA and Texas Instruments chipsets on the firewire interface. My PC had no firewire inputs on the board so I bought a delock PCI firewire card. Regardless of this fact my audio interface seems to work very stable and reliable on my windows 10 machine now.
Focusrite discontinued the support for the Saffire 56 from Windows 10 build 1903 due to device incompatibilities in the firewire interface and says "it will not work on versions >= 1903".
0 kommentar(er)
