Siig firewire card problems

Hello guys.
Can anyone help me please. I have installed a new siig 2 port pcie TI firewire card to work with my focusrite saffire pro 24 dsp to try and iron out some sound issued with my onboard firewire. I cannot get any sound out of the saffire when plugged into the new card. The lights come on and it says it's connected but no sound and the mix control software says no device connected. External sources i.e. guitar show on the input gain leds but no sound. Tried disabling realtek sound drivers and onboard firewire but no joy. I have powered down and plugged back into the onboard firewire and everything works so no hardware issues with saffire or firewire cable.
Can anyone help me to determine if the new card is at fault or my pc settings.
 
Cheers

Thanks for the reply BretB
The answer is sort of. The card comes with the driver onboard. The Siig website says that the card has the latest driver, no download available.

It would be useful to know which version of Windows you are running, and whether 32 or 64 bit. Also the part number/name of the card.
 
Cards generally do not come "with the driver onboard". Siig's website says (for the couple of random cards I looked at) that they use the driver that comes as part of Windows, so assuming that's the case for yours Windows should have spotted the card has been installed. searched the Windows driver repository on your PC and loaded the (hopefully) correct driver. This may or may not have happened.
 
If you go into Windows control panel/device manager does the card show up in the list of devices? If so does it have an exclamation mark next to it? If you right click on the card and call up its properties does Windows tell you a driver is loaded and he card is working properly?
 
If the card is absent from the devices list try right-clicking on the name of your PC (at the top of the list) then "scan for hardware changes" and see if Windows now finds the card and loads a driver. You may need to have the PC on-line doe this as Windows may need to check the Microsoft website for a driver as well as the local files.
 
Be aware that getting firewire cards to work, especially with audio, can be a nightmare in Windows.
 
If the firewire card is reported as working correctly in device manager, is the saffire shown as present as well? If so, is that shown as working?

Hi tlw and 2:43 AM.
here are some specs you mentioned.
Intel Core i7 2700K  Gigabyte Z68X-UD3H-B3   32Gb Corsair Vengeance RAM   Windows 7 64bit  Sonar X2a Producer   Focusrite Saffire PRO 24 DSP   NVIDIA MSN GeForce GTX 650 Ti.
 
The card is a SIIG DP FireWire 2-Port PCie part number NN-E20012-S2. In device manager the card is present and is working. I have tried legacy driver and that just made windows media player not even try to play songs ( this has been the most convenient way to do a quick check, with ti driver WMP attempts to play tracks but no sound i.e song progress bar, no sound).
 
The saffire has all 3 lights lit.
Thanks for the replies.
 
 

SkyMonkey
The card is a SIIG DP FireWire 2-Port PCie part number NN-E20012-S2. In device manager the card is present and is working. I have tried legacy driver and that just made windows media player not even try to play songs ( this has been the most convenient way to do a quick check, with ti driver WMP attempts to play tracks but no sound i.e song progress bar, no sound).
 
The saffire has all 3 lights lit.

 
OK, this is the exact same card that I am looking to buy! It is in my vested interest to ensure this card works for you, and in turn works for me in the future (have not bought yet)!
 
Three lights lit means that the Saffire should be connected and operable. I have the Pro 24 (non-DSP), but I would assume they both operate the same.
 
Per Focusrite, the legacy Firewire drivers were not required with MixControl 3.0 and later updates. We're now on v3.2, I believe. If drivers are available from Siig's website for the NN20012 card, and Win7 doesn't auto-find and load the correct ones, I would assume the Texas Instruments 1394 OHCI Compliant Host Controller (as displayed in the Device Manager) is the correct one.
 
Speaking of MixControl, make sure everything is still adjusted and OK in there too, i.e. main volume knob to 0dB, no mutes enabled, applicable monitors turned on (the 6 square buttons on the right--mine are all blue), monitor outputs configured correctly (DAW1, DAW2 to Monitor Outputs 1, 2, etc.). Also, make sure both the Saffire's sample rate and Windows sample rate are the same. I use 48kHz because of ADAT-sync, so I must configure Windows the same way to play audio outside of Sonar. Therefore, go to Playback Devices (right-click Windows volume icon) and go to the Advanced tab. Set the Default Format to 44.1kHz, 48kHz, or 96kHz depending on your setup. Click the test button. Hopefully you hear the chimes. Do the same for recording devices.
 
