Page 1 of 1

FW mobile problem with Windows 10

Posted: Sun May 31, 2020 4:59 pm
by wagnerpinheiro4
My interface was working fine I would turn on the computer and it was always connected and running smooth.
I changed my main hardrive to a SSD M2 and I did clone my previous hardrive with the OS.
After I did that when I turn on my computer the windows is loading and I see that my interface syncs with the PC. Problem is that if I don't open any audio on the computer right away and leave it running the interface will disconnect the and the red and blue light will start to blink.
If I open anything that has audio and leave it running the interface won't lose connection but problem is when I open my Studio One 4 all the windows audio doesn't work anymore and then if I take 1 to 3 minutes to use the interface it will disconnect from windows again and I have to reboot my computer to sync.
Anyone having the issue?

Re: FW mobile problem with Windows 10

Posted: Mon Jun 01, 2020 9:19 am
by klypeman
One thing I did if my Project did not sync was to go to the UC and change the sync to spdif and back to get to Project to behave again and the led to turn blue again.

Re: FW mobile problem with Windows 10

Posted: Tue Jun 02, 2020 1:48 pm
by MarkusHassold
Maybe you should reinstall the driver.

Re: FW mobile problem with Windows 10

Posted: Thu Jun 04, 2020 8:26 am
by wagnerpinheiro4
klypeman wroteOne thing I did if my Project did not sync was to go to the UC and change the sync to spdif and back to get to Project to behave again and the led to turn blue again.


That's the thing once the interface gets out of sync the UC doesn't behave well any change I try to make it there a message shows up and then I can't do anything but close the software.

Re: FW mobile problem with Windows 10

Posted: Thu Jun 04, 2020 8:27 am
by wagnerpinheiro4
MarkusHassold wroteMaybe you should reinstall the driver.


Done that several times and even replaced the Firewire card since I have 2 working at home. Either way both cards are installed fine and the same thing happens with both of them now.

Re: FW mobile problem with Windows 10

Posted: Tue Jun 16, 2020 9:35 pm
by wagnerpinheiro4
Well I actually got it back working normally.
What I did was I opened the Presonus software then on the settings window there's an option to perform a factory reset on the unit.
I did that then I had to reboot to sync and it is working fine now.
Hope this post can help someone else as well.

Re: FW mobile problem with Windows 10

Posted: Wed Jun 17, 2020 1:41 am
by klypeman
:thumbup:

Re: FW mobile problem with Windows 10

Posted: Wed Jun 17, 2020 11:10 am
by cristofe
Thanks for sharing your fix. I'm also running an FSM and several FS 26x26's on Win10.
I initially had troubles getting them to play nice with that OS. But all is good now.

Re: FW mobile problem with Windows 10

Posted: Fri Oct 21, 2022 4:39 pm
by BrentZen
Nice to see a few of us left using the FSM's, I have issues with my UC 1.7.6 and Windows 10 Pro Ver 21H1 on a PCAudioLabs unit I have had since 2013. I recently upgraded my hard drives and added some RAM and added a GeForce Graphics Card so that I could Collaborate using Sessionwire. But I don't think that is related to my problem. I am using 2 FSM's daisy chained for 16 inputs that I use with my XENYX X222USB Mixing Board. My DAW is Studio One Pro ver 5 and I have some control over the UC from the DAW but once I close Studio One I get intermittent disconnect from the FSM's and after a few minutes the SampleRate will lock in and all the controls grey out and I am locked out to make any Clock changes. All the other settings like WDM and such are working but no access to the Clock setting SampleRate: Clock Source: Safe Mode: or Buffer Size: Similar issue on start up until I open an Audio source like YouTube then the UC locks at a SampleRate: and I am locked out. My motherboard is older and I do not believe I have Standard hardware security supported in this unit. I am considering doing an Uninstall of UC and a factory reset but before I take that step I thought I would see if anyone else has run into this and found a simple fix. Sad that they stopped supporting this product I am coming up on 10 years you would think that they would want to market the hell out of that kind of reliability and longevity.