M and Gordon.
i use an audient interface with multiclient driver ...nary a prob in any music app.
i set it to 48k asio. nope.no go...it gets reset to 44.1k.
so Mr M same prob here....i get a bb message... 44.1 fine.
Mr M...you asked why in bb asio 48k is listed at bottom.
same here BUT i believe that asio dialog just lists the interface/driver capabilities.
i may be wrong but it doesnt necessarily mean that bb can utilise 48k ?
now heres a 'likkle wrinkle' ...and i might be out to lunch as i use only 44.1 whether bb or rb or reaps v2 that i also use...
in my dim getting older memory did someone mention once 48 k can be used in rb ?
but maybe i'm wrong.
i'm busy with songs right ...and dont wanna muck around with my settings...
but if your feeling bold Mr M see if you get the same 48k prob in rb.
i would be curious.
i feel on this pg site...a memo/sticky re this issue be issued as i'm sure this is gonna crop up again..
particularly with new users i guess.
happiness.
om
OK, I switched BiaB to WAS (always) audio. Now, my ASIO driver remains at 48K, and BiaB uses 48K for both Input and Output audio, even though audio output is going to the monitors connected to my RME audio interface. [shrug]
I don't understand, but I'm happy now! Thanks everyone!
P.S. I don't even install RealBand. Since I use Bitwig and Studio One, both of which support the BiaB plugin, I don't need it. Also, I'd been using Reaper for over 10 years, but I hadn't even opened it since getting Bitwig 5, so I uninstalled it. Was installing Reaper completely as simple and easy as installing it? Nope. It took me over 30 minutes just to clean up all of the Reaper entries in the Windows Registry. Over 30 freaking minutes! Unbelievable. There were entries for every single update to Reaper since the first version of v4 that I installed. And I was on the latest version of Reaper 7 when I uninstalled it. Lordy, but that was time-consuming and irritating.