Search the Community

One thing I just had happen because I was working on videos and using 48hz, Cakewalk would drop out when switch back to 44.1 or I loaded a 44.1 project. So is it possible your interface is having to change sample rates? This shouldn't happen but it is a possibility. If your projects are 48 and your exporting to 44.1. But as said this is off line and shouldn't matter. But it might explain the drop out and why the export is unaffected. I don't think the export uses your ASIO driver or the audio engine. But if it's converting??

1. Is the plugin on a track or a bus? If the latter, is it a separate bus just for reverb? If the former, is it a mono or stereo track? I have seen odd behavior with some stereo plugins when placed on a mono-interleave track, including reduced volume. 2. Are there any other plugins in the track/bus fx bin that the reverb is on? I have seen weird interactions between plugins, where a specific ordering causes the signal to be lost. 3. Is there any automation on the track/bus? Volume automation, obviously, but pan automation can also cause unexpected drops in volume. 4. You're running the paid version, but I've seen cases where a plugin reverts to demo mode on its own. What are the demo restrictions, e.g. does it drop out at intervals? Maybe a screenshot of your minimal project that shows the problem might help, just to see how everything's routed. This might seem like a left-field longshot, but what happens if you substitute a different reverb in your original project?

The drop out message has a code (16 in the image above) and a link to the help in the lower right. Click on the help and it opens this page http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.53.html listing the codes, cause and action to take. In order to provide more assistance requires much more information about the hardware (PC specs and audio interface), OS, DAW version and setup info such as driver mode, interface buffer settings , the drop out code and details about the project.

Issues that I've encountered since updating to 09: * Sometimes synth tracks drop out, on export; * Sometimes synths are out of alignment with the audio, on export; * When you edit or change settings during playback (playback loop on/off, resize audio clips, move audio clips across tracks, etc.), the output of all synths drops out. Arranger is a mess - I don't know if that was there before, it's the first time I've tried to use it: * When promoting arranger tracks (moving parts forward, in the order) - either by hand or in the arranger window - the program crashes; in the rare instances it doesn't crash, what and how it moves, only God knows - some clips, yes, some, not, the Arranger block header, not, so on so forth; it's unusable; * When demoting arranger parts - it doesn't switch the parts in the order, it just lengthens the song by ADDING the part moved in the place you moved it to, and leaves a gap in the original place 😳; I don't get the logic behind that; if you also have a tempo variation along the way, the result is a mess, cause it doesn't know how to handle moving parts among different tempos. * Also, when demoting arranger parts, some audio clips are truncated for no reason - you need to resize them every time. * In the process of moving arranger parts, audio clips get misplaced randomly in the project. I've had audio clips thrown back as far as bar 867, in a project that ended at bar 110. If I didn't tag every single audio clip, I wouldn't even know what those were, so I would have to spend time finding where they belonged. The export in that instance took about 45 minutes, and I had no clue why - cause it's not like it announces it misplaces clips. Workspaces - when you choose one as default, it applies it over the existing project settings, on load, so it does more harm than good. If you choose none as default, it doesn't apply it to new projects, so it doesn't help. Default Workspaces should only be applied to new projects. The settings a project are saved with should override everything. You don't choose particular settings and save the project with them, to have them replaces by the Workspace every time you open it. Meter resolutions should be a part of the Workspace settings, as much as anything else. When applying a Workspace to a project it should act like a mass settings import, after which it should no longer intervene. Any changes that you make and save with should be kept on project load - again, saved project settings should override everything. Clip gain: when I create a gain envelope on a clip, it automatically creates envelopes for all clips in that track. I avoid using the feature, cause I have to spend time deleting all other envelopes afterwards; don't get the logic behind that move either. When you select a clip, it should only create the envelope for that clip. About the buffer: we're not engineers, and shouldn't start engineering our own exports, I think Cakewalk should automatically choose the fastest buffer size based on the available resources, and we have to trust that it does a great job. When I choose a compressor, I don't have to manually adjust the THD, the compression curve, the noise levels and such, I just know that the compressor has all of those dialed to where it sounds good, and that's why I choose it. How would somebody change their buffer size? What do I check, and what calculations do I need to make, to make sure it's the fastest that works without dropouts, and such? And what is that about the buffer size changing the sound of the track? That shouldn't happen in any circumstance, and I shouldn't need to change the buffer size according to "how I want the track to sound", should I? I have plugins for that. Just my experience, if it's of any help improving this program.

