PreSonus Forums

Hey all,

I'm having issues getting Universal Control to recognize my firewire card and as a result my FPS isn't syncing (solid red light).

I'm on windows 10 using the legacy 1394 OHCI Compliant Legacy Driver:


OHCI Info from UC

OS: Microsoft Windows Version unknown [6.2.9200]
CPU(s):
Processor: Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
Physical: 1
Cores: 4
Logical: 4
L1 Cache: 32 KB (8)
L2 Cache: 256 KB (4)
L3 Cache: 6144 KB (1)
Installed RAM: 12243 MB


Microsoft ohci1394.sys [6.1.7601.22699]
Microsoft 1394bus.sys [6.1.7601.22699]

Looking for OHCI 1394 Host Controllers...


Done.

Notice how after "Looking for OHCI..." it returns nothing and just says done.

Thoughts?

I followed the install guide to a "T", but I suspect this has more to do with my firewire card.

Any help is appreciated.

Regards,

Michael

EDIT:
Oh, this is my firewire card: http://www.amazon.com/Syba-Firewire-IO2213B-Components-SY-PEX30016/dp/B006DQ0KD2?ie=UTF8&psc=1&redirect=true&ref_=oh_aui_detailpage_o04_s00

Have you run latencymon on your system? Looks like you have a disagreement there. Windows seems to recognize it, but looks like UC doesn't. It has a TI chip (reportedly) which are typically the way to go.

Edit: what port are you plugging in to? If you are trying to plug into the FW 800 port, the cable may be the problem. When going from FW 400 to 800, the cable must be rated as bilingual. Make sure it specifically states that, and if not find one that does.

Thanks for the reply!

I'm using the firewire 400 cable that came with the FSP.

I ran latency mon and got "Your system appears to be suitable for handling real-time audio and other tasks without dropouts", so I'm guessing that's a good sign.

I'm using the cable that came with the FPS (6 pin FW 400), but I'm wondering if the card requires a bilingual cable (i.e., the card may have FW 400 looking ports, but is actually FW 800, is that possible?)

Again, thanks. I'll look into the cable.

the card may have FW 400 looking ports, but is actually FW 800, is that possible?

Don't think that's possible. Try a different cable, and also try both ports on the back of the FSP.

Hmm... Just tried it on an old MBP and both ports work. I'm guessing it's something to do with the card and good old Windows 10... this is frustrating!

Tried another cable and same results. I might see if I can find another card to try.

I think it is the card too.

matthewgorman wroteI think it is the card too.

Yeah, that sounds like the problem. Myself and others have gotten Firestudios to run on
Win10 using the legacy driver.

I'm experiencing the same issue. The FSP worked on my old MacBook, but will not connect on my new windows 10 build. The first firewire card I tried was an Iocrest SI-PEX30017. I had suspicions that it was not the right card, so I picked up a Siig NN-E20012-S2. The first card showed in the device manager as present, but the FSP would not sync, and would go from red to blue to red when powered on, with UC version reading all zeroes. The Siig does all the same, except that now when the FSP is powered on, it also shows in the device manager, but has a yellow exclamation mark on it. Tried a, "update driver" on it via the device manager with no change. Also trying to find the solution for the serial port drivers. Mobo chipset drivers had no effect on this. I'm at a loss. Also using the cord that came with the FSP. Any help/ideas would be immensely appreciated.
Cheers,
A

Did you install universal control? That is the driver installer for the FSP, and is needed to operate. Latest version is 1.7.4

I did. Apologies; that's what I was referring to as "UC". It's still installed. Should I do a uninstall/reinstall?

Hi everyone. I was having this exact same issue. I tried a ton of the suggestions I found here and elsewhere to no avail.

I was able to finally get my FSP sync'd with Windows 10 by downloading a previous version of Universal Control.

I hope this helps someone else.

Glad to hear you got it up and running! It seems ironic that the newer OS prefers the older UC.
I've run into similar problems with Firepods and my Firestudio 26x26 and various Win OS'.
In some cases I've tried several versions of UC before I found one that worked well with that
particular machine and/or OS.

I'll give the Older version of Universal Control a shot tonight,
and will follow up with results this eve.

tjcowhey wroteHi everyone. I was having this exact same issue. I tried a ton of the suggestions I found here and elsewhere to no avail.

I was able to finally get my FSP sync'd with Windows 10 by downloading a previous version of Universal Control.

I hope this helps someone else.

You absolutely did! Reverting from UC 1.7.4 to 1.7.2 Legacy did the trick. If you were local, I'd buy you a pint! Been fighting with this for a few days now. Thanks a million!

I am having the same problem. Everything worked fine until I upgraded as required. I have tried every version back to the VSL disc I got with my StudioLive 24.4.2. Technical Support cannot figure out what to them should be a simple driver issue. They have failed. I am taking them to court and get my money back and buy another product that works. I am disgusted with Presonus. When it works great, but it is always a bid "if". I have lost money because of this problem and have to work with a friend who has a Mackie setup that seems bulletproof. I have been duped and then ignored with this upgrade issue.