![]() However that still doesn't explain why it works in Windows 7 but not 10. So it seems the Pro24 doesn't get enough juice from Firewire even though Focusrite claim it as an acceptable setup. As soon as I plugged one in the issue disappeared. Googling led me to a few different but similar-ish issues with the Dual Saffire setup that folks fixed by using a PSU for the Pro24 instead of relying on Firewire power. So I turned the PC off and connected the Pro24 Firewire through the Pro40 as I always do and immediately I was having the audio dropout issue again, worse than before actually. At this point I was figuring 1809 was indeed the solution until I notice that, when installing the Saffire software, I never reconnected the Pro24. I then played a CDs worth of audio with no issues. (This fixes the 96kHz issue which I knew already courtesy of u/One-Jury-9530.) I set the Advanced tab for the Saffire to default to 44.1kHz 16bit. Install Win 10 1809, install drivers and MusicBee for an audio test. I'd already tried it and got the same results I had at the time (couldn't keep the Saffire from jumping to 96kHz sample rate), but I decided to give it another go and here's what happened. ![]() I've been running Win10 1903, since I read it was the last version to support Firewire, although it seems 1809 is the more likely "final" version. Tried a whole bunch of stuff over the last few weeks including ASIO4ALL, reinstalls (again), and any tricks the interwebz can give me, but without success. Hopefully one of you were in the same hole and found a way out. I can't seem to find anyone who has had this experience but that can't possibly be true. Um, so WTF? What have I not tried? I'm about a month and a half into this build and a lot of time on teh webz as the kids say. Those are what I load into the Mix Control for both OSs. It's also not settings (or shouldn't be) since I have master files for the saved settings. I've been running these with Win7 for ~7 years with no issues. I have a Win7 dual boot (because I knew Win10 was going to be a PITA for Firewire) which works seamlessly. I've done so many scratch reinstalls of Windows I could do it in my sleep. Once it's working it's solid until the next reboot. I can mess around with it (loading defaults, playing with sample rates, multiple reboots) and I can get it to work sometimes, but I can't see a consistent pattern in what I'm doing that makes it suddenly work. I've blocked all Windows updates and I'm using the legacy firewire driver. ![]() I'm using Win10 version 1903, although the issue shows with 1809 also, with Mix Control 3.7. I'm running a Pro40 and a Pro24 through a Firewire card in my PC. If I stop the audio source I can change the sample rate, but then no applications recognize the existence of the Saffires. ![]() ![]() Sometimes it boots to 96kHz, and whenever the sample rate is 96kHz there's a "pulsed" crackle. It also does this with YouTube or any other sound source for that matter. It plays the music weirdly but with a crackle. Whenever I try to play a 44.1kHz mp3 it switches to 96kHz sample rate. Just built a PC to upgrade my home setup and move to Windows 10. ![]()
0 Comments
Leave a Reply. |