Hi, I'm new to this DAW and I have sound drop outs that i cant fix. I have put a few tracks down and mixed them nicely (Purely volume and EQ), and then Cakewalk stopped making sounds. Cant hear a thing, however the program seems to be running fine. Windows sounds works fine with everything, - just not with Cakewalk anymore. Things I have tried (might not use correct terminology); 1- Changed playback buffer size (to them all), (Was set at 256) 2- Changed Driver mode (to them all), (left on WASAPI, tried MME) 3- Applied, saved, reloaded Cakewalk everytime, 4- Checked every forum on the internet (including Youtube), 5- Made sure windows and cake walk use same Sample rate, 6- Disconected all (besides main) devices in windows, 7- Probably other stuff I forgot to mention (but willing to try again), Also, It was working fine, then just stopped (I presume with a drop out message), however at the time I did not know to look at the error number and look up the link to the documentaion - (I found that out while tring to fix the issue). I dont know how to find out what error number it was. This issue IMHO is an error that should never happen on audio software, Its like an error that stops the display on a graphic editor. There should be a failsafe since this error renders the software useless. Enough ranting from my frustration.... So does anyone have any ideas? or was my mum right in saying that I was unique to everyone else in the world?

I like it. Great vocals and instrumentation, and a catchy tune. A very minor thing which could be my listening setup, but the upper frequencies of the side-stick seem a little hyped in the section near the end where the instruments mostly drop out. Other than that, the mix is really good and the instruments are really well placed in the stereo field too. Well done, and thanks for sharing!

Hi Tecknot, thanks for your response. Sound card sample rate is set to 4800 Mhz, buffer size is 256, Cakewalk is set the to the same sample rate, using ASIO Mode my understanding is that the bit rate is fixed at 24. Usually when there is a conflict I hear a tick as the project opens and realize that Cakewalk has reset my sound card to match the project configuration. I'm not sure how to set sample rate in Windows, my Windows sound settings defer to the device selected. Drop out and static occurs also with brand new project files with nothing more than a single audio track, but the more severe blue screen drop outs are from heavily packed projects with many virtual instruments. In such cases I have gone through the project deleting track by track to observe changes, for a while I was thinking there was a problem with one of the libraries. There could very well be more than one thing going on here. But I've never found a clear identifiable culprit. Regards Heb

When I wrote and play the song on piano and sing it, it doesn't sound so Beatle-esque, but when I arranged it for a rock band and strings, my use of a Rickenbacker 12 string guitar (Orange Tree Samples' Evolution Rick 12 String library) and the Modo modelled Hofner bass played with a pick (the way McCartney plays it), really gave it a strong Beatles' vibe -- and of course the string arrangement is definitely from the George Martin school. I originally recorded this with a Fender Precision Bass (Orange Tree Samples') library using a preset that is based on James Jamerson's tone, but I really wanted the tone of a Hofner bass on the pre-chorus (the section where the drums drop out), so I found when I replaced the bass, the song took on a much more Beatle-esque vibe and then when the Rick 12 string guitar on the chorus is incredibly linked to the Beatles' sound too. And then I ruined it all with my crap vocals! Hahaha. Sad.

Looking at the 3rd screen shot I see the #1 spot is ataport.sys. I googled this and there sure is a lot of issues with audio ( on board) and hi DPC due too this driver. Not sure what is actually does there's not much about that part. But when I run Latency monitor on 3 of my computers I don't have that. But I did get interesting results on each. my main DAW no surprise it stays in the low green even with the wireless internet on. I fired up the old Silverstone which I'm just in the process of adding software. It is only fresh out of the box and it's looking pretty bad. This is vintage 2008? and all the hardware was top notch in it's day but W10 struggled with some of the drivers. This is a fresh install of W10. I'm not even sure how far we should trust Latency monitor as far as it's report and what to do. It always say's the same thing about CPU throttling and when I check it's always disabled by default ( I certainly didn't do it) I also ran Latency Monitor on my Laptop I use for remote recording. Its W7 , i5 8GB RAM and works great. But It also showed a hi DPC count due to yet another system driver. Sorry no screen shot it's off line and doesn't have one drive or drop box. But the point I guess it makes is if it's showing nasty DPC count and your having drop outs then at least you sort of know why. This ones my Office computer I just re built with a new SSD drive and a fresh install of W10. Seems we share a common ground here with the NVIDA driver wining the DPC race to the front.

Yeah, the current help is hosted on the old Cakewalk server which BandLab acquired. The web-based help is updated with every release. The drop out codes were added in 2019.09 If you prefer, there is a pdf of the help in here It is not updated as regularly as the web-based help though. Good news - easy fix especially with the addition of the drop out codes

There should be a toast message containing a drop out code and a link to the help page about the drop out codes. It may not be any particular track/lane. It is not clear if leaving track 57 alone and archiving other tracks solves the problem too.

