Click Browse my computer for driver software.Right-click on Legacy1394.inf and choose Install to install theĭevice Manager, expand IEEE 1394 Bus Host Controllers.(x86)\1394 OHCI Compliant Host Controller (Legacy)\X64_driver\ This willĮxtract the drivers to: C:\Program Files (x86)\1394 OHCI Compliant Double-click to run the 1394_OHCI_LegacyDriver.msi file.Download the Microsoft Firewire 1394 Legacy Driver Installer.How do I install the Firewire 1394 Legacy Driver in Windows 10? I'm currently experimenting with the instructions found here.īy selecting the legacy driver, I can now use settings in the saffire mixcontrol that the Texas Instrument driver from my previous installations (which worked fine before Windows 10 2009, and have stopped working since the current windows 10 version). 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. It's good to keep things up-to-date.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". So, in summary, things may be better, but they are not worse. Here is the setting I use - 48kHz and 256 samples - in both tests. I loaded the stress test and there were no noticeable differences in CPU or dropouts. Here are the same tests using the 3.1 MixControl and drivers. I then installed 3.1 and restarted, then repeated the setup. I also made a stress test project that pushes things to a limit with a lot of soft synths (Reaktor, Alchemy, Kore) and reverbs running (2C Aether at 4x oversampling on lots of track). The fourth shows thew LatencyMon Driver page sorted by execution time. The third shows the LatencyMon Driver page sorted by ISR. The second shows the LatencyMon Driver page sorted by DPC. The first image shows the test run after about 1 minute. You can look at them in a new window (or download) to see the full-size images. These are full-size screen captures - I initially embedded them, but the posting software took too long to load with them in, so I just put in a link. Then I did 4 screen shots which you see below. After about 10 minutes from the restart I reset the tools and let them run for a minute while the Reaktor project was playing. I then started up DPCLAT and LatencyMon and let them run for a while after a system restart. Some typical prochannel stuff were in use on the Reaktor track. So this tests several ports and channels. Before making changes I set up a typical project that uses Reaktor running a high CPU load and automatically generating sound - and then I looped that back in to a second track and recorded that track input. I decided to upgrade from Mixcontrol 2.2 to 3.1 and I think the results are good so far.
0 Comments
Leave a Reply. |