*** I don't fully understand how this works, because even high sample rates will play back (interpolated?), but I seem to have less issues if the Windows sample rate is set up to be the "native" sample rate of the Saffire. Otherwise, when opening up various audio applications outside of Sonar, e.g. Sound Forge, the Saffire will temporarily lose its connection until the time I click the record button in said application. ***
 

SkyMonkey
The issue with Hot Plugging. Do I have to power down the whole system to avoid hot plugging or can I just use the power switch on the back of the saffire and switch plugs then.

I don't know if I believe in the whole hot-plugging-causes-damage thing. I'm sure older equipment and cards were that way, but newer cards adhering to the IEEE spec should be OK. With the camcorders I've used in the past, and even the Saffire to this day, I've never had a problem. However, err on the side of caution. The switch on the back should work, but upon subsequent reconnect and power up, just ensure all three lights are ON. If so, that should mean it's connected and operating. To be doubly-sure, however, I would just restart the computer after a connection to ensure it's OK and working properly.
 
You may want to download an application called DPC Latency Checker to see if somehow, some way this new card isn't causing a crippling latency that is not allowing audio to pass through.  When running DPC Latency Checker, the bars in the graph should be small and green.  Try it when idle and when playing audio (iTunes, WMP, etc).

^^^^^^^
Wow, SkyMonkey. This is some serious stuff if the Focusrite guys can't figure it out! I hope for the best. I will definitely be watching this thread, so please keep us posted. Thanks. And for now, my NN20012 card is on hold!
 
Before installing the PCIe card, what kind of audio issues did you experience?  Also, just curious, what length and what brand Firewire cable are you using?

Hi guys.
Thanks again for the responses.
2:43 AM, audio issues are crackles on some guitar VST's (Guitar Rig 5) and on some synth VST's (FM8). I got the firewire cable from Maplins for about £15.00, so not a cheap knock off I hope. It is 1.5m and as I've said all works well on mobo FW apart from occasional crackles.
Fireberd, Hi, I have tried uninstalling the drive in the way described but no joy.
I am still waiting to get back in contact with Focusrite tech support, it's the weekend, and am awaiting a reply from SIIG.
I am off for a couple of days so I will catch up with all posts soon and update on any tech support I get.
 
Cheers
SkyMonkey

Jay Tee 4303
I have 3 Siig Firewire cards, two 800/400s and one straight 400, none of them are recognized by any of the 3 PCs in the main tracking room, driver updates don't help...I'll trade the Siigs for three Fender thin picks and the cell number for a smokin brunette who plays bass like Tiran Porter.

If this is the case, then why does Focusrite give Siig cards no less then four slots of recommendation in their IEEE-1394 Card Compatibility Article??! Very strange indeed!
 
http://d3se566zfvnmhf.clo...patibility_article.pdf

Back to the OP for just a moment...and this may be a stupid question, but I gotta ask...since it's a PCIe, you did plug in an external, 4-pin Molex power plug to the back of the card, right?
 
EDIT: Also, Google and download a small app called ohciTool.exe. It scans and reports connection and compatibility with Firewire cards/interfaces. It may be worth a shot and running the app to see what it reports. If you can't find it, I can email it to you.

Cheers for the link Deering
 
Here are the results.
the top is the SIIG and the bottom is the Gigabyte onboard.
 
OS: Microsoft Windows 7 64-bit Service Pack 1 [6.1.7601]
  Microsoft 1394ohci.sys [6.1.7601.17514]   Microsoft ohci1394.sys [6.1.7600.16385] (legacy)   Microsoft 1394bus.sys [6.1.7600.16385] (legacy)
