Page 1 of 1

Why are these drivers so awful?

Posted: Thu Jan 18, 2018 1:28 am
by axxessdenied
Seriously... can you guys get your stuff together?

I have the right cable.
I have the right firewire chipset.
I have the latest version of Universal Control installed that was released on Dec. 20, 2017.


The drivers don't seem to load properly into Windows half the time. Sometimes the unit works flawlessly. And, like right now... I can't open my DAW without any other app not being able to use my interface for sound. I can't open up the advanced options when I go to playback devices and properties for my firestudio project because it's not even there. Sometimes I can see it. That's when everything works beautifully.
Now, if I close my daw I don't get my system sound back.

I have to restart and unplug to try and get the device to resync. Or just restart my pc.


I'm thinking a better idea is to throw this unit in the trash and move on. Pretty unfortunate since it's a good unit when things work well. These issues are just getting in the way of my being productive. Productivity is the most valuable thing and anything that stands in the way is useless. So... what the hell do I do? I am NOT BUYING another cable. I've replaced those enough times already only for the same weird issues to persist.
I just want things to work. I can't see myself buying another Presonus interface if the drivers are not going to be up to par with the hardware.....

Re: Why are these drivers so awful?

Posted: Thu Jan 18, 2018 1:32 am
by axxessdenied
Here is what I get in the properties.
https://1drv.ms/i/s!Ap9wYDeGjliQg6ZXHZFOFV0MU5bUsA

No advanced panel is visible.


https://1drv.ms/i/s!Ap9wYDeGjliQg6ZYQRIa4RhSRIc46w

These are the latest drivers. I just checked against the release notes.

Re: Why are these drivers so awful?

Posted: Thu Jan 18, 2018 1:34 am
by axxessdenied
https://1drv.ms/i/s!Ap9wYDeGjliQg6ZZVs3NGWQLcOL9eQ
universal control acts like an application has control of it even though I don't have anything open.

Re: Why are these drivers so awful?

Posted: Thu Jan 18, 2018 1:58 am
by axxessdenied
Restarted.

Things are working as intended.

Except that now I have an insane amount of static and crackling on my inputs.

I had this problem before and it went away for a while. And, now it's back.



.... I just wanna make some music, man.

Re: Why are these drivers so awful?

Posted: Thu Jan 18, 2018 11:44 am
by axxessdenied
You know what... There is no point. I've gone from Windows 7 to 10 and it's been nothing but issues with the FSP. Time to retire this unit and give up on firewire completely in Windows 10 I think. I was up to 6:30 am last night and made zero progress lol. That's just money down the drain right there.

Re: Why are these drivers so awful?

Posted: Thu Jan 18, 2018 11:53 am
by matthewgorman
I have the right cable.
I have the right firewire chipset.
I have the latest version of Universal Control installed that was released on Dec. 20, 2017.


I can understand your frustration. We have all been there. But we need more detail to be able to help. I have helped many a user that told me they were on the most current version when they were not. The devil is in the details.

If you still want help, I need to ask that you list the actual version numbers, cable connections, firewire chip, OS processor info, etc etc.

FWIW, when working in a daw, it is by design that the daw takes total control of audio output. That behavior is normal and expected.

On the surface, your problem seems to be firewire related. That could be the card in the pc, the cable, or the jacks on the back of the FSP. Bear in mind, there are FW chips in the approved list that perform sporadically in certain environments.

Re: Why are these drivers so awful?

Posted: Thu Jan 18, 2018 2:11 pm
by Skip Jones
To Matt's point regarding info. Click on the hyperlink in my signature to create a signature of your own that has specs.

Kind Regards,
Skip

Re: Why are these drivers so awful?

Posted: Wed Jan 24, 2018 5:49 pm
by klypeman
I know this don't help much but I run 2 FP´s on my Win 10 64 bit system and it IS working :thumbup:
Best thing for you to do if the forum community has any chance to help you will be to add your signature (system, brand of firewire card, cable type (4 pin,6 pin ?) ect. ect. then people in here have a much better understanding of your particular problem and hopefully able to help better ;)

Re: Why are these drivers so awful?

Posted: Tue Jan 30, 2018 10:47 pm
by Occam's Razor
axxessdenied wrote

I'm thinking a better idea is to throw this unit in the trash and move on. Pretty unfortunate since it's a good unit when things work well. These issues are just getting in the way of my being productive. Productivity is the most valuable thing and anything that stands in the way is useless. So... what the hell do I do? I am NOT BUYING another cable. I've replaced those enough times already only for the same weird issues to persist.
I just want things to work. I can't see myself buying another Presonus interface if the drivers are not going to be up to par with the hardware.....


I know, I posted an extremely detailed thread of what I have done and tried to get this stupid thing working, and I got nothing.
The best I have right now is my FSP works, but all the options in the Launcher are greyed out, and the Launcher does NOT detect my new OHcCI card, but the newest version of the OCHI Tool DOES.

I've written to Presonus Tech Support telling them in my very first Sentence that I own a Presonus Firestudio Project 10x10, and Tech support replied telling me they don't support the Firestudio 26x26

They can't even be arsed to read my tech question, asnd instead respond telling me an entirely different model than the one I asked about is not supported.

My thread compiled each and every troubleshooting step that I pieced together throughout the forums and still no luck, I guess I'll have to live with the semi-functioning drivers and Launcher.

This is definitely my first and last Presonus Purchase though.

Re: Why are these drivers so awful?

Posted: Sat Feb 10, 2018 10:08 am
by axxessdenied
matthewgorman wrote
I have the right cable.
I have the right firewire chipset.
I have the latest version of Universal Control installed that was released on Dec. 20, 2017.


I can understand your frustration. We have all been there. But we need more detail to be able to help. I have helped many a user that told me they were on the most current version when they were not. The devil is in the details.

If you still want help, I need to ask that you list the actual version numbers, cable connections, firewire chip, OS processor info, etc etc.

FWIW, when working in a daw, it is by design that the daw takes total control of audio output. That behavior is normal and expected.

On the surface, your problem seems to be firewire related. That could be the card in the pc, the cable, or the jacks on the back of the FSP. Bear in mind, there are FW chips in the approved list that perform sporadically in certain environments.
I traded in two guitars for an RME Babyface Pro and have zero issues now. I'm pretty sure Windows 10 doesn't have the proper driver support anymore for legacy firewire drivers. You can't even install the old legacy drivers in the current version of windows.

Re: Why are these drivers so awful?

Posted: Sat Feb 10, 2018 11:40 am
by klypeman
Let's stay on facts. I got two Firestudio Projects up and running right in front of me.
Win 10 64bit Home.
If you look in this thread, you will see a link how to add your signatur.
As it is now it sounds as you are guessing and that is not good for anyone.

Re: Why are these drivers so awful?

Posted: Sat Feb 10, 2018 9:15 pm
by axxessdenied
The Babyface Pro I got works much better than the firestudio was for me. So, I am not going to bother troubleshooting anymore. I've been through multiple PCs all the way from Windows 7 to 10 with the FSP and it's always had intermittent issues. Not really interested in putting anymore time into troubleshooting what should be working after trying different firewire chipsets and cables and not being able to come to some kind of long-term resolution.