• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

v8.0.0 Bug: Unable to Deselect 'Recording Device'

TheNeil

New member
Hi all,

I first mentioned this bug on the discussion thread for 8.0.0, but as it still persists in 8.0.1, I'm making a thread for it.

I can no longer select 'No Audio Device' for 'Recording Device' in Audio Setup (that's Recording Device, not Playback Device, in case anyone's confused). It's still present in the drop-down, but if I try selecting it, the app just glitches for a second, then goes back to whatever was selected before.

Would be great to see this fixed, because the app's constantly accessing my built-in microphone when I've not got a recording interface connected. That's a waste of processing, and macOS complains about it too. Whenever I'm mixing, mastering, using VIs, or whatever, I'm used to keeping Recording device off entirely, but that's broken since I upgraded to FS Pro.

I'm currently on Studio Pro v8.0.1, macOS 26.2. No external audio devices currently connected (Steam Link's 'Steam Streaming' software Mic & Speakers are the only other options aside from my machine's built-in mic & speakers).

Thanks.

No Recording Device.png
 
For reference, this is not happening with Win10
 
Not happening in Windows 11 either
You need a Mac user to validate this next...
 
That looks to be for Fender/PreSonus hardware. I'm just using FS Pro mostly without a recording interface. When I do need to record guitar or vocals, I just plug in my Motu M4; but that's rare compared to how often I'm using it software only.
 
Universal Control *may* be supplying that null device to select, hence my suggestion.
 
This happens with Fender Studio Pro 8.0.1 in macOS Sonoma 14.7.2 . . . :oops:

There is a workaround, but since describing and explaining it requires another of my AI Robot treatises, I put it in the Lounge.

 
Last edited:
Universal Control *may* be supplying that null device to select, hence my suggestion.
Thanks for the suggestion, but it wasn't required in the past - never had this installed - so I'm hoping to see a fix for this bug, rather than having to rely on secondary software which is otherwise not relevant.
 
Back
Top