Looking for OHCI 1394 Host Controllers...
1:   Vendor : (104C) Texas Instruments   Chipset: (8235) XIO2200A   Revision: 01   Max 1394 Speed Capability: S400   Support:  Compatible, no known issues.
2:   Vendor : (1106) VIA Technologies   Chipset: (3044) VT6307/VT6308   Revision: C0   Max 1394 Speed Capability: S400   Support:  Compatible, no known issues.
Done.
 
First time I ran the SIIG card was with the Molex plugged in but will try again.
 
Will post with results. (Really hope I'm just an idiot!)

Hello... My PCI firewire card of choice is the Adaptec 4300 (AFW-4300), Adaptec FireConnect 4300 (boxed retail), has the TI Chipset and Windows 7 loads the driver needed for my Presonus Projects. Old production cards still found/sold on EBAY.
 
Just other thoughts on your problems...
1) are you using the proper pin cable in your new card? FW800 have 9-pins connectors FW400 have 6-pins, adaptors are needed between the two... have you verified your connectors and pin numbers, between all the hardware in your setup? WIKI firewire for diagrams and info.
2) have you tried to disable the onboard Firewire in your motherboard BIO's for any of your testing? interrupt conflict?
3) have you tried to disable the onboard audio in your motherboard BIO's for any of your testing? interrupt conflict?
4) have you tried to raise your buffer size with your onboard Firewire/Audio settings? Clicks/POP problem.
5) have you defragged your current projects on your hardrive/storage location? Clicks/POP problem.
 
: )

One final though, and I don't think anyone has suggested this.  With the PCIe card installed, and Windows running, reinstall the Intel motherboard chipset drivers and see if that changes anything.  One of the things the chipset drivers do is identify (define) all the devices on or attached to the motherboard. 
 
You can get the latest chipset drivers direct from Intel.  Go to the Intel site and let it "automatically find drivers and software".  Since its not an Intel motherboard it won't find much, but it will find the chipset drivers. 

OK
Latest update. Thanks for the post Fireberd, I found the Intel site quite unhelpful but events have surpassed initial problems. I noticed that I was having trouble shutting down my PC (it would simply reboot) so I googled the problem and discovered that my PC was crashing on shutdown with a very brief BSOD and automatically rebooting as per windows settings. The web page showed how to stop the reboot in settings but suggested that this would only mask a more serious problem, one culprit mentioned being new hardware. So I removed the SIIG and no more shutdown crashes.
Also SIIG themselves have been in contact after I lodged a tech support question. The first reply asked simple driver questions, so instead of going through the whole thing again I directed them to this thread. Yesterday I got this reply.
 
Hello,
This product could be defective or not compatible with your system. Please return it where you purchased it from for replacement.
Thank you.
Regards,
Erick 

SIIG Support
 
So the card is going back for a refund, never to be seen again.
Take this as a FAIL for the card. For me anyway.
 
I will post when I get a different card but this may not be for a couple of weeks. I am going to order a Startech TI PCI card part number PCI1394MP. Any experiences with this card would be greatly appreciated.
 
Thanks for all you help guys

Well, stick a fork in it, this thread and issue is done, right?  Too bad it couldn't be resolved--totally sucks.

^^^^^
Good news, SkyMonkey! Glad you got things to work...finally!!!   Yes, I will agree with you on the graphics card vs. PCIe card.  Worrying about the same thing, a couple of weeks ago I test-fitted a eSATA PCIe card, and it sure is right up close to the fans. Probably not too big of a deal since my card has two, monster-sized fans, but still.
 
Thanks for good luck wishes.  So far my system has been relatively stable for me using my motherboard Firewire port. I've made some changes in my workspace (i.e. eliminated countless, stupid and crappy plugins) and increased my buffer size by two.  MixControl is currently at Medium-128 (at 48kHz).  Sonar reports total round trip at 7.9ms with these settings. I wish I could do better, but at least it's stable as I have less "unexpected stop" application crashes.
 
Please post your latency and settings when you get a chance. I'm curious to see what they are. Right now, I got a red light on my Firewire-card-purchase future, but maybe will reconsider if your numbers are quite low in comparison.