CbB - No audio output

Hi All,
 
I recently updated to CbB after using SPLAT for my main DAW and in general I'm quite happy with it. However, the last week or so I've started developing problems. I loaded into a project I was working on and when I hit play there was a faint click but no audio but the audio engine did not report a dropout. I resolved it by changing the latency setting.
 
Another day, I solo'd a track and when I went to listen back to the rest of the project I had the same problem as before except the track I had solo'd was still audible (and yea I'd taken it off solo and nothing else was muted or solo'd). Changing the latency did not fix it this time but a re-start did.
 
I have now had another issue the same as the first example. Changing the latency and multiple re-starts failed to resolve it. All the meters are showing signal and the audio engine does not drop out. On a whim I decided to try SPLAT and it fired up fine first time. Returned to CbB same problem. Back to SPLAT - fine.
 
Ok so I'm back to SPLAT for now, but any idea what might be the problem? All settings are the same in both.
 
I'm on Windows 10, intel i7920, 8GB RAM, Focusrite Liquid saffire 56. HDD's aren't full, RAM is at 20% ish usage, CPU basically at idle.

brundlefly
Maybe try replacing CbB's AUD.INI with SPLAT's, and if it fixes the problem compare the two files.

Do they not share an AUD.ini? I can't seem to find a seperate version for CbB

Thanks. I had a look at them both and they appear to be identical

What happens if you exit CbB, rename its AUD.ini file (to something like AUD.ini_bak), then reopen CbB.  CbB will profile your system and rebuild your CbB AUD.ini file.

TheFitz
Ok, tried this and CbB loaded up with a non existent interface set in inputs/outputs. Changed it back to my current interface and this resulted in an audio engine dropout followed by a crash. Fortunately SPLAT is still stable!

That's definitely not normal behaviour. 

I never had that issue when I changed from Platinum to CbB.  It's probably something on your system that CbB does not like.  Of course you have installed all updates and driver updates for all hardware.

Have you tried contacting Bandlab support?

https://help.cakewalk.com/hc/en-us/requests/new

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
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.

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.

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.