Jim Stamper

Thanks, that sounds like a good idea, but I'm not going to get into troubleshooting right now. I spent years in a day job troubleshooting PC issues. It's usually a process of elimination and can take a lot of time. Plus, if there's a name for this Cakewalk symptom ("Poof") then it isn't just me who's being affected, and I only have this issue with Cakewalk, no other apps. It might be a good idea if Cakewalk would take a look at how their code handles Windows filetable requests.

The above problem happened again a few minutes ago. I had a project that wouldn't open (It Poofed! while opening). I re-named it. It opened. At the very least, re-naming is something you can try if you have a Poof project

It's been awhile so I can't tell you the exact settings, but I've done this successfully with a project that had acoustic guitar audio tracks - which I could not re-record, and midi tracks. I increased the tempo significantly from 130bpm to 160bpm. This change was requested by a publisher. The midi tracks of course were mostly easy enough to re-bounce to audio at the new tempo. All of the above posts are good tips. Plus ... it's important how the Clip Properties are set for stretching, and which algorithm is used for off-line bouncing. I also think it works better if you have strong levels in a track before bouncing. Back-up your original project and create new copies you can use to test different methods until you get good results. For me, once I got the best results possible (radius mix advanced algorithm), I still had to edit the acoustic guitar tracks to fix notes or measures that didn't bounce very well. Sometimes I could do it by splicing in identical notes from elsewhere in the track, or from a different take of the guitar track (I always keep all the takes), or even from the original slow version if the tempo of the note (a held note) wasn't important. I finally got a good final mix, and I was pretty impressed that Cakewalk did this well with acoustic guitar. Of course it works better speeding up vs slowing down. The track did get published, it sounds fine, and it gets placements in TV shows and ads.

In my case, I don't see how it could be a plug-in. I changed absolutely nothing in the project. Only the file name. "Poof!" I like that - it's a perfect name for it! PS. I stopped using TTS-1 years ago, it seemed to crash or freeze often. I gave up on it.

The volume controls affected for me are every volume control in every patch I have loaded in the Kontakt GUI. The track volumes (set at 101) are not affected. I don't know about the Kontakt master volume, I didn't notice it - I've probably never changed that control away from the default. To deal with the aftermath ... I located an older version of the project (lucky to have one that was not affected), I saved each of those Kontakt multi's as a new multi (so it retained my desired patch volumes). Then in the new project I replaced each Kontakt multi with my newly saved ones, then all the volumes were at the right level again. I just have to be careful from now on not to hit Reset for a stuck note. In fact the stuck note was not even in a Kontakt instrument, it was a different VST.

It was saved to the exact same location, permissions, etc, the only change was the name. I don't have the time for awhile to troubleshoot this with Cakewalk Support. However I will comment that it's not too unusual for Cakewalk to behave this way ... that is, it will just exit (crash I guess) to the desktop while I'm working on a project ... or it will appear to be opening a project and then exit to the desktop. Seems like I've seen others mention this type of behaviour.

Good thought to keep in mind. I did test that and it's not what happened in my case. That's a good idea. It probably takes a little more time overall (adding automation to each track) vs. using the volume control in each patch like a mixer to set levels and continuously make adjustments. I'm feeling like there's a bug in either Cakewalk or Kontakt which causes my unintended zero volumes when using Midi Reset.

I saw those posts too, tried it, and it didn't make a difference. This is one of the "Other Options" referred to in my original post. Also I forgot to mention that none of my other midi instruments (non Kontakt) were affected, they all maintained their Volume settings. Thanks anyway.

I totally messed up a complex mix today. I had a stuck midi note so I clicked on Midi & Audio Reset. I very rarely have to do that. Some time later, after a lunch break, I realized my whole mix was out of balance. Then I found my dozens of Kontakt7 (Player) patches were all at volume ZERO! After more hours and hand-wringing, troubleshooting, and thinking what might have happened, I discovered that the Reset causes this. I can easily reproduce it now. I tried unchecking the "Other Options" in the Preferences Midi section. I also made sure that Kontakt Instrument Options: Controller boxes are not checked. None of these settings make any difference. I admit I'm not a midi wizard, but is it really supposed to work this way??

This is so flaky, I just wondered if anyone else has seen it? I have a project name in this format project name.cwp and I wanted to save a copy of it I did a "Save Copy As" in this format: bak project name.cwp That copy would not open at all. Cakewalk looked like it was opening each of the plug-ins, etc, but then Cakewalk just stopped and returned me to the Windows desktop. But Cakewalk was able to open other projects. I restarted the PC, same results. I wanted to flag that project for myself so I decided to rename it as this: bak project name is corrupt.cwp And then it opened just fine! I don't have time to try to troubleshoot this, just wondering if someone else might have an answer.

It happens in various projects regardless of what synth. I was able to reproduce it in a simple project with only a few Cakewalk supplied / supported synths and plug-ins. It seems like you need to have several midi and instrument tracks selected, including at least one with a Volume automation envelope AND that track Edit Filter = Volume, and bounce them all down to a single track (like a master mix). I've seen it happen with only 6 tracks. I have a really clean new Intel brand PC - the NUC Enthusiast, Windows 11, and all hardware & software drivers up to date

I've been working with Cakewalk Bandlab support on this, but no resolution yet. I'm posting this in case it might help someone else. Sometimes I get the "catastrophic failure" error when I select a group of tracks and bounce to a new track, usually my "final mix" track. What I've found is I have an Instrument Track and I have Volume automation on that instrument, and I have the "Edit Filter = Volume". When that track is selected and I perform a bounce, it fails with a "catastrophic failure" All I have to do is change the view to "Edit Filter = Clip". Then no problems

Thanks, Yes I also do that when I first set up a PC. But not laptops, I've never used a laptop as my DAW.

Thank you both. All my connectors & cables were new in November. I haven't made any changes. But it's possible something became loose when shifting gear around on the desk. I'll check it out ?

All of sudden, on opening an existing project, I'm getting blue dialog boxes in the lower right corner that say something like "detected a device change". A couple of these dialogs flash up during the open, then disappear. There doesn't seem to be any problem from that point on. Anyone know what causes this? As far as I know, I haven't made any device changes or updates Thanks

Thanks JnTuneTech, I'll have to look into whether there's an option to set the base configuration as non-gaming. I don't recall from when I installed Windows and all a few months back, but it was hectic at the time. I was migrating around 130 apps from my old PC. As far as I know I haven't had any trouble with the Nvidia component so far, it's the Intel update that's giving me headaches.

I have a 5 month old Intel NUC 11 Enthusiast mini-PC ... nice, quiet, small, powerful. The system is almost all Intel - CPU, Graphics, Intel Driver & Support Assistant, and there is also an NVidia graphics chipset. Now lately Intel has been trying to push a graphics update "Intel® Graphics DCH Driver for Windows® 10 & Windows 11" which includes an ARC management utility ... and things have gotten messy. I tried several times to install the update using Intel utilities and when that failed, I used Intel instructions from Intel Support to "manually" install it. All of this failed. And THEN the Windows Update utility came along and "updated" the Intel driver to an older version than I started with. It's gotten bad enough that I have a support ticket open with Intel, which they've been working for about 2 weeks, with no resolution yet. They just keep asking me for more info, and it's starting to feel like I'm doing their QA testing. Intel hasn't provided much clarity re the purpose of the DCH driver and the ARC utility. They seem to promote it for gaming performance. All I really care about is have a stable Cakewalk environment! So ... does anyone have advice on this Intel graphics driver update and how it might help or hurt the running of CbB? Thanks