The original Win 8 firewire driver glitches constantly. However the new RME driver has improved glitches drastically in conjuction with legacy Win 7 firewire driver (about 1 glitch an hour) and audio stays stable and does not crash out with the long beeeeep.
So for me the new drivers have introduced glitches into audio when used with Thesycon driver. Thesycon firewire driver had glitches with new RME driver and brought back total mix freezing issues, and after about 30 mins long beeeeep. There are three options possible I think:ġ) The new RME-driver does not solve all the freeze-problems.Ģ) The freeze I get now is due to the Sweex FW-card with VIA Chipset (I can replace it for the DAWI again tomorrow and do more tests) Note: I didn't use any windows7 legacy-drivers (yet) It ran fine for 45 minutes, then I got another freeze. Then I noticed this thread and installed the new Win8-driver. Problems disappeared if I removed the FW-card and used a USB-audio interface.īecause I thought the Dawicontrol-card might had a problem, I switched it today for a Sweex VIA-chipset card (I know it's inferior to the DAWI, but I wanted to test things.) I got random computer-freezes with audio hanging all the time, just like others here. I added a separate FW-card (The Dawicontrol DC-1394 PCI) to connect with my Fireface800 I'm so happy, I can now keep my FF400 for hopefully many more years, as it's still in perfect condition - so great to be able to use my gear so long after purchase!īought a new computer in January (ASUS P8Z77 with Win8). So far, still - no problems, even under heavy CPU it's been solid, no glitches!īefore, with the standard driver, even just booting windows and just playing an mp3 would cause problems - sometimes 5 minutes later, sometimes instantly. Hehe, I understand you needing to keep details under wraps, I was just curious as you initially seemed to think it wasn't possible to get things working with Microsoft's problematic drivers.Įither way, I am very thankful and this is why I initially bought my RME, because people always praise your driver stability and updates. This could (could !) mean that even there the legacy driver is no longer needed (in case you needed to change to it before). I will upload a new version this evening which adds the same change for Windows 7. I am still astonished about the positive feedback. It just happened what we always refer to - we were able to finally experience this specific problem on one of our computers with Windows 8. See John’s discussion for the exact steps to change the driver.Sorry, but I can (ok, I confess, I don't want to) give details about the fix itself. That’s worked great for me! It’s great to see those much faster speeds than USB 2. John pointed out that you could go into the Device Manager and change the driver to the 1394 Legacy driver.
Microsoft rewrote the IEEE 1394 (FireWire) driver for Windows 7 and let’s just say it doesn’t seem to work that well. Fortunately, John Zhu came to the rescue on the Tech Net Forums. Many people reported hangs, but none seemed to have a solution.
That’s not good nor was the option of using that pokey USB 2 connection as that wouldn’t take advantage of the SSD drive.īefore I sent the drive back, I did some hard web searching and found I was not alone in people complaining about the Windows 7 FireWire drivers. Alas, on all my machines as soon as I tried to do anything on the drive, Windows 7 hangs completely.
My plan was to use the FireWire 800 connection to the drive so I can get the best portable speed possible. Recently I bought a smoking fast external SSD enclosures from Other World Computing.