Originally Posted by Noel96
The most usual cause of ASIO/WAS not working is because another program is that hooks up to audio is open (say something Media Player, a DAW such as Reaper, etc.). Often ASIO only works with one program at a time.
Correct - for this reason I always recommend either WAS or MME, and only switching to ASIO for recording.

Originally Posted by Noel96
By the way, MME is fine. That's what I use. The quality of the sound is identical whichever audio driver is used. The only time I use ASIO/WAS is if I am recording directly into BIAB as those two audio driver reduce latency and help the recording input and BIAB synchronise.
This is correct. The only additional difference between ASIO and the others is that ASIO bypasses the Windows Audio stack, meaning that if you have any bass or treble controls or spatial audio enabled in Windows, ASIO will bypass those.

Originally Posted by Melody_Maker
I was finally able to identify the source of my problem and fix it :

For ASIO or WAS to work straight away when Bb is launched, the CoyoteWT DXi instrument package needs to be installed on the system even if the song uses no MIDI but only realtracks.
However, during Bb 2024 installation, a "Coyote WaveTable DXi Synth" checkbox appears as optional, which may be misleading.

So, as soon as I installed CoyoteWT, ASIO or WAS audio output started working properly again. (Installer source in C:\Bb\Data\Installers\SetupCoyoteWT13.exe)
What did you have selected as the MIDI Output driver? If it was set to none, that can cause the playback to fail in some cases. CoyoteWT is not required for playback to work, from my testing. Either way, as you've found a solution I'm going to mark this thread as resolved.

Originally Posted by Redshawn66
I found the only solution was to create a new BIAB Song file, and Copy & Paste everything from the old file, and it works okay now; its as if the file becomes corrupted somehow.
That's quite possible - we occasionally have customers send us files that are corrupted. It's never been something we've been able to duplicate, so our assumption is that it might be either a problem specific to the computer or a weird one-time glitch.

Originally Posted by Redshawn66
I think 1951 was the first computer, and so much has evolved since then. If I had a quid for every hour lost due to computer problems over my life…… Really, they’re still in the experimental stages, and are very technical, one tiny configuration issue can create all sorts of issues.
Precisely! As amazing as computers these days can be, it's not hard to forget how easily the castle can crumble.

I work here