Not seeing anything like that here. Multiple people have tried it. It is likely specific to your project. What drop out code are you getting?

I am wondering why, after recroding this piano instrument into the interface, am I getting a pop on nearly every audio recording. Its in this begininng 4 beats on about the 3rd beat. Othertimes theres a drop out and sounds like a CD skip The 7mb mp3 file is here for download https://file.io/ZKHq9hPAm9aK

My rig is a fairly decent Windows laptop with a fast setup (it never breaks a sweat to be honest) which I got custom built by Novatech in Portsmouth UK. On it I have BLS which is connected by a single into three USB splitter. The songtracks are all individually track recorded mixes of 'my version' of songs, mixed and mastered as best on phones then better optimised in the rehearsal studio with the PA we use and so that it sounds okay on the IEMs we use. All the mixes have VST plug ins such as compression and EQ (the presets shipped with BLS are pretty good, TBH, just need a few tweaks to sweeten in places on either individual tracks or on busses) My buddy has a Mac running Reason and three controllers and has his sound arsenal split and spread across them. The USBs connect to firstly my Roland FA06 (which is stuffed with the Axial updates), to the footswitch (which, thanks to the kind folk on here is programmed to send a 'spacebar' command for my buddy to start the songfile) and to my 'desk', where it splits further to control my Voicelive, Lexicon MX200 and a DMXIS lighting 'dongle' which has it's own VST plugin in BLS. The songs are as said, all multitrack audio. I have MIDI tracks sewn in which control the effects (PrCh, CC for on/off), my FA06 (PrCh), and the notes in the DMXIS assigned VST Plugin which changes pre programmed scenes (strobes, lasers, hazer, moving heads, washes) Songs are stacked in different Play Lists as sets. Load a song, the next one loads behind it ready for a spacebar from the footswitch. The mixes we have are engineered to drop out the synth sounds my buddy is playing and that usually is basslines and obviously drums. I play the odd song on my Roland AX Synth. Unfortunately, because the MIDI on the AX Synth is via Bluetooth I am currently and sadly not using the synth engine in it (the radio TX/RX is pretty shit also) so I am thru-ing a track to play my FA06 which gives me 15 layered patches on Ch1 anyway. I link this via a PandaMIDI remote. It sounds complex - it is. But the effect is good and although it's fun setting it all up, the audience love it. The only snags we have had recently are drunk customers and people wanting selfies, mid song. A while ago the firmware in the DMXIS dongle threw a six but that was fixed the next day with a clean out and reinstall Any other Qs, please fire away HARDDRIVE

I've been having this problem for a while , and I think I finally solved it. Some of my songs would drop out make noise, and my thread monitors would go through the roof after a few minutes of mixing down to mix down computer. I tried changing the setings to my Motu AO24 , but the results were the same. Finally while Cakewalk was running I did something I never tried before. My audio files are on my SSD "F" drive. I called up the Task manager (alt/ctrl/delete), and clicked on the performance tab. There was no or little activity on my "C" drive. Right before the problem started, the activity of my "C" drive maxed out, the audio noise started. I then stopped everything and after a few minutes, the "C" drive maxed out itself again, reading and writing. When Cakewalk was playing with all the plugins, I was only using about 7% of my 128GB RAM, and my audio drive was using 6 to 15% of it's resources, I think I narrowed it down to having the automatic defrag on. I turned it off and the "C" drive shows no activity, except from the ethernet, which I may turn off while using Cakewalk. So if I have problems in the future I'll watch , for programs running in the background with the Task Monitor from now.

Recently I have revisited some of my earlier work with the view of updating and remixing them, ( after all, I now have twenty five years or so experience of working in Cakewalk, so I can now make them better .. yeah)? Well, it hasn’t been without its problems. My idea was to re-record the drums on some, (I am now able to record 16 tracks of audio), and use newer plugins where required, and generally spiff things up. And so I began, and soon the glitches began also. I could start recording ten tracks of drums and very soon the audio engine would stop and throw up an error. I have an Intel I7 processor and 32Gb of Ram and can normally record at a buffer size of 64 but I was getting audio engine dropout all the time. I would disable all plugins, but still the audio engine would drop out. It soon became apparent that the dropouts were occurring in the same places most of the time. In my earlier work I did a lot of editing to the tracks and would leave them in their raw state without bouncing to clips after, and so everything was a bit untidy. I would then bounce down to a stereo track, export to wav and mp3, and that was it…done. Also, often I would be working on a number of different projects at the same time, so I would be back and forth between projects at different times all on the same hard drive. You see where I’m going. My projects were becoming fragmented, although I didn’t realize this at the time. Now I read somewhere that .bun files collected all the audio of a project and kept the files together, so I wondered if this would solve my problem. I had never used .bun files before so I saved a project as a Cakewalk bundle. The saving of the project can take some time as Cakewalk collects all the scattered files together in a new file. I then opened the new .bun file in Cakewalk and played the file to check. I then saved the project as a Normal file, closed the project and then opened the new .cwp file in Cakewalk to check. After saving to bundle .bun files and then to new normal .cwp files I was able to record new tracks without audio engine dropouts. We see many people on these forums complaining of difficulties with audio engine dropout and recording, blaming Cakewalk as problematic, so I wonder if some can be solved in the manner I have explained.

