Dude as I said your having a UEFI bios issue you can turn UEFI off and run in bios mode.
if you read through this thread you will find the FW card you have has issues with
UEFI bios which is why boom R suggested the PCIE syba card as an alternative.
Boom R if your in the know.
Is there a PCI Card that works as well as the syba in your opinion?
The Syba card that many of us on here use works perfectly & OoB.
It's still available for purchase on Amazon.com, and
also available from NewEgg, too. Note that the sales package may not be branded "Syba" - it may be branded "Best Connectivity" - (
I posted a thread about that a while back). Note that it comes with a full-size bracket (even though it's billed as a low-profile card)
Belkin also makes some FW cards with TI chipset.
I may need to get with the OP (thelostswede) to see if we can either edit the OP/title of the thread, or maybe close it. Again, if you use UEFI, there are issues with this card. Older boards pre-UEFI
AND when this post was first created-were BIOS, and therefore worked like a champ.
I have not tried disabling UEFI and using standard BIOS to see if this card works with mobo in that mode (not to mention that I don't even have a card that I can use for testing). Maybe someone who is more familiar with mobo architecture can chime in here: If you switch from UEFI to BIOS, do you need to go back to using DSDT? I believe the DSDT-free options in MultiBeast work because of UEFI.
I would be curious to see some metrics on the throughput between a card with PCIe controller chip (like the one being hailed in this post) and cards with PCI 1394 chipset with PCIe bridge (like the Syba card). The thought was that, because a card uses a PCI chip (on a PCIe card), followed by PCIe bridge, that this architecture would add extra overhead or cause more lag in audio signals. My uneducated opinion is that the data transfer between the 2 cards is almost not even worth mentioning (from an audio/DAW standpoint). There are
many more user-friendly things you can do to help reduce latency, including lowering your buffer settings when recording.
Also, it may be a moot point because many of the FW audio interfaces now offer no-latency (or near no-latency) monitoring modes IF you monitor through their audio desk software. MOTU's CueMix, Focusrite's Saffire Control, Apogee Maestro, etc. Disable input monitoring in your DAW, then monitor through the audio interface's audio desk software. Then latency caused by FW when monitoring is no longer an issue. You **may** need to check your tracks to make sure things line up, though (timing-wise).
