Hi Audio
 
This started happening after the first time that script error kept coming upthat everyone mentions
I started Bandlab up tonight and soon as i got to a basic load screen ,a message comes up saying it does not recognize my Focusrite 6i6 drivers and it was hard to see as  the message box kept flickering and also making popping noises as It flicks.
I have been working on a song In Cubase as that Is solid and was wondering about some fx plugs that I could do with that Is not in cubase.
Fired Bandlab up and this problem starts.
I had to go to task manager to shut Bandlab down.
I managed to get to the preferences and had to recheck all the focusrite drivers again.
Fired up Bandlab again and the flickering and noise starts again
I have a fast up to date machine and no problem with cubase.
Something is buggy In there.
I have uninstalled and re-installed ,but the same thing happens every time.
If Cubase works ,so should Bandlab!!!
Cubase is flawless for me
 
 
All the best
john

Hi I will check on the focusrite site to see if there are any driver updates ,but my 6i6 never fails me until Bandlab.
 
 
Just checked and My 6i6 still has the same control panel .

It's cute but given time and it's going to seem as silly as to whoever said no to "Hey lets...." before.
After what, 4 days. It's getting to look kinda "gay" in the 80s dorky sense of the word.
 

To gripe about the toast screen is petty, really.  I could see it if it slowed up the load time, but it doesn't seem to (at least for me) and could, as Noel suggests, give you a hint to where trouble is if you run into a load error.  Besides, it's cute.  Lighten up!
 
JB

igiwigi
Anyone like me having grief with this program.

Nope!  CbB run fine here with my 2nd Gen Focusrite 2i2 on a fully patched Windows 10 Pro machine.  Every CbB update has been fine.

promidi

igiwigi
Anyone like me having grief with this program.

Nope!  CbB run fine here with my 2nd Gen Focusrite 2i2 on a fully patched Windows 10 Pro machine.  Every CbB update has been fine.

It was a conflict with the Cubase Generic Low Latency Driver http://forum.cakewalk.com/FindPost/3775572
 

But if you're ever having troubles that will quickly become a mock.

Hidden_Symmetry
Do you really stare at it when the projects are loading up?
I'm hoping it will come in handy if & when a project won't open. It might give an indication as to what plugin isn't loading properly. Not sure if it operates that way but it would be great if it did.

 
Not bothered by the toast, but in ref to above, it doesn't appear to be of any real help if you have a plugin misbehaving. I know firsthand.
Clean Win10 install, just got all plugins, softsynths, DAWs up and running. All Cakewalk projects were starting through their load-ins and POOF....CWBL just closes with no error, no communication as to what went wrong. There wasn't info ( or it's too fast??) to glean any insights.
 
For the record, I did the "shift +start" on a test project and restricted plugins until I found an offending Breverb2 by Cakewalk. Something was choking everytime it hit that. Reinstalled, bypassed on all current projects and reinserted the new version of Breverb and all is well...... ( only left all that info for some other soul who runs into that). Toast screen didn't signal there was an issue.
 
Anyway...toast screen: OK, doesn't bother me, but not sure you'll ever lean on it for troubleshooting from my anecdotal evidence.
 

You could screencap the toasts and would see the last plugin that it tried to load load before it crashed. But point taken that the info flies by very quick. The ability to capture that to a log would be useful in the future.

I would like to see the toast info written out to the project folder to use as a manifest; preferably in a human readable tagged format. Maybe even containing preset data formatted in a way that could be imported by the Preset Manager.