Greetings,
Studio One Pro V3 says that it cannot initial the FireStudio Project when I select it in the configure menu. I am using a Dell laptop with a built-in FireWire port, with a clean install of Windows 10. I am running the latest version of Studio One Pro V3 and Universal Controller. Sorry I didn't provide version numbers but I just downloaded them from Personus last night. The light on the FSP when powered on turns red then blue for a moment and then back to red. Studio One Pro and Universal Controller can see the FSP. So everything appears to be working except Studio One can't initialize the FSP. Any help would be greatly appreciated. Rick... |
The light on the FSP when powered on turns red then blue for a moment and then back to red. Its not syncing. When the FSP is synced to the pc, the light is solid blue. red means no sync. Back in the Win 7 days (and maybe 8 but I wasn't on that train), there was a fix that may be worth a try. Go into the PC control panel/device manager. Find the IEE 1394 device (firewire port), rt click that for detail. Then on the drivers tab, it lists available drivers. If you see legacy as an option, switch to that and see if it helps sync. Otherwise, it sounds like its possible that the firmware did not load correctly. Run the uninstaller for UC 1.8, then reinstall. On the reinstall, make sure that anti virus is off if applicable. Then also make sure that on the driver selection page, that the firestudio driver is selected for install. After years of never having to deal with things like this, Win 10 has changed a few things for me too. I never had to turn off av, now I do. Things like that. Good times. One other situation I have encountered, and it may help you. Doing a selective driver install, I have had device sync issues. If your first attempt at installing 1.8 was just installing the FSP driver, try to install all drivers for firestudio, audiobox, etc. For some reason that cleared it up on my system. No harm in doing this other than the odd Audiobox would not initialize message or similar. That just means that a driver was installed, and the device is not connected to the pc. |
Not a problem. If none of those things work, I recommend a support ticket. I am leaving for vacation for 2 weeks, so I probably won't be responding at that time. Didn't want to leave you hanging.
|
Here's an update.
I did try some of the suggestions above, but no luck. After doing some more research, I found that Presonus provides a list of Firewire/1394 host controller chipsets that are not compatible with their products. As it turns out, the 1394 host controller chipset in my laptop is not compatible. The chipset built in to my Dell Studio XPS laptop is made by Ricoh, and Ricoh is listed as one of the worst. In fact, all the Ricoh chipsets are on the incompatible list. Lucky me! Rick |
I don't know if your Dell has a pc express card slot, but my Dell Lattitude E6410 does. I use a TI based card as my machine had the crappy onboard Ricoh chipset too.
https://soundcloud.com/cristofe-chabot/sets/main
PC'S: HP XW6000 Dual 3.2GHz Intel Xeon, 8GB RAM WinXP SP2 HP 6005 Pro AMD Athalon X2 B24 3.0Ghz, 4GB RAM Win8 Pro Dell Latitude E6410 Laptop Intel i5 2.67Ghz 8GB RAM Win7 Pro x64 Audio Interfaces: Terratec EWS88MT PCI (2), Audiobox 1818VSL USB & Firestudio 26x26 Firewire, Line 6 PodXT, Roland GS-10, NI Rig Kontrol 3 Monitors: Yamaha HS50M's DAW: S1 3.2.1 Pro To add your software and hardware specs to your signature to make it easier for us to help you, click HERE. |
Just for the heads up.
DId you guys try the legacy 1394 drivers? https://www.studio1productions.com/Arti ... wire-1.htm |
Users browsing this forum: No registered users and 6 guests