Hi There
Just updated Presonus Studio One to 3.1.
It kept failing to load SCOPE ASIO.
Eventually I ran it in Compatibility Mode Win 8 and away it went.
Has anyone else had this issue?
maus
Presonus Update Scope Compatibility
Re: Presonus Update Scope Compatibility
Did you get any error messages on why it failed to "load Scope ASIO"?
Might it have been querying what Audio Rates the Scope ASIO driver supported? Maybe it tried to set an Audio Rate that Scope ASIO didn't like?
What was the behaviour of the DAW iteslf? Did it hang and quit, just hang, or launch the app OK but you couldn't present the Audio Preferences page (where you might select Audio driver), or you couldn't select Scope ASIO? Was Presonus Studio One 3.0 OK?
There's a known issue around apps that use Portaudio library with the Scope ASIO driver installed...
I'm hopeful to get to the bottom of the issue - my progress is slow...
I don't think Presonus Studio One uses Portaudio.. And, while I don't use Win8, using Compatibility Mode in Win7 doesn't solve the Scope ASIO issue in Portaudio apps... But I'm asking these questions in case we get something more out of Studio One in terms of error logs, compared what the portaudio library build itself seems to produce (i.e. no error logging at all, no sniff of what calls portaudio makes to the ASIO driver that exposes itself to hang-fails when querying/using Scope ASIO).
Might it have been querying what Audio Rates the Scope ASIO driver supported? Maybe it tried to set an Audio Rate that Scope ASIO didn't like?
What was the behaviour of the DAW iteslf? Did it hang and quit, just hang, or launch the app OK but you couldn't present the Audio Preferences page (where you might select Audio driver), or you couldn't select Scope ASIO? Was Presonus Studio One 3.0 OK?
There's a known issue around apps that use Portaudio library with the Scope ASIO driver installed...
I'm hopeful to get to the bottom of the issue - my progress is slow...
I don't think Presonus Studio One uses Portaudio.. And, while I don't use Win8, using Compatibility Mode in Win7 doesn't solve the Scope ASIO issue in Portaudio apps... But I'm asking these questions in case we get something more out of Studio One in terms of error logs, compared what the portaudio library build itself seems to produce (i.e. no error logging at all, no sniff of what calls portaudio makes to the ASIO driver that exposes itself to hang-fails when querying/using Scope ASIO).
Not because it is easy, but because it is hard...
Re: Presonus Update Scope Compatibility
Sorry I was a little brief with my earlier post.
I am using Windows 10 64Bit with XITE-1 and Scope 5.xx
I am pretty sure that presonus don't use portaudio, but now you mention it, I did load portaudio to see what it did (which for me was pretty much nothing).
I was hoping for more network connectivity flexibility.
When I am back in the studio I might uninstall it and see if it was part of the problem.
@eanna
Studio 1 just gave me an error message. It would load but then told me there was no audio outputs and I had to select another audio output source.
Once I ran it in compatibility mode it was fine and happy with scope.
I am using Windows 10 64Bit with XITE-1 and Scope 5.xx
I am pretty sure that presonus don't use portaudio, but now you mention it, I did load portaudio to see what it did (which for me was pretty much nothing).
I was hoping for more network connectivity flexibility.
When I am back in the studio I might uninstall it and see if it was part of the problem.
@eanna
Studio 1 just gave me an error message. It would load but then told me there was no audio outputs and I had to select another audio output source.
Once I ran it in compatibility mode it was fine and happy with scope.
Re: Presonus Update Scope Compatibility
For what its worth, I uninstalled Jack 1.9.10_64, but that didn't fix the problem.
It still works in Win 8 compatibility mode.
maus
It still works in Win 8 compatibility mode.
maus
Re: Presonus Update Scope Compatibility
Looks more like a win 10 compatibility issue than a studio one v3 issue ?
I don't see why Studio one would change its driver recognition between v 2 and v3.
Win 10 on the other hand... it happenned before ...
I do not know though, I would like to know though
I don't see why Studio one would change its driver recognition between v 2 and v3.
Win 10 on the other hand... it happenned before ...
I do not know though, I would like to know though
Re: Presonus Update Scope Compatibility
other ASIO apps work properly in win10...