ive had the very odd drop out, i just turn the unit off for few seconds and back on and s sorts it out so the usb drivers refresh without rebooting the pc. Drops out usually a software issue which can conflict with driver on pc, things like youtube can even cause it running in background using the sound drivers haha and not the unit itself which is rare, so basically background programs, anti virus, wifi and things like apps that also use audio like spotify etc

You Don't Know Jack Schitt? Many people are at a loss for a response when someone says, "You don't know Jack Schitt." Now you can intellectually handle the situation. Jack is the only son of Awe Schitt and O. Schitt. Awe Schitt, the fertilizer magnate, married O. Schitt, a partner of Kneedeep &. Schitt Inc. In turn, Jack Schitt married Noe Schitt, and the deeply religious couple produced 6 children: Holie Schitt, Fulla Schitt, Giva Schitt, Bull Schitt, and the twins: Deep Schitt and Dip Schitt. Against her parents' objections, Deep Schitt married Dumb Schitt, a high school drop out. After being married 15 years, Jack and Noe Schitt divorced. Noe Schitt later married Mr.Sherlock, and because her kids were living with them she wanted to keep her previous name. She was known as Noe Schitt-Sherlock. Dip Schitt married Loda Schitt and they produced a nervous son, Chicken Schitt. Fulla Schitt and Giva Schitt were inseparable throughout childhood and subsequently married the Happens brothers in a dual ceremony. The wedding announcement in the newspaper announced the Schitt-Happens wedding. The Schitt-Happens children were Dawg, Byrd, and Hoarse. Bull Schitt, the prodigal son, left home to tour the world. He recently returned from Italy with his new bride, Piza Schitt. So now if someone says, "You don't know Jack Schitt", you can correct them. Not only do you know Jack, you know his whole family!

Thanks for following up and thanks for asking. I had at least two files open with different midi clock sources and switched between the open projects from the Windows drop-down menu. One was set to use midi sync, the other set to use audio. I confirmed that at least twice today before posting my question. Later in the day, I got a code 13 dropout; I am not sure what prompted that. (I dealt with it and moved on.) I will see if I can replicate it now with the code 0. Results of quick test: With three specific files, after switching I got code 13 four times. With two of the files open, I got code 0 four times when switching. It is possible that something within those files other than the midi clock source makes a difference as to which dropout code I get. BTW, when I consider having two projects open at the same time with different clock sources "User Error" (i.e., not a bug). Easy fix: Don't do it! Update: Currently narrowing down possibilities when switching with the two-files loaded. Drop out code 0 seems to happen when I switch with the transport off (not playing back). When playing back just not (several times), there was no audio dropout, though there was a consistent audible glitch. (Dropout Msec = 250) It is possible the code 0 comes from (1) Cakewalk not receiving midi clock (i.e., not being sent) and (2) the transport being stopped. To be tested. Update: I need to sort this out for my own needs (real-time performance stability), so I will be doing further testing, probably tomorrow. But for now, I can get audio dropout code 0 both when my external clock source (1) is and (2) is not transmitting midi clock. This is prior to putting Cakewalk into external midi clock standby mode (i.e., prior to pressing play on the transport and getting "Press <Esc> to cancel. Waiting for MIDI Sync.") Once in external midi clock standby mode, the Window drop down menu is disabled, so no switch can take place until after the transport has been started from the external source. Then an external stop command successfully stops the playback, Cakewalk goes back to midi clock standby mode, there is no audio dropout, etc. as expected.

