We can contact presonus if you are unable to get any information from their support on this matter. I don't have this device to test so I can only speculate to the cause. I would consider this to be a bug in the presonus driver. Ive uninstalled the software and hardware, restarted, reinstalled without success. This is because that software could be 'locking' your PreSonus hardwares settings, disallowing you to change configuration to reflect your setup in Pro Tools.
#Asio presonus firestudio driver drivers#
W10, PreSonus Firestudio, last drivers from 2017. If another piece of audio software on the computer is open and has acquired the driver for your interface, you may need to close that software in order for this fix to work. That would cause us to call ASIOSetSampleRate to 96K. After years of stable operation I now find my ASIO samplerate and buffer size changing when I launch reaper, but not to the values I have set. The presonus driver itself is reporting its sample rate as 96K to Cakewalk even though its not set to 96K. You have another driver that references the same PreSonus ASIO device that is internally reporting 96K and setting the presonus indirectly to 96K.ĭo you have the Steinberg generic audio driver or something else like that installed? If so that could be the cause.Ģ. The only way I can see this process setting the sample rate of the driver to something else is:ġ. Power off your PreSonus FireStudio interface or StudioLive mixer. When Cakewalk starts up it goes through a small validation process for all drivers on the system to build the list of available devices.Īs part of this process it sets the sample rate of each driver to the SAME sample rate that the driver reports to us. Although there are ASIO drivers and some of our class compliant devices may work on. Note that I'm not opening any project at this point.
0 kommentar(er)
