My windows machine uses a non English language so the guide above might be not entirely accurate on the wording you might find on your machine. Small disclaimer: The process of selecting another driver might use a different wording, I recommend searching for a guide on how to do this if you are stuck or not sure.
If you have the same issue I hope it will help my fellow friends in the firewire hell :) Either the PCI card manufacturer or microsoft botched things up picking a driver that only "seemed" to work. 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. You can check which version you have by looking at the serial number on the underside of the unit: serial numbers beginning “SU” are the USB 1.1 variant, “S2” is the USB 2.0 variant.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".
*the USB 1.1 version of the Saffire 6 USB is no longer supported. You can install the latest driver by selecting your product in the Downloads section of our website, then installing either Focusrite Control (2nd Gen Scarlett 6i6, 18i8 and 18i20, 3 rd Gen Scarlett Range, Clarett USB Range), Scarlett Mix Control (1st Gen Scarlett 6i6, 8i6, 18i6, 18i8 and 18i20) or the standalone driver installer (1st and 2nd Gen Scarlett Solo, 2i2 and 2i4, iTrack Solo, Saffire 6 USB 2.0). We want to make sure that we’re doing everything we can to give the best customer experience, so you can focus on your creativity. This release brings the 1st Generation Scarlett Range, iTrack Solo and Saffire 6 USB 2.0 up to the same driver versions as the 2nd and 3rd Generation Scarlett ranges and the Clarett USB range.ġst Generation Scarlett 6i6, 8i6, 18i6, 18i8 and 18i20 continue to be supported by Scarlett Mix Control 1.10.ĭelivering stable driver performance is one of our highest priorities. We recently released our latest Windows USB driver (version 4.63.23) which supports the following devices:
0 kommentar(er)
