4 posts
Page 1 of 1
|
Hi folks, any ideas please with the following? Have tried all of the FAQs I can find with no luck. many thanks, DennisB
System: HP Compaq 64 bit 2.4GHz E4600 Core 2 DUO, 4GB RAM Texas Instruments X10 2200A 1394A Firewire card Windows 10 Pro Problem: 1. Blue/red flashing Firewire status LED. 2. Unable to select clock or buffer in Universal Control (driver 0.0.0. dislayed in launcher). 3. Launcher/Settings/OHCI info does not find OHCI 1394 controller. (Firewire card was working OK before Presonus install with Yamaha n12 firewire mixer) Attempts to resolve: 1. Tried a 2nd 6 pin firewire cable - no change. 2. Downloaded a legacy 1394 OHCI driver from MSoft - no change. 3 Re-installed Launcher (ensuring legacy driver still selected) - no change. 4. Double checked Firewire card chip set is in Presonus compliant list - confirmed TI X10 220A. 5. Deleted all 1394 drivers and Presonus app/ files using Presonus Install and manual deletion of all %appdata% Presonsus files. 6. Reinstalled legacy OHCI 1394 driver and Universal control (r174) - no change. |
|
With me same problem. The latest driver is un-installable.
Win7 ultimate SP1 64 with platform update i7-2600K @ 3.40GHz 8GB RAM I tried all the other legacy drivers, included 1.1.1 what came with my firestudio mobile. With the 1.1.1 it didn't work. With all the others I hear random noises, as pieces of dust on vinil. Super enoying and unacceptable. For more than three! full days I tried to solve the problem with no success. I read all available info, workarounds, forums,... My firewirecard is on the compatibility list, I changed cable,...did everything possible. On another OS I run (the same but 32bit) driver version 3.5.2 8028 (1586) is installed and the soundcard works. Altough this driver is unfindable now. Now I think it´s up to Presonus to solve this problem. |
|
When mine had issues it is tricky. I have always got it back working. I have had to reboot between step. Manually remove Presonus drivers/dir, as they didn't seem to remove with the uninstall. On and on.
I somehow set it once for recording at 192 which took me a long time to get back. It would become unresponsive. Did you ever get it to sync? PS: My first FSM when pop and smoked out, DEAD. Some cheap cap blew Ithink. I didnt want to go USB so i stayed with another FSM. Maybe HW for the cracklin?
Win 10 latest, MSI G41 Z87, I4770K (no OC), 16GB, NVIDIA 710, 2x27" Monitors 1Tb SSD, 500G SSD, 3 platter drives. SYBA Firewire SD-PEX30009, FS Mobile. Monitor2USB, S1 Pro 5 current.
Hobbiest - Mainly Guitars, UVI, Soundtoys, NI, IK, EZ2, SD3, GR5, TH3, Amplitube 4 and 5, Waves GR, Korg 707, NanoPAD2, MicroKey2. Eris 5, B2031A, 2013 R1200GS-LC. |
|
Hey, if you get this working, can you tell me if you show the ZERO LATENCY little z in the start page or in a cue buss?
Win 10 latest, MSI G41 Z87, I4770K (no OC), 16GB, NVIDIA 710, 2x27" Monitors 1Tb SSD, 500G SSD, 3 platter drives. SYBA Firewire SD-PEX30009, FS Mobile. Monitor2USB, S1 Pro 5 current.
Hobbiest - Mainly Guitars, UVI, Soundtoys, NI, IK, EZ2, SD3, GR5, TH3, Amplitube 4 and 5, Waves GR, Korg 707, NanoPAD2, MicroKey2. Eris 5, B2031A, 2013 R1200GS-LC. |
4 posts
Page 1 of 1
Who is online
Users browsing this forum: No registered users and 4 guests