Hi all,
This is specifically for anyone using Windows 10 x64 with a FireWire audio interface AND using a host that get regular updates. For the three hosts I use, all have had releases in the last few weeks - two at the end of March and one mid-April. This most recent one, in its latest update, has had problems with my FireWire ASIO driver. It continues to work with other drivers.
If you have had a host update since about 8 April and you're using FireWire, could you please post what hardware you're using. I'm most interested to hear from Echo AudioFire users, as that's what's causing my issue.
Thanks!
-- Peter
Anyone using Win10 x64 with FireWire?
-
- KVRAF
- 7413 posts since 8 Feb, 2003 from London, UK
-
- KVRAF
- 6113 posts since 7 Jan, 2005 from Corporate States of America
I still have FireWire devices, but i don't use Windows for much any more (mostly Mac now). [shrug] Did Windows 10 drop FireWire support?
- dysamoria.com
my music @ SoundCloud
my music @ SoundCloud
-
- KVRAF
- 6113 posts since 7 Jan, 2005 from Corporate States of America
Echo Audio seems to have left the building. I used to have their PCI-based devices (which worked well). I read a lot of positive things regarding RME's drivers. They don't seem to abandon OS or hardware anywhere as often as other developers. But then, their product is very spendy.
- dysamoria.com
my music @ SoundCloud
my music @ SoundCloud
-
- KVRAF
- 2312 posts since 9 Jun, 2002 from East of Santa Monica
Ouch. One big reason why I'm still on Win 8.1. I haven't seen a more disruptive POS than Win10. (POS standing for PC operating system 
).
I don't seem to have FW issues others often complain about but I think that's mostly because I've used PCI/PCIe Firewire cards (TI chipset) in my last two DAW PCs.
Of course your problem may not be FW-related, but that your Echo drivers have been finally rendered obsolete. As a test, switch over to the Legacy Firewire drivers as explained here:
https://www.studio1productions.com/Arti ... wire-1.htm
(You can ignore the instruction about the FW card, just use your onboard FW port - assuming that's what you're using).
If it doesn't fix the problem, it's likely the Echo drivers. If it does work, then stick with the legacy drivers or then you might consider trying a PCI FW card.
).I don't seem to have FW issues others often complain about but I think that's mostly because I've used PCI/PCIe Firewire cards (TI chipset) in my last two DAW PCs.
Of course your problem may not be FW-related, but that your Echo drivers have been finally rendered obsolete. As a test, switch over to the Legacy Firewire drivers as explained here:
https://www.studio1productions.com/Arti ... wire-1.htm
(You can ignore the instruction about the FW card, just use your onboard FW port - assuming that's what you're using).
If it doesn't fix the problem, it's likely the Echo drivers. If it does work, then stick with the legacy drivers or then you might consider trying a PCI FW card.
Last edited by flugel45 on Thu May 04, 2017 3:24 pm, edited 1 time in total.
-
- KVRAF
- 24455 posts since 7 Jan, 2009 from Croatia
I've used FW shortly on W10 (TC Electronic Impact Twin), it worked just fine - no distruptiveness of any sort. Had a PCIe FW card with TI XIO2003 chipset, everything was spot on.
https://www.amazon.co.uk/SEDNA-PCI-Expr ... ge_o00_s00
https://www.amazon.co.uk/SEDNA-PCI-Expr ... ge_o00_s00
-
- KVRAF
- 6097 posts since 5 Jul, 2001 from Just about .... there
My new MB does not have FW built in, so I had to get an expansion card. Couldn't find a TI chipset one. I can run at 44 and 48 without issue. But, I can no longer run at 96. I'm assuming it's the expansion card. I would get another one, but I'm going TB shortly, so I'm not worried about it.
At 44 and 48 it works flawlessly at low latency with an Lynx Aurora FW.
At 44 and 48 it works flawlessly at low latency with an Lynx Aurora FW.
If you have to ask, you can't afford the answer
-
- KVRian
- 589 posts since 16 Jun, 2003
I'm using Win10 build 1607 with an M-Audio Projectmix I/O without any issues. I dread each new build of Windows as I fear it will be the end of an £800 piece of hardware. I was holding back on build 1607 until I left my PC on overnight and it installed automatically - despite the fact that updates were supposed to be disabled.
LooneyJetman - Follow me on Spotify | Bandcamp
-
- KVRAF
- 18503 posts since 26 Jun, 2006 from San Francisco Bay Area
I am. RME Fireface 400 and Live 9. Works fine.
Zerocrossing Media
4th Law of Robotics: When turning evil, display a red indicator light. ~[ ●_● ]~
4th Law of Robotics: When turning evil, display a red indicator light. ~[ ●_● ]~
-
- KVRAF
- Topic Starter
- 7413 posts since 8 Feb, 2003 from London, UK
Hi,
Thanks for all the responses.
Just to clarify the current position.
My Firewire port works in Windows 10 for all programs except one when used with its ASIO driver in 64bit mode. That one program worked up until its version at the start of April 2017. 64bit versions of the program after 2 April 2017 have not worked. The other programs I have -- that have not been updated since the end of March 2017 -- continue to work: the next most recent being Reaper was last modified 23 March and Stagelight on 20 March. The 32bit version still works. The 64bit version still works with the MME driver.
There are no errors. The Echo FireWire Analyser, however, shows only one output buffer being written - so the driver does get activated. (Input buffers cycle up at the usual rate -- I've nothing to test with to see if they'd contain audio data.)
The program, MuLab, gets frequent updates. Releases on 1, 2, 4, 8, 14, 23 and 31 March and 2 April all worked. It next had an update on 8 April, which didn't work and triggered my investigations. None of the 11 subsequent updates has worked.
Windows 10 1607 updates have been applied on 17 March (KB3150513), 9 April (KB4015438), 11 April (KB4015217, KB4018483, KB890830), 22 April (KB3150513) and 2 May (KB3150513).
I asked on MSDN and also got no response.
If anyone with a Firewire card and Windows 10 64bit would like to test out MuLab, please feel free to grab MuLab 7.4.6 from http://mutools.com/mulab-downloads.html and let me know how it goes.
Thanks,
-- Peter
Thanks for all the responses.
Just to clarify the current position.
My Firewire port works in Windows 10 for all programs except one when used with its ASIO driver in 64bit mode. That one program worked up until its version at the start of April 2017. 64bit versions of the program after 2 April 2017 have not worked. The other programs I have -- that have not been updated since the end of March 2017 -- continue to work: the next most recent being Reaper was last modified 23 March and Stagelight on 20 March. The 32bit version still works. The 64bit version still works with the MME driver.
There are no errors. The Echo FireWire Analyser, however, shows only one output buffer being written - so the driver does get activated. (Input buffers cycle up at the usual rate -- I've nothing to test with to see if they'd contain audio data.)
The program, MuLab, gets frequent updates. Releases on 1, 2, 4, 8, 14, 23 and 31 March and 2 April all worked. It next had an update on 8 April, which didn't work and triggered my investigations. None of the 11 subsequent updates has worked.
Windows 10 1607 updates have been applied on 17 March (KB3150513), 9 April (KB4015438), 11 April (KB4015217, KB4018483, KB890830), 22 April (KB3150513) and 2 May (KB3150513).
I asked on MSDN and also got no response.
If anyone with a Firewire card and Windows 10 64bit would like to test out MuLab, please feel free to grab MuLab 7.4.6 from http://mutools.com/mulab-downloads.html and let me know how it goes.
Thanks,
-- Peter
-
- KVRist
- 257 posts since 23 Oct, 2005
The 64 bit version of Mulab 7.4.6 works fine here.
I'm running 64 bit windows 10 version 1703, build 15063.250 with a startech firewire expresscard and a focusrite pro40. If you want more specific info, lmk.
Edit: Setup works across two different machines with 3 other DAWs. The only hiccup I've had was windows update switching from the legacy firewire driver to a newer one. Here's an article about the easy fix for that.
I'm running 64 bit windows 10 version 1703, build 15063.250 with a startech firewire expresscard and a focusrite pro40. If you want more specific info, lmk.
Edit: Setup works across two different machines with 3 other DAWs. The only hiccup I've had was windows update switching from the legacy firewire driver to a newer one. Here's an article about the easy fix for that.
-
- KVRAF
- Topic Starter
- 7413 posts since 8 Feb, 2003 from London, UK
Thanks for trying that out -- it gives me some hope.
Unfortunately, that MSI file failed to do anything here, just bailed out silently, leaving no trace of the "(Legacy)" driver. I'm using some StarTech card, if I remember rightly, too.
@EDIT@ Aha, got the MSI sorted.
#EDIT2# Unfortunately it made no difference at all. All the applications that worked with the TI driver and the non-legacy generic driver worked with the legacy driver. Unfortunately, the program that did not work with the TI driver and the non-legacy generic driver also did not work with the legacy driver. So it's not the driver. Which makes sense. The driver didn't change.
Unfortunately, that MSI file failed to do anything here, just bailed out silently, leaving no trace of the "(Legacy)" driver. I'm using some StarTech card, if I remember rightly, too.
@EDIT@ Aha, got the MSI sorted.
#EDIT2# Unfortunately it made no difference at all. All the applications that worked with the TI driver and the non-legacy generic driver worked with the legacy driver. Unfortunately, the program that did not work with the TI driver and the non-legacy generic driver also did not work with the legacy driver. So it's not the driver. Which makes sense. The driver didn't change.