PreSonus Forums

Hi all.
Some updates.
Given that i still think that Quantum's driver should be improved to circumvent Win7/10 problems (my RME works perfectly as a multiclient audio and MIDI device), i tried some tricks that may help Presonus to spot the problem.

This trick "improve" the multiclient audio support but not the MIDI multiclient support.

Go to "Services" and look for "PreSonus Hardware Access Service" under the "Standard" tab.
Under the "Startup Type" column right click and go on "Properties" and set the Startup type as "Automatic (Delayed Start)".

With this option i have multiclient audio operations working most of the times. Only one time i got a problem about Quantum not being seen by the system, but after a Win reboot everything went fine.

The MIDI multiclient problem is NOT solved by this so is still a issue to be spotted out.

On xmas break, was able to just now test the above suggestion, I followed it to a T,and it still doesn't work.

PreSonus fix this bug!

I have a Quantum and the sound falls out when I'm playing a youtube video and at the same time open my DAW. But the sounds comes back after seconds so I don't see the "big" problem. Does any other driver manage to do this?

TerjeNorway wroteI have a Quantum and the sound falls out when I'm playing a youtube video and at the same time open my DAW. But the sounds comes back after seconds so I don't see the "big" problem. Does any other driver manage to do this?

RME drivers work perfectly.
Presonus needs definitely to fix this bug. Quantum's drivers are unstable when multiclient operations are needed. 9 out of 10 times multiclient operations don't work. They get stucked at 48kHz for example even if try to set it to 44.1...and they works on a app only at a time.
Please Presonus fix this.

Thank you for confirming this!! Presonus is most definitely aware of this bug.

So let's hope for a fix soon!

I think this is fixed now with the Universal_Control_v2_10_0_50756 2.10.0.50756 driver update. At least my youtube sound does not disappear when I open my DAW at the same time

Hey thanks, Can anyone else confirm this is fixed now?

jonhamilton2 wroteHey thanks, Can anyone else confirm this is fixed now?

Well, sort of.
Most of the times i start my Win10 machine Presonus Quantum doesn't work wither as a system audio device and as ASIO device in my DAW.
I have to restart the whole system and then everything works.
This happens 99% of times.
But i don't know why. At least multiclient audio features seems more stable than before.

For what is worth I have a similar problem on OSX.
Support has been unsatisfactory and confusing to say the least.

It's probably badly written drivers...

aero3 wroteFor what is worth I have a similar problem on OSX.
Support has been unsatisfactory and confusing to say the least.

It's probably badly written drivers...

One problem with that statement cause OSX uses it's own audio drivers; Core Audio. Or do you mean OSX has bad audio drivers?

Hi all, while stuck in my home studio another little free time to make some tests.
I reported few weeks ago another run..
viewtopic.php?p=223489#p223489

Now i've adbandoned the use of things like ASIOLink o VoiceMeeter Potato on my desktop machine because Presonus Quantum refuses to work as expected in a multiclient enviroment (either does not work as ASIO multiclient). I just use my Quantum as pure ASIO interface for my DAW (mostly Reaper and Ableton Live) and connected to my Monitor Station V2 the Soundblaster card via Optical out to a SPDIF converter and finally to the SPDIF in of Monitor Station.

i've totally disabled the Presonus as a system audio device and guess what....problems.
Everytime i start my Win10 64bit machine Quantum is set at 48kHz sample rate. Even if it was shut down at 44.1.
1 times out of 2 if i try to put it at 44.1 it returns suddenly at 48. When this behavior is shown no ASIO app will be able to start because of some kind of ASIO error. I have to restart the system one or two times and things go right.

Well i'd expect at least some word from Presonus that...is totally silent.
Very bad support i must say.
I ask myself what this forum is for or the support section is for...no interaction most of the times...no replies.
Probably my plan to expand to Quantum 4848 will sadly gonna change
Very good hardware quality, bad software/driver quality, bad support.

