Wow I would have no respect for anyone who told me to use anything other than the correct ASIO driver from Focusrite. That's just plain bad advice and not helpful. 
 
But is seems CbB is not recognizing your interface properly. Windows updates sometimes trash Audio drivers so possibly try re installing the latest ASIO driver? 
Always use the same usb port too. 

sock monkey
Windows updates sometimes trash Audio drivers so possibly try re installing the latest ASIO driver? 

I concur about Windows updates sometimes trashing Audio drivers.  I personally tell Microsoft never to touch drivers, ever.

Here are the latest downloads for the Liquid Saffire 56


https://customer.focusrite.com/downloads?product=Liquid+Saffire+56
 

sock monkey
Wow I would have no respect for anyone who told me to use anything other than the correct ASIO driver from Focusrite. That's just plain bad advice and not helpful. 
 
But is seems CbB is not recognizing your interface properly. Windows updates sometimes trash Audio drivers so possibly try re installing the latest ASIO driver? 
Always use the same usb port too. 

My presumption was that they might know of an ASIO specific issue with the latest patch and were trying to ascertain if this was the case here.


I'll try re-installing the driver, but as SPLAT is still working fine, I suspect that this is not the issue. As it only happened after I installed the lastest update for CbB, I suspect it is something to do with that.

TheFitz

sock monkey
Wow I would have no respect for anyone who told me to use anything other than the correct ASIO driver from Focusrite. That's just plain bad advice and not helpful.
 
But is seems CbB is not recognizing your interface properly. Windows updates sometimes trash Audio drivers so possibly try re installing the latest ASIO driver?
Always use the same usb port too.

My presumption was that they might know of an ASIO specific issue with the latest patch and were trying to ascertain if this was the case here.

I'll try re-installing the driver, but as SPLAT is still working fine, I suspect that this is not the issue. As it only happened after I installed the lastest update for CbB, I suspect it is something to do with that.

I had a similar issue with my Focusrite 6i6 after one of the Windows 1803 updates. 
 
Sonar was working fine, CbB had audio issues. This was only on one of my PC's.
 
CbB is compiled using a newer version of Visual Studio, so it's using the newer C++ runtime (which may call the Windows API's in a different way under the hood).
 
I noticed that this PC was the only one that didn't have KB4340917 installed, so I installed it, re-installed my Focusrite driver, and everything was fine.
 
I don't know whether installing the update fixed it, or re-installing the driver did (or both!), but the Windows 1803 release has been pretty buggy, and several updates have been released to fix issues.
 
I'd check your Windows update history to see if you've any failed updates, and make sure they're installed.... then re-install your Focusrite drivers.
 

OK, I've reinstalled my focusrite driver and checked for windows updates of which there were none that had failed. I gave it a quick test and I now have sound again on CbB but it is running really slow! 2-3 second pause after hitting play and it is otherwise generally sluggish. (SPLAT still working fine).
 
I noticed there was a CbB update this morning and have installed it, but not had a chance to test it yet.

There was yet another update this morning, which I installed, and everything seems to be working fine again.

Hmm, curiouser and curiouser!
 
I'm having the same issue again but it seems to be related to the pro-channel. It is sporadic and doesn't seem to be related to the number of plugins or size of the project. I initially resolved it by bypassing the bus console emulator and then re-enabling it, but in another instance I had to remove and replace the console emulator. I have since had a few occasions where I could track it down to the EQ, a third party plugin or the pro-channel itself (when powered off/bypassed audio returns normally).
 
On the last occasion today it was the console emulator again but it would only work if you also changed the latency of the driver (doesn't matter if it is increased or decreased as long as it is changed) as well as bypassing and re-enabling the conswole emulator.