I don't really want to call them crashes, although I suppose one could. I'm curious if anyone else is experiencing this. Here's the deal, with a bit of history: I guess it started a month ago or maybe a little longer, where CW would suddenly exit to the OS. It wasn't a hard crash or anything, the sort of thing that might have required a system reboot. Nope, suddenly *boink* it would just drop out to the OS. I reloaded CW and everything was back to normal -- until it happened again. And then I noticed a trend. You know how, if you load a series of CW files, the previous one(s) don't exit, but just stay in the background? Well, I began to notice that if I had loaded a certain number of files, it was more prone to exiting. So I started keeping an eye on the number of files that had been loaded, and it doesn't seem to be a definite number -- probably has more to do with the amount of memory each uses? But CW usually exits after 4 or 5 files have been loaded. And I can always tell when it will happen. After loading the last file, when I click on "Play" the transport icon turns amber and then stays that color for a half-second or so, with no sound being played, and then, poof, back to the OS. It got to be so regular that I got in the habit of clearing out the background files so this wouldn't happen. Until one time, and this has happened only once so far, the same thing happened to a file with none in the background. After rebooting CW and reloading the same file, everything was fine. So it didn't have anything to do with the file, far as I could tell. And in case you're wondering, the system is fairly new. It's running Win10 from a new SSD drive, and it has 16 GB of RAM. I have a couple of TBs of open drive space on the drive I use to store my music files. Back when I was running Win7, this never happened. This machine has had Win10 since January, with none of this sort of behavior until relatively recently. I don't know if I should be pointing fingers at a recent update of Win10 or a recent update of CW or maybe both? Or something else, altogether? This isn't really a pressing issue. Nothing's usually being harmed, since it happens when I first press "Play." It's just a matter of curiosity at this point, but of course, I wouldn't mind putting a stop to this behavior.

Thanks Jeff! Hi David, Thanks for the encouragement and kind words I did actually use Cakewalk to mix this. I also gave the SoundCloud mastering service a go and it seemed to work pretty well. I recorded the instruments with Studio One because at the time I had given up on Cakewalk after the Gibson fiasco. Sonar Platinum was my first DAW and I really enjoy the workflow and the workspaces. I could have easily tracked this in the latest Cakewalk as Bandlab has made great strides in eliminating bugs and adding new features and minimizing audio engine dropouts. The comping is easy and intuitive as well. I hope someday there will be zero drop outs but I very rarely get them. I have used the "mask engine dropouts" set to true setting and that has really helped. I can't say enough about the arranger tracks and the new export feature is out of this world! So far I'm finding it better than the Studio One arranger track tool. One of the main reason's I stuck with Studio One is because of the arraigner tracks functionality...it's a super tool for song writing and quickly hashing out ideas. Also the Studio One audio engine is very very fast and stable which I hope someday Cakewalk can be optimized to that level. I had my doubts about anyone being able to resurrect and improve the Cakewalk audio engine but we're seeing that happen right before our eyes. How far they can take it remains to be seen. While I haven't created a song from scratch with the new Cakewalk yet, I will be doing this with my Robin over the next several weeks and I will put the Cakewalk's arranger track feature to the test. So far what little testing I've done with it has left me very impressed.... super easy to use. My favorite feature in Cakewalk is the Mix Recall utility. Back when it was first released (Sonar) I had glitchy issues with it and gave up on it. After running it thru it's paces recently I can't stump it..... it's literally bullet proof so far and coupled with the new export features it's really something special... I don't know if there's any other DAW with that kind of combination that works so incredibly well. I've always loved the pro channel and let's not forget the track templates... another feature that blows my mind and works incredibly well for me. Since I returned to Cakewalk it's been like a little Christmas to me. I've always loved the interface..... it's feels like home. They still have work to do but so far I'm very impressed with what I'm seeing happen with Cakewalk. Regards Craig

Pretty hard to even guess with out more details. Like your system including audio interface and settings. Have you optimized for audio? Drop outs are not caused by Cakewalk, they are systems related. Run Latency Monitor to check.

I just Automate the Metronome Bus Output volume to play the count in then drop out. (especially once the drums are down) Handy to be able to click back in again after a first ending when the song comes back in for another round or three, sometimes faster each round. Also good for times when you rumble the chord for a while at the song start then get a solid click in at the appropriate time for a set tempo. (I just like automating things really)

Thinking the W11 install unregistered Rapture pro Just re install it using CCC. That’s drop out issue solved but still the Latency Monitor report needs attention. Question for everyone. Didn’t have time to read this whole thread. But what I gleaned was even though my 10 year old HP Pavilion tells me it isn’t compatible with W11 it would probably be fine. I just bought a 500 GB SSD to replace the 250 OS drive and thinking I might as well download the W11 version to install fresh. Thoughts? Figure I have nothing to loose as will still have the original 250 W10 OS drive to fall back on.

I doubt an antivirus program is causing your drop outs, especially with today's PC's and how streamlined antiviral programs are now. One fast way to find out is to disable the program and see if you are still get drop outs. But drop outs are cured by raising your ASIO or WDM buffers. That should cure it