
- Focusrite saffire pro 40 drivers install#
- Focusrite saffire pro 40 drivers drivers#
- Focusrite saffire pro 40 drivers update#
- Focusrite saffire pro 40 drivers driver#
I'll keep you posted if the fix will be stable and persistent or is it a stroke of luck for now. Gushue - maybe this is something that might help your friend too?
Focusrite saffire pro 40 drivers driver#
the issue is not happening, at least for now! So, basically, I went to Legacy driver and then back to the "normal" up to date one, alleviating the Kyle P.
Focusrite saffire pro 40 drivers drivers#
Then, I re-did the procedure, but with Texas Instruments driver for the Firewire controller, again re-installing Focusrite drivers as well.Īnd. What happened was the good old noise in the speakers, so I was bummed.
Focusrite saffire pro 40 drivers install#
I did so, removed Focusrite drivers, and did a clean install of Firewire drivers and most up-to-date Focusrite drivers. After that, my system was always running on Texas Instruments 1394 OHCI Compliant 2.1 - before updating to 1909, and afterwards.īut! According to your recommendation, I tried installing the legacy one again. I did use legacy 1394 driver before with little success, as my Saffire when powered on with the legacy driver were outputting some weird and disconcerting noise I didn't want to experience. I won't say resolved, but surprisingly mitigated, after many trials and errors. Being a software engineer myself, I hope to be able to provide some valid information to help track this down. I will post as much details as I can later tomorrow, I have to compile them down in a reasonably formatted e-mail. Thanks, that's a lot! Knowing you are aware of this sometimes happening is quite reassuring. The OP on the thread seems to have found at least a tempory solution. Windows is however currently setting the framework for midi 2.0, which is amazing, since midi 1 has been relavant since what 1980? Its mostly security updates relavant for general use. Especially in the OS, which rarely makes any audio centric improvements. Incremental upgrades are asking for problems. The software subscription model is awful imho, and the exact opposite of what audio engineer's need, which is a set and forget system. Ive incorporated a basic laptop as a buffer for software updates so i can evaluate them before updating the main system. This is infuriating on one hand since its just code, on the other hand if your software is backed up and organized, its good that hardware will run it for a long while, at least up to this point. Most of the issues are on the software side, not the actual computer hardware. My power supplies were around 100 bucks, and have a 10 year warranty, my Ram, lifetime warranty.Īgain i hate the obsolescence thing, but given its our world right now, we really have to be more responsible as equipment owners to backup our data, and dilligently save OS install versions, and especially drivers, so we can keep legacy systems running. So a computer system can last nearly 2 decades. There's still a lot of computer systems running Windows xp in the buisness world.
Focusrite saffire pro 40 drivers update#
I think they can do a better job with legacy support, but the update is optional for w10 pro (generally speaking). Its important to note tho that this was the result of an OS update. it reminds me of the definition of insanity. Kurt Foster, post: 464506, member: 7836 wrote: as long as you depend on a computer to record audio you will be forced to go through the same cycle.