alfonsosantimone wroteHi all, while stuck in my home studio another little free time to make some tests.
I reported few weeks ago another run..
viewtopic.php?p=223489#p223489

Now i've adbandoned the use of things like ASIOLink o VoiceMeeter Potato on my desktop machine because Presonus Quantum refuses to work as expected in a multiclient enviroment (either does not work as ASIO multiclient). I just use my Quantum as pure ASIO interface for my DAW (mostly Reaper and Ableton Live) and connected to my Monitor Station V2 the Soundblaster card via Optical out to a SPDIF converter and finally to the SPDIF in of Monitor Station.

i've totally disabled the Presonus as a system audio device and guess what....problems.
Everytime i start my Win10 64bit machine Quantum is set at 48kHz sample rate. Even if it was shut down at 44.1.
1 times out of 2 if i try to put it at 44.1 it returns suddenly at 48. When this behavior is shown no ASIO app will be able to start because of some kind of ASIO error. I have to restart the system one or two times and things go right.

Well i'd expect at least some word from Presonus that...is totally silent.
Very bad support i must say.
I ask myself what this forum is for or the support section is for...no interaction most of the times...no replies.
Probably my plan to expand to Quantum 4848 will sadly gonna change
Very good hardware quality, bad software/driver quality, bad support.

Just a note- this is a Community Support forum. It’s rare that someone from Presonus actually chimes in on posts here. They have a whole actual support system with Tickets and staff under the Presonus Knowledge Base.

robertgray3 wrote
Just a note- this is a Community Support forum. It’s rare that someone from Presonus actually chimes in on posts here. They have a whole actual support system with Tickets and staff under the Presonus Knowledge Base.

Thanks. But several times i've got no answer via the ticket system...or just answers sounded lik...."Is like it is"....
I'll try again...

I've just add a ticket...let's see what they say.

alfonsosantimone wrote

robertgray3 wrote
Just a note- this is a Community Support forum. It’s rare that someone from Presonus actually chimes in on posts here. They have a whole actual support system with Tickets and staff under the Presonus Knowledge Base.

Thanks. But several times i've got no answer via the ticket system...or just answers sounded lik...."Is like it is"....
I'll try again...

Ok, hopefully you get somewhere with it but from my experience if Support views it as an expected function or limitation than it truly is what it is and discussing it in the forum, outside of a few very rare cases, won't do much. Honestly imo the forum here is for questions where you know something is possible but cant quite figure it out on your own and want to talk to other users.

For example (hypothetically) you saw somebody do something in a youtube tutorial but that same action doesnt work on your computer- in the forum here somebody will point out that your settings need to be adjusted, which you may or may not have known- stuff like that is where the forum here helps.

alfonsosantimone wrote
i've totally disabled the Presonus as a system audio device and guess what....problems.
Everytime i start my Win10 64bit machine Quantum is set at 48kHz sample rate. Even if it was shut down at 44.1.
1 times out of 2 if i try to put it at 44.1 it returns suddenly at 48. When this behavior is shown no ASIO app will be able to start because of some kind of ASIO error. I have to restart the system one or two times and things go right.

.

have you tried to force a firmware update? I think the device have to reset then. Also reinstall Universal control to be sure

Try to start a song in 44.1 kHz 16bit, that did the trick for me once with Apollo Twin and Windows 10.

TerjeNorway wrote

alfonsosantimone wrote
have you tried to force a firmware update? I think the device have to reset then. Also reinstall Universal control to be sure

Yes. No solution for my problem tho. I updated several time firmware and universal control (i have latest version of both)...but same problems.

klypeman wroteTry to start a song in 44.1 kHz 16bit, that did the trick for me once with Apollo Twin and Windows 10.

Thanks for the hints guys but nothing solves that problem. Even starting a DAW is pratically impossible whent that problem occurs...i.e. Reaper just kind of freeze....Anyway Apollo is not Presonus so i guess different drivers, different problems.