Part of this issue is related to driver type - ASIO, WAS, or MME.

WAS and MME can both operate in non-exclusive mode, and BB typically uses a resampler for any audio sent to it that doesn't match the driver. So the driver can be set to 48khz, 192khz, whatever, and BIAB can operate in 44,100 if it wants to. This typically works fine on any hardware that's set to at least 44,100hz, and I've personally tested that up to 192khz.

ASIO requires the hardware to synchronize to the software, and generally allows only one application to talk to the audio interface at a time. Most ASIO drivers work this way, with very few exceptions - for example the Focusrite driver currently allows multiple clients, though all clients must be set to the same sample rate. Currently BIAB requests a sample rate of 44.1khz when using ASIO and doesn't use a resampler - I'll ask the dev team to see if it's possible for BB to request a higher sample rate or use the resampler or something. This could potentially add latency, as the resampling process takes CPU time.

ASIO is a fairly old driver type - it was introduced in the 90's (1996 iirc). WAS was introduced with Windows Vista in 2007. If you're using multiple programs at the same time, you're much better off using WAS/WASAPI or MME (technically MME ports through WASAPI anyway).

*edit*

RealBand can already operate at 48k and 96k using ASIO, and you can select the sample rate from Options > Preferences > Audio > Audio File Type.

Last edited by Simon - PG Music; 05/12/21 01:39 PM.
I work here