Helpful ReplyFirewire VIA chipset and Windows 10 - BEWARE!

Page: 12 > Showing page 1 of 2
Author
Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
2015/08/09 20:26:44 (permalink)

Firewire VIA chipset and Windows 10 - BEWARE!

I'm running a test Windows 10 partition and notice there are connectivity issues between VIA firewire and Saffire Pro, as confirmed here:
http://uk.focusrite.com/answerbase/windows-10-compatibility
 
I don't know if other VIA firewire chipsets are effected.
Just a heads up!
 
Thanks...
post edited by Doktor Avalanche - 2015/08/09 23:06:42

Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
#1
Maarkr
Max Output Level: -81 dBFS
  • Total Posts : 488
  • Joined: 2011/12/10 09:35:33
  • Location: Maine
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/10 11:11:56 (permalink)
knock on wood... i have a VIA VT6308 chip in my Gigabyte mobo and my Saffire Pro 24 has worked so far.  Seems like my chips is one recommended in their document below...
 
focusrite has an app on their site that will analyze your chipset and give advice on it...
http://us.focusrite.com/a...h-my-interface?id=1184
 
here is their pdf that talks about acceptable firewire devices...
http://d3se566zfvnmhf.cloudfront.net/sites/default/files/answerbase/Focusrite%20IEEE%201394%20Compatibility_0.pdf
 
just found out the urls get shortened in the forum... if u rt click on them you will go there... if you copy it it will not work.
 
post edited by Maarkr - 2015/08/10 14:45:45

Maarkr
Studio: SPALT Lifetime/BL Cakewalk, Studio One 3.5, UAD, Z3ta+2, IKM, NI, Waves, iZotope, Melda, Reaper
i7 3770/Giga Z77 mobo, Win10 Pro-64 w16Gb, MOTU Ultralite MK4, Yamaha HS80M wSub, Live: PX-5S, FA-06, Roland Lucina, Epi Les Paul, Ibanez Bass, Amps, e-drums, Zoom R-16...
Latest album release, NEW! Counry Classic at http://genemaarkr.bandcamp.com/
#2
Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/10 11:39:46 (permalink)
You are running running 3.4. I'm running 3.6 . Maybe that I the issue.

Btw under Win8.1 at least 3.6 is by far a better driver.
post edited by Doktor Avalanche - 2015/08/10 11:47:33

Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
#3
arachnaut
Max Output Level: -67 dBFS
  • Total Posts : 1168
  • Joined: 2007/05/05 17:24:33
  • Location: Sunnyvale, CA USA
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/10 12:02:05 (permalink)
I have had no problems since upgrading to Windows 10 last week.
 
I'm running Windows 10 Pro with Mixcontrol 3.6 downloaded from the Saffire Pro 40 location (although I'm using the Pro 14). The OHCI scan tool reports this:
 
Looking for OHCI 1394 Host Controllers...
1:
Vendor : (1106) VIA Technologies
Chipset: (3044) VT6307/VT6308
Revision: C0
Status : Active
Details:
Subsysten VendorId: 1043
Subsystem DeviceId: 81fe
Max # isoch Rx contexts: 4
Max # isoch Tx contexts: 8
Max 1394 Speed Capability: S400
Support: Compatible, no known issues.
Done.

- Jim Hurley -
SONAR Platinum - x64  - Windows 10 Pro 
ASUS P8P67 PRO Rev 3.0;  Core i7-2600K@4.4GHz; 16 GB G.SKILL Ripjaws X;
GeForce GT 740; Saffire Pro14 MixControl 3.7; Axiom 61
64-Bit audio, SR: 48kHz, ASIO 256 samples latency, Rec/Play I/O Buffers 512k, Total Round Trip Latency 13 ms, Pow-r 3 dither 
#4
Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/10 12:07:55 (permalink)
OHCI shows as compatible on my machine as well. Regardless is a known issue see Focusrite link. Glad it works for some.

