After the upgrade the machine and audio worked perfectly for quite some time but the other day I discovered that a Windows 10 upgrade (specifically Windows 10 Version 1511) was hung during downloading and had never installed. Windows 10 was installed as a free upgrade from Windows 7. Good heavens, thank you for this post! I have a Windows 10 圆4 machine, two Focusrite Saffire 40's and a IEEE 1394 controller with a VIA chipset. Package works also at Windows 10 and at one case, I've find it useful. To obtain it for new systems, you'll need to download additional package from Microsoft. Legacy OHCI 1394 driver isn't present at system from Windows 8 onward. Can't guarantee that this would help, though it may be worth trying a VIA chipset one. I did read somewhere (though I can't find the link now) that some Asus motherboards don't get on with the TI chipset, but it didn't explain why. MixControl was also really flaky, and kept losing connection to the Pro40 or wasn't able to detect it.Īs soon as I put a VIA chipset Firewire card in, everything worked perfectly very low latency (32 samples), no drop outs and no disconnects. Couldn't get audio going with anything at all. Tried all different audio drivers (ASIO, WDM, DirectSound, etc.) but nothing. It would be detected correctly, drivers installed, I could see it in device manager and the lights were lit up on the Pro40, but as soon as I tried to play any audio, Reaper just had 'buffering' in the transport section and nothing happened. I originally had a TI chipset Firewire card with my Rampage V Extreme and just couldn't get the Pro40 going at all with it. Not sure if this will be any help at all as the setup is quite different, but the combination of Asus motherboard, TI Firewire and Pro40 was what I was struggling with. Have any Focusrite users seen this? I do plan to post on the Focusrite site if possible. Doesn't seem to have a causality- it's pretty random. Please note- this isn't dire- it's just kind of frustrating. Pro40 is connected to one of the 800 jacks, but the problem also exists with the 400. I should also state that I have played around with buffer settings and Firewire latency in the Saffire MixControl software- I'm currently at 256 samples of buffer and medium firewire latency, but changing these things seems to have no effect. It happens in Soundforge and it happens in Studio One, so I'm fairly certain that it is Focusrite centric. I can start recording with a clean project and a single track and it will do it. Here's what I know- it has nothing to do with plugins. I had to quit Soundforge and cycle the Pro40 and it came back and worked well for quite awhile, and then it did it again. I say that this is not Reaper-centric because yesterday it happened while I was in Sony Soundforge 11. I have found that if I go to Preferences, Audio, and just click OK (and change nothing) the Focusrite will "reset" and everything starts working again. I'll hit stop, the system will respond (the play light goes out) but when I restart playback, Reaper will not play. However:Įvery now and then, while recording, Reaper will just halt. Everything works pretty well- the preamps on the 40 are AMAZINGLY good, and everything has been pretty solid. I have TI Chipset card now that was recommended by the Focusrite web site. At the same time, I replaced the firewire card I had been using because it had a VIA chipset, and I understand that this unit doesn't get along well with VIA. I recently purchased a Focusrite Saffire Pro 40. I thought I'd post it here because this community has been pretty good about helping solve a couple of issues lately. I should start right off by saying that this isn't a Reaper-centric problem.
0 Comments
Leave a Reply. |