Johnny Penk Posted December 3, 2023 Share Posted December 3, 2023 Why do I need to shut down Bandlab in the task manager after Xing out of Bandlab to bring it back up again…. When I’m done with a project and x out of Bandlab then if I want to bring it up again, I have to go into task manager and “end process” then I can open it again. This is definitely a bug. Please fix this, thank you Link to comment Share on other sites More sharing options...
Byron Dickens Posted December 3, 2023 Share Posted December 3, 2023 You talking about BandLab or Cakewalk? Assuming Cakewalk, what audio interface do you have? If anything its might be a bug in the driver. When audio drivers go wacky, this can happen. Doubtful it is Cakewalk's fault or the forum would be on fire. I know I don't have that issue. 1 Link to comment Share on other sites More sharing options...
OutrageProductions Posted December 3, 2023 Share Posted December 3, 2023 (edited) This is most likely related to a hang in the drivers for your Audio interface. You can look for updated drivers, or cycle power (ie: disconnect) it for a few moments to pin this down. If you save & close the project session first, then close CbB, does it still hang? Edited December 3, 2023 by OutrageProductions 3 Link to comment Share on other sites More sharing options...
sjoens Posted December 3, 2023 Share Posted December 3, 2023 (edited) Ongoing issue here, even with empty (no) projects. Only TM doesn't work when CbB is dumped into Background Processes. I also have to force the system off (hold the power button) for it to shut down properly. Will try using TM to End Task for the audio interface next time... which will be soon. Edited December 3, 2023 by sjoens Link to comment Share on other sites More sharing options...
sjoens Posted December 3, 2023 Share Posted December 3, 2023 And soon, it was. But ending the interface process in TM did nothing to release CbB from Background Processes. Link to comment Share on other sites More sharing options...
OutrageProductions Posted December 3, 2023 Share Posted December 3, 2023 As stated previously: cycle the power on your audio interface (ie: unplug it from the USB) for a moment and see if CbB clears the Task Manager in a few seconds. If it does then it is probably related to your Audio I/F driver set. 1 Link to comment Share on other sites More sharing options...
John Vere Posted December 4, 2023 Share Posted December 4, 2023 I’m missing something here? Why do you close Cakewalk? I just X out of the project and then the start screen appears and I open a different project. And I’ve never had that issue anyway. And that’s with dozens of different computers and 6 different interfaces including on board audio. Plug in??? Probably. Link to comment Share on other sites More sharing options...
sjoens Posted December 4, 2023 Share Posted December 4, 2023 I close it when I'm done for the day... or a changed setting (like a custom theme) requires it. My case is probably a rogue 3rd party plugin that only needs to be scanned, not loaded, to wreak havoc. Link to comment Share on other sites More sharing options...
Johnny Penk Posted December 4, 2023 Author Share Posted December 4, 2023 Even if I x out of the project while leaving Cakewalk by Bandlab up, I can’t load another project. It says, “not responding”. Then I have to bring up TM to end process. I will try the audio Interface but I’ve never had this issue before the last two updates Link to comment Share on other sites More sharing options...
Max Arwood Posted December 4, 2023 Share Posted December 4, 2023 If you go into the task manager, open cakewalk. See if there are subprocesses locking up. Look to see is their are and 32 bit listings. How many sub processes do you have under cakewalk? Link to comment Share on other sites More sharing options...
John Vere Posted December 4, 2023 Share Posted December 4, 2023 It most definitely a plug in or I guess this can happen with audio drivers as some are saying. It’s not Cakewalk itself. Link to comment Share on other sites More sharing options...
Johnny Penk Posted December 4, 2023 Author Share Posted December 4, 2023 9 minutes ago, John Vere said: It most definitely a plug in or I guess this can happen with audio drivers as some are saying. It’s not Cakewalk itself. It’s not the audio interface driver. I just updated it and no change. Going to keep trying to figure this out. Link to comment Share on other sites More sharing options...
John Vere Posted December 4, 2023 Share Posted December 4, 2023 What is the interface? Link to comment Share on other sites More sharing options...
57Gregy Posted December 4, 2023 Share Posted December 4, 2023 1 hour ago, Johnny Penk said: It’s not the audio interface driver. I just updated it and no change. Going to keep trying to figure this out. Did you learn this by unplugging the interface and then plugging it back in, or just trusting that your interface manufacturer wrote a good driver? 2 Link to comment Share on other sites More sharing options...
Byron Dickens Posted December 4, 2023 Share Posted December 4, 2023 2 hours ago, Johnny Penk said: It’s not the audio interface driver. And how did we test this? Link to comment Share on other sites More sharing options...
shane Posted December 8, 2023 Share Posted December 8, 2023 Daily Sonar user here.... This (still) happens to me about 4 times a week, and I always thought it was one of my hardware drivers; either the MIDISPORT 8x8 (likely) or RME Fireface UFX (less likely, but not impossible) or something along that hardware chain-- could be a Firewire driver or USB driver is the culprit. Frustrating because it just quits, and I CTRL-ALT-DEL and can't force quit in task manager. The FASTEST solution has always been to reboot. Link to comment Share on other sites More sharing options...
Bristol_Jonesey Posted December 9, 2023 Share Posted December 9, 2023 Do any of you with this problem boot up your pc before your interface is switched on? Link to comment Share on other sites More sharing options...
Dave Gelzleichter Posted December 9, 2023 Share Posted December 9, 2023 I had this problem some time ago, and the fix was updating my graphics card driver. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now