Btw I didn't upgrade. This was a clean Win10 install after formatting the hard drive. I do have an upgrade somewhere else I will try that next.

Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
#5
arachnaut
Max Output Level: -67 dBFS
  • Total Posts : 1168
  • Joined: 2007/05/05 17:24:33
  • Location: Sunnyvale, CA USA
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/10 12:56:22 (permalink)
I have Firewire latency set to 'Medium' - 'Short' did not do as well for me.
 


- Jim Hurley -
SONAR Platinum - x64  - Windows 10 Pro 
ASUS P8P67 PRO Rev 3.0;  Core i7-2600K@4.4GHz; 16 GB G.SKILL Ripjaws X;
GeForce GT 740; Saffire Pro14 MixControl 3.7; Axiom 61
64-Bit audio, SR: 48kHz, ASIO 256 samples latency, Rec/Play I/O Buffers 512k, Total Round Trip Latency 13 ms, Pow-r 3 dither 
#6
Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/10 13:31:40 (permalink)
Upgrades don't work either. So that's both clean install and upgrades.
It's definitely the chipset model. Looks like you have a variant that works.
The symptoms are that you can't connect to the interface (as Focusrite explains) so you can't even adjust the settings if you tried.
 
Nevermind my DAW is still on Win8.1
post edited by Doktor Avalanche - 2015/08/10 13:39:49

Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
#7
arachnaut
Max Output Level: -67 dBFS
  • Total Posts : 1168
  • Joined: 2007/05/05 17:24:33
  • Location: Sunnyvale, CA USA
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/10 13:52:53 (permalink)
If it helps, here is how my firewire drivers look:
 


- Jim Hurley -
SONAR Platinum - x64  - Windows 10 Pro 
ASUS P8P67 PRO Rev 3.0;  Core i7-2600K@4.4GHz; 16 GB G.SKILL Ripjaws X;
GeForce GT 740; Saffire Pro14 MixControl 3.7; Axiom 61
64-Bit audio, SR: 48kHz, ASIO 256 samples latency, Rec/Play I/O Buffers 512k, Total Round Trip Latency 13 ms, Pow-r 3 dither 
#8
Maarkr
Max Output Level: -81 dBFS
  • Total Posts : 488
  • Joined: 2011/12/10 09:35:33
  • Location: Maine
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/11 11:04:45 (permalink)
DA, the driver on the focusrite website for my Saffire Pro 24 is ver 3.4.  I'm going to stick with it as long as it's working.  

Maarkr
Studio: SPALT Lifetime/BL Cakewalk, Studio One 3.5, UAD, Z3ta+2, IKM, NI, Waves, iZotope, Melda, Reaper
i7 3770/Giga Z77 mobo, Win10 Pro-64 w16Gb, MOTU Ultralite MK4, Yamaha HS80M wSub, Live: PX-5S, FA-06, Roland Lucina, Epi Les Paul, Ibanez Bass, Amps, e-drums, Zoom R-16...
Latest album release, NEW! Counry Classic at http://genemaarkr.bandcamp.com/
#9
ampfixer
Max Output Level: -20 dBFS
  • Total Posts : 5508
  • Joined: 2010/12/12 20:11:50
  • Location: Ontario
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/11 11:48:50 (permalink)
Going back a few years, but wasn't the TI chipset identified as the one to have for Sonar and Firewire? I seem to recall a thread where it was listed as a best practice.

Regards, John 
 I want to make it clear that I am an Eedjit. I have no direct, or indirect, knowledge of business, the music industry, forum threads or the meaning of life. I know about amps.
WIN 10 Pro X64, I7-3770k 16 gigs, ASUS Z77 pro, AMD 7950 3 gig,  Steinberg UR44, A-Pro 500, Sonar Platinum, KRK Rokit 6 
#10
Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/11 11:57:54 (permalink)
ampfixer
Going back a few years, but wasn't the TI chipset identified as the one to have for Sonar and Firewire? I seem to recall a thread where it was listed as a best practice.


The DAW is irrelevant, it's the hardware it connects to. VIA has worked perfectly fine until Win10. Either Focusrite or VIA driver to blame.

The PDF posted here gives a list of Focusrite compatible chipsets
:

http://uk.focusrite.com/answerbase/how-can-i-tell-if-my-firewire-chipset-is-compatible-with-my-interface

All Sonar is concerned about is a good ASIO driver.
post edited by Doktor Avalanche - 2015/08/11 12:06:42

Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
#11
arachnaut
Max Output Level: -67 dBFS
  • Total Posts : 1168
  • Joined: 2007/05/05 17:24:33
  • Location: Sunnyvale, CA USA
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/11 14:27:51 (permalink)
ampfixer
Going back a few years, but wasn't the TI chipset identified as the one to have for Sonar and Firewire? I seem to recall a thread where it was listed as a best practice.




Firewire was originally adopted as a connection favored by movie makers and used to attach movie gear.
It tended to be more adopted by the Apple users, since Apple invented it.
Apple wanted a licensing fee for each interface, so Intel came out with USB alternatives.
Firewire and now Thunderbolt always stayed a step ahead of USB, but now with USB 3.1, we probably have a break-even point again.
 
However, it will still be a while before we see newer USB devices.
 
Firewire is probably considered dead nowadays as few pieces of newer equipment support it. And Thunderbolt is very expensive, power hungry and thermally active. All the connectors are active. USB is far more universal and the newest USB 3.1 stuff with that great new connector will probably become the de-facto standard in years to come.
 
Back in the XP days, I had a special PCI card that had Firewire 400 and 800 ports because all my external drives were Firewire 800. (This was before e-SATA, which I use nowadays).
 
It did sometimes seem to be trial-and-error to find the right chipsets and drivers because some people had movie gear, others audio, and I had audio and hard drives.
 
These old debates always re-surface when problems come up, but I think the issue is one of just finding out what works for you. The specs haven't changed and all the parts are supposed to conform to the spec. And just when you get things working, some new update will come up and you have to re-tweak things again. That's become a major issue now with so many vendors adopting 'agile' programming techniques.
 
In the past, I found some versions of NVIDIA graphics updates interfered with interrupt latency and made my Firewire interface glitch. But that was quite some time ago. I still try to keep my video drivers up-to-date, even though they are mostly game updates. I do check things with latencymon after updates.
 
For Focusrite drivers, there is a Firewire latency setting (not really audio latency) that seems to apply to the firewire transactions and interrupts. Larger setting might make larger Firewire transactions and heavier interrupt times, while shorter latencies will use smaller chunks at more frequent intervals. At least that is my understanding.
 
I've found the 'Short' setting was inferior for me compared to the 'Medium' latency setting. I was able to load larger and more projects using that.
 
Most of my projects involve humongously complex Reaktor modules (which are single threaded), so I need all the performance per core that I can muster. My tests then are stressed that way - most bang per CPU, not most number of tracks total.
 
 
 
 
 

- Jim Hurley -
SONAR Platinum - x64  - Windows 10 Pro 
ASUS P8P67 PRO Rev 3.0;  Core i7-2600K@4.4GHz; 16 GB G.SKILL Ripjaws X;
GeForce GT 740; Saffire Pro14 MixControl 3.7; Axiom 61
64-Bit audio, SR: 48kHz, ASIO 256 samples latency, Rec/Play I/O Buffers 512k, Total Round Trip Latency 13 ms, Pow-r 3 dither 
#12
Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/11 18:36:06 (permalink)
Focusrite emailed me today saying situation is still ongoing and they will be emailing me when it is fixed.

Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
#13
Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/28 14:01:14 (permalink)
Apparent workaround.... Not tested.
 
Turn on Saffire.
Start Windows 10
Log in.
Restart Windows 10 (keeping Saffire on).

Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
#14
Jim Roseberry
Max Output Level: 0 dBFS
  • Total Posts : 9871
  • Joined: 2004/03/23 11:34:51
  • Location: Ohio
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/28 14:40:44 (permalink) ☄ Helpfulby glennstanton 2017/06/07 16:26:42
Doktor Avalanche
The DAW is irrelevant, it's the hardware it connects to. VIA has worked perfectly fine until Win10. Either Focusrite or VIA driver to blame.



VIA Firewire chipsets have certainly NOT all worked fine with all audio interfaces up until Win10.
Ever tried to run an M-Audio FW1814 connected to a VIA chipset Firewire controller?  Don't bother, you won't be able to install the driver.
  • Some VIA Firewire chipsets work fine with certain audio interfaces (RME and MOTU are less fussy about controller)
  • Some VIA Firewire chipsets "work" in that you can play/record audio... but performance is poor compared to TI.
  • Other VIA Firewire chipsets result in complete instability (or just plain won't even allow install of audio interface)
 
It's rare, but even some TI chipset Firewire controllers are unreliable with certain audio interfaces.
  • Manhattan makes a TI chipset Firewire controller that doesn't work properly with the MOTU 896HD.  Ironically it works fine with the 8-Pre.
  • UA Apollo, Mackie, and Tascam units are particularly fussy about the specific TI chipset.
 
It's down to the specific combination of Firewire chipset and audio interface.
 
 
post edited by Jim Roseberry - 2015/08/28 14:48:54

Best Regards,

Jim Roseberry
jim@studiocat.com
www.studiocat.com
#15
BassDaddy
Max Output Level: -33 dBFS
  • Total Posts : 4232
  • Joined: 2012/12/31 13:55:58
  • Location: I'm an American. From America!
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/28 14:47:49 (permalink)
Great info in this thread. Thanks everyone.

It's Bass, not Bass.
i7 2700K, 16GB DDR3, 2 SSD sample drives and OS drive, HDD SATAIII for projects, 2 24" monitors
Focusrite Saffire Pro 24, Focusrite VRM Box, LAVA Lamp, SONAR Platinum 64 bit, Mackie MCU and 1 MCU XT, Akai Advance 49, Windows 10,
Komplete 9 Ultimate, Cakewalk, Toontrack, IK, AAS, XLN, UVI, Air Music Tech, Waves Factory, Sample Tek and Sonivox VSTi's. Overloud, T-Racks, Audio Damage, D16, Nomad Factory, Waves Gold FX 
#16
BassDaddy
Max Output Level: -33 dBFS
  • Total Posts : 4232
  • Joined: 2012/12/31 13:55:58
  • Location: I'm an American. From America!
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/28 14:47:49 (permalink)
Great info in this thread. Thanks everyone.

It's Bass, not Bass.
i7 2700K, 16GB DDR3, 2 SSD sample drives and OS drive, HDD SATAIII for projects, 2 24" monitors
Focusrite Saffire Pro 24, Focusrite VRM Box, LAVA Lamp, SONAR Platinum 64 bit, Mackie MCU and 1 MCU XT, Akai Advance 49, Windows 10,
Komplete 9 Ultimate, Cakewalk, Toontrack, IK, AAS, XLN, UVI, Air Music Tech, Waves Factory, Sample Tek and Sonivox VSTi's. Overloud, T-Racks, Audio Damage, D16, Nomad Factory, Waves Gold FX 
#17
Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/28 15:59:26 (permalink)
Doktor Avalanche
The DAW is irrelevant, it's the hardware it connects to. VIA has worked perfectly fine until Win10. Either Focusrite or VIA driver to blame.


Jim Roseberry
VIA Firewire chipsets have certainly NOT all worked fine with all audio interfaces up until Win10.
Ever tried to run an M-Audio FW1814 connected to a VIA chipset Firewire controller?  Don't bother, you won't be able to install the driver.
  • Some VIA Firewire chipsets work fine with certain audio interfaces (RME and MOTU are less fussy about controller)
  • Some VIA Firewire chipsets "work" in that you can play/record audio... but performance is poor compared to TI.
  • Other VIA Firewire chipsets result in complete instability (or just plain won't even allow install of audio interface)
 
It's rare, but even some TI chipset Firewire controllers are unreliable with certain audio interfaces.
  • Manhattan makes a TI chipset Firewire controller that doesn't work properly with the MOTU 896HD.  Ironically it works fine with the 8-Pre.
  • UA Apollo, Mackie, and Tascam units are particularly fussy about the specific TI chipset.
 
It's down to the specific combination of Firewire chipset and audio interface.
 
 


No issues with Win 7 and 8.x at all. Works great, I have had no issues ever until Win10.

The problem is just windows 10 (for the moment). Loads of other drivers are having problems under Windows 10 right now, so obviously it's software not hardware.

And as you see it's deemed perfectly compatible by Focusrite:
http://d3se566zfvnmhf.clo...%20Compatibility_0.pdf

"Chipset Incompatibilities: The FireWire chip controls all data being streamed to and from the FireWire port, and certain chips have been known to cause problems with connectivity. We would recommend using either a Texas Instruments or a VIA FireWire chipset to avoid any such issues."

I trust Focusrite with what they say, they are excellent esp with support. They will resolve this issue.
post edited by Doktor Avalanche - 2015/08/28 16:10:58

Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
#18
ampfixer
Max Output Level: -20 dBFS
  • Total Posts : 5508
  • Joined: 2010/12/12 20:11:50
  • Location: Ontario
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/28 17:50:04 (permalink)
What I've seen posted in the last few years supports what Jim is saying. 

Regards, John 
 I want to make it clear that I am an Eedjit. I have no direct, or indirect, knowledge of business, the music industry, forum threads or the meaning of life. I know about amps.
WIN 10 Pro X64, I7-3770k 16 gigs, ASUS Z77 pro, AMD 7950 3 gig,  Steinberg UR44, A-Pro 500, Sonar Platinum, KRK Rokit 6 
#19
Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/28 17:53:12 (permalink)
ampfixer
What I've seen posted in the last few years supports what Jim is saying. 



And yet the manufacturer of this interface states (again):


"Chipset Incompatibilities: The FireWire chip controls all data being streamed to and from the FireWire port, and certain chips have been known to cause problems with connectivity. We would recommend using either a Texas Instruments or a VIA FireWire chipset to avoid any such issues."
 
If it's Jim vs Focusrite, I think I know who is likely to be correct here in the case of this interface.
 
And I've had no issues with Win 7 and 8.x and VIA - so forgive me for completely disagreeing in the case of Saffires here. There is a specific problem going on with Win 10 (Focusrite drivers or VIA drivers or even the OS itself) and Focusrite are on it. My interface continues to work on 8.1 so it's definitely software not the chip.
post edited by Doktor Avalanche - 2015/08/28 18:05:05

Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
#20
Jim Roseberry
Max Output Level: 0 dBFS
  • Total Posts : 9871
  • Joined: 2004/03/23 11:34:51
  • Location: Ohio
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/29 10:26:13 (permalink)
You can search back thru literally hundreds of posts (from the past 10+ years) of folks having problems with a Firewire audio interface.  In almost every case, the user was running a Ricoh, Lucent, Augere, Via, or other "rogue" chipset Firewire controller.
 
If you want to maximize your odds of success, it makes sense to use a TI chipset Firewire controller.
 
As for pitting me against Focusrite or any other manufacturer, pfffffffft!  
I've turned down job offers from numerous audio software/hardware companies over the past 20+ years.
Focusrite makes some nice hardware... but they're not RME, MOTU, or Lynx when it comes to round-trip latency.
 
 

Best Regards,

Jim Roseberry
jim@studiocat.com
www.studiocat.com
#21
mettelus
Max Output Level: -22 dBFS
  • Total Posts : 5321
  • Joined: 2005/08/05 03:19:25
  • Location: Maryland, USA
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/29 11:32:00 (permalink)
Jim's comment earlier was more global, which made me realize the thread title is misleading. The actual point with the OP is specific to Focusrite Saffire units running Win10 on VIA chipset.

ASUS ROG Maximus X Hero (Wi-Fi AC), i7-8700k, 16GB RAM, GTX-1070Ti, Win 10 Pro, Saffire PRO 24 DSP, A-300 PRO, plus numerous gadgets and gizmos that make or manipulate sound in some way.
#22
Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/08/29 12:00:19 (permalink)
mettelus
Jim's comment earlier was more global, which made me realize the thread title is misleading. The actual point with the OP is specific to Focusrite Saffire units running Win10 on VIA chipset.



I've been very specific about saffire here as well. I'm not disagreeing with his specific point he's right about that, but not in the context of the Saffire interface. You are probably right about the thread title being misleading, although I'm worried there could be other issues with Win10 and VIA chipsets. We shall see.

Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
#23
kitekrazy1
Max Output Level: -40 dBFS
  • Total Posts : 3524
  • Joined: 2014/08/02 17:52:51
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/09/05 14:24:38 (permalink)
Jim Roseberry
Doktor Avalanche
The DAW is irrelevant, it's the hardware it connects to. VIA has worked perfectly fine until Win10. Either Focusrite or VIA driver to blame.



VIA Firewire chipsets have certainly NOT all worked fine with all audio interfaces up until Win10.
Ever tried to run an M-Audio FW1814 connected to a VIA chipset Firewire controller?  Don't bother, you won't be able to install the driver.
  • Some VIA Firewire chipsets work fine with certain audio interfaces (RME and MOTU are less fussy about controller)
  • Some VIA Firewire chipsets "work" in that you can play/record audio... but performance is poor compared to TI.
  • Other VIA Firewire chipsets result in complete instability (or just plain won't even allow install of audio interface)
 
It's rare, but even some TI chipset Firewire controllers are unreliable with certain audio interfaces.
  • Manhattan makes a TI chipset Firewire controller that doesn't work properly with the MOTU 896HD.  Ironically it works fine with the 8-Pre.
  • UA Apollo, Mackie, and Tascam units are particularly fussy about the specific TI chipset.
 
It's down to the specific combination of Firewire chipset and audio interface.
 
 




Has VIA ever updated their 1394 drivers.  The ones that have worked on my systems were dated 2001.
I guess FW interfaces are not a good investment and some of those Sapphire have been on sale.  I'm not a fan of USB since everything is USB.  Few are PCI-x that are affordable.  The lowest price Thunderbolt unit is $200.  I miss the PCI bus. I wonder how long the RME HFs will be manufactured. You can still get RME PCI cards.

Sonar Platinum, W7 Pro 32GB Ram, Intel i7 4790, AsRock Z97 Pro 4,  NVidia 750ti, AP2496
 
Sonar Platinum, W7 Pro, 16GB Ram, AMD FX 6300, Gigabyte GA 970 -UD3 P, nVidia 9800GT, Guitar Port, Terratec EWX 2496
#24
mettelus
Max Output Level: -22 dBFS
  • Total Posts : 5321
  • Joined: 2005/08/05 03:19:25
  • Location: Maryland, USA
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/09/05 14:48:24 (permalink)
The VIA driver I am using came from Microsoft in the Win7 package, but is still older than dirt (6/21/2006, version 6.1.7601.17514).
 
I am of the same mindset that I do not trust potential USB conflicts, so went with FW for that reason (only FW device I have ever owned). Downside is I own enough hardware where driver updates stopped with Win7 that I will be staying here a while longer.

ASUS ROG Maximus X Hero (Wi-Fi AC), i7-8700k, 16GB RAM, GTX-1070Ti, Win 10 Pro, Saffire PRO 24 DSP, A-300 PRO, plus numerous gadgets and gizmos that make or manipulate sound in some way.
#25
fireberd
Max Output Level: -38 dBFS
  • Total Posts : 3704
  • Joined: 2008/02/25 14:14:28
  • Location: Inverness, FL
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/09/06 06:45:00 (permalink)
I used to have a Saffire Pro 40 (with T.I. Chipset in PC) and it worked fine but the best latency I could reliably use was 12ms.  The Safire Pro 40 died and I moved on to USB with a Roland Octa-Capture and halved the latency and now with Windows 10 I'm down to the 4ms range.  I have several USB connected devices for recording, including a BCF2000 and a Tranzport, along with USB controllers for wireless mouse and keyboard, and there are no conflicts.
 
The Saffire Pro 40, like most firewire devices use a DICE (or DICE II) chipset and DICE likes to see a T.I. in the PC.  I used to have a DICE Utility that checked for the firewire chipset (and the DICE web site used to have a statement about using T.I. - I haven't checked lately). 

"GCSG Productions"
Franklin D-10 Pedal Steel Guitar (primary instrument). Nashville Telecaster, Bass, etc. 
ASUS ROG Maximus VIII Hero M/B, i7 6700K CPU, 16GB Ram, SSD and conventional hard drives, Win 10 Pro and Win 10 Pro Insider Pre-Release
Sonar Platinum/CbB. MOTU 896MK3 Hybrid, Tranzport, X-Touch, JBL LSR308 Monitors,  
Ozone 5,  Studio One 4.1
ISRC Registered
Member of Nashville based R.O.P.E. Assn.
#26
Doktor Avalanche
Max Output Level: -32.5 dBFS
  • Total Posts : 4294
  • Joined: 2015/03/26 18:02:02
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2015/09/16 13:41:17 (permalink)
Contacted Focusrite yesterday asking if they have at least located the issue. They just repeated the same line, their "top priority" etc. Worrying... 
post edited by Doktor Avalanche - 2015/09/16 13:49:52

Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.6,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),2 x 1TB SSD (Samsung EVO 850),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5. Rap Pro,Maschine Studio+Komplete 9 Ultimate+Kontrol Z1,Addictive Keys,Waves Silver,Izotope Nectar elements,Overloud Bundle,Geist,Acronis True Image 2015.
#27
35mm
Max Output Level: -68 dBFS
  • Total Posts : 1105
  • Joined: 2008/12/09 08:21:44
  • Location: Devon, UK
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2017/06/07 11:59:40 (permalink)
I hope you don't mind me digging this up. I'm setting up a new system drive and thought I'd try win 10 as I was eligible for a freebie, although I had read bad stuff about driver support for older products. I have an old TI PCI firewire card that I have used in systems for years so I was hopeful it might work with my Safire. It seems not. Anyone heard of any workarounds or fixes for this?
 
I have a Pro 40 elsewhere that I may try out, but I hate hardware going obsolete. I also have an NI Kore controller that I haven't tried out yet, but I guess that will have issues too.
 
EDIT Safire Pro 40 seems to work fine. Safire and sadly my old NI Kore 1 don't.
post edited by 35mm - 2017/06/07 15:10:02

Splat, Win 10 64bit and all sorts of musical odds and sods collected over the years, but still missing a lot of my old analogue stuff I sold off years ago.
#28
abacab
Max Output Level: -30.5 dBFS
  • Total Posts : 4464
  • Joined: 2014/12/31 19:34:07
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2017/06/07 15:25:30 (permalink)
I cannot speak for Saffire, but I can vouch for this FireWire 1394 PCIe card with TI chipset working well in Windows 10.  I am using it with an M-Audio interface.  I had been using it on Window 7, and now Windows 10, with no problems whatsoever.
 
Syba Low Profile PCI-Express 1394b/1394a (2B1A) Card, TI Chipset, Extra Regular Bracket SD-PEX30009
https://www.amazon.com/gp/product/B002S53IG8

DAW: CbB; Sonar Platinum, and others ... 
#29
Sir Les
Max Output Level: -67 dBFS
  • Total Posts : 1182
  • Joined: 2012/07/09 04:56:19
  • Location: MONTREAL, QUEBEC, CANADA,
  • Status: offline
Re: Firewire VIA chipset and Windows 10 - BEWARE! 2017/06/07 17:55:47 (permalink)
LSI firewire 400/800 may also work better for some brands of audio devices.
 
https://www.tonymacx86.co...0-compatibility.59767/
 
 

1. Intel 5960x 3.5mhz , ASUS x99 deluxe u3.1, Asus Thunderbolt ex II,   G skills f4 3000 Memory 32GB , ADATA ssd 250GB Main Drive, Lots of WD Red 7200 Mechanical Drives with Black Drives, 14x multi optical Drive, LG Multi Blu Drive,  2X Extern WD Mybooks usb 3.0, AMD r7 270 video card, Motu 828x TB , Motu Midi XT.
2.  USING MAC PRO, as win 10 has damaged 2 x99 systems 8.1 is also to blame for the final burnout trying to roll back!
 
3.  Something Wonderful: https://1drv.ms/f/s!AlHkRy9cXBbYpQNvVBCt8r7fQ5PS
#30
Page: 12 > Showing page 1 of 2
Jump to:
© 2022 APG vNext Commercial Version 5.1