Search the Community

ajust want to day that this midi device drop out is still persisting in 2023... just wondering if anyone actually found a solution? transition to reaper?

I have a dual socket, AMD Opteron 6274, 32 core system running at 2.20Ghz 56 Gigs of memory. *8Gb dedicated to each processor = 40Gb usable. 512GB SSD "C" drive Sometimes Plugins have been installed on "C" drive, other times installed on other SSD Drives to prevent bottle necks. I've tried all the tricks here. + Multiple sound cards/Multiple driver configs +Multiple soundcards in multiple re-installs of windows. With and without updates. Audio drop out happens when I try play back of: 2 midi tracks, from one instance of: Kontact 6 (In pic) (Also tried Kontakt 7) through 3 "loaded" plug ins using less than 207 Mb of ram. Kontakt has been set to use 1 core -> 16 cores. Nothing resolves this. Does using protools or other software help those of us, with similar issues? I've had this issue for years. Just started recording again. This is unbelievably frustrating.

Yeah, 300 is crazy. Trying to milk the last drop out of their faithful users, who are usually running professional studios in Europe and don't mind the upgrade cost *that much*. Being the powerful DAW that it is, I wonder if it wouldn't sale A LOT more if they priced it similarly to Studio One, for example. Maybe they dread the inevitable increase of support tickets... EDIT: OK, it's worth pointing out that the upgrade cost is for the Suite version, which comes with quality 3rd party goodies. To upgrade Samplitude proper costs $200.

Nice inviting intro to let the listener into the song. Nice harmonies in the chorus. Nice drop out for the lyrics stayed at the back of my mind part. One of those tunes that either elevates one's mood or let's them accept some sadness - or both!

Hi, Seem to have developed a random audio drop out & can't for the life of me work out where from. The audio will just suddenly stop for less than a second. Never in the same place. It doesn't happen often & it's not CPU, buffer or AD/DA induced as the material doesn't have to be taxing the PC for it to occur. Nor is it mechanical - speaker cables/amp etc. I've been using this particular system for 5 years - 8 core intel - 32 ram - Windows 10 - RME Fireface UC - and it's been fine until recently. Has anyone else suffered this. Is there a work around? Thanks... Steve E

I’ll have to agree with @Lord Tim. Audio interface drivers can make a difference and I was a bit surprised at Marks comment. I have 5 audio interfaces on hand right now. My latest is a Motu M4. I had been running using 128 as my buffer with both a Tascam and a Scarlett interface. The minute I started using the Motu I would get occasional static. Not drop outs but definitely the audio sucked. I now have to use 256 and even higher. Out of curiosity a few weeks ago when this happened I turned off the Motu and turned on the Scarlett 6i6. I set it for 128 and worked all day with out any audio issues. it’s old and missing a few features the Motu has but the only difference must be in the driver. I keep hoping a driver update will fix it. The other thing I wonder about is USB power? The Tascam and Scarlett use wall warts. The Motu is bus powered. At Motu supports advice I purchased. Dedicated USB PCIe card which improved the static issues somewhat but not 100%. When the OP said Zoom I went “ Oh, oh! “ Been many complaints about those drivers in the past. I think some companies like Motu are very oriented towards Mac OS or that interfaces that don’t come with proper power supply’s do not perform as well as the ones that do.

I paid for Cakewalk for MS DOS, Cakewalk for Windows and then for Sonar, etc. If the quality is there and the price is within my budget, I would not mind paying again. To be honest, I will be happy if all the malcontented entitled freeloaders drop out from the forum. 😜

i had something similar about a month or so ago on a plugin i was using on my bass track and could really only notice it once i exported as a 2-track and so i had to trace the crackling and drop out. eventually figuring out it was in demo mode after a recent move to W11... now i've been steadily checking plugins i haven't used in a while to see if they fully activated or not...

I didn't count latency as a performance issue per se, but I can see how it could be seen as such. The latency does differ between interfaces even though the buffer size could be the same. The bottom line though, is that it's up to the CPU to cook the buffers in time. Increasing the buffer size (and therefore the latency time) gives the CPU more time to cook the buffers. Cracks & pops are a symptom of the latency time being too low for the CPU to catch up with, but not enough to drop out.

I never got Wotja v22 Pro plugin to play nicely with Cakewalk. If I want to use the Wotja VST plugin, I use Reaper. In my case. Wotja loaded OK in Cakewalk and the track is created, but after it started playing the Cakewalk audio engine would always overload and drop out. Never figured out why, so just moved on... evidently the Wotja plugin is sending something that Cakewalk doesn't like. So really have no clue... Tried the new Wotja v23 Lite, and it's about the same. Edit: see my latest post for a resolution.

Probably because really the only solution in this case is a second audio interface. Not all onboard audio is the same I guess. It’s a hit or miss thing. I do what you are doing with my office computer. I like to write my tutorials with Cakewalk open and test plug ins so I load up large projects sometimes. Quality seems very limited when using the on board audio and I get crashes and drop outs so I connected my old Focusrite 6i6 and the weird issues all were gone. I also have a laptop that is much newer than my office computer and it can play all my projects with out issues using on-board audio.

I had this type of experience but here is what I found out: 1) IF the last track in the track view is a folder AND that folder is collapsed. Grab your track (that you want to move) with the double up/down arrows and move it below your folder and place the double arrow as far LEFT as it will go, then release. Your track should drop to the bottom and not be in the folder. 2) IF the folder is the last item in the track view, and the folder is expanded. The track indicator (should be a colored line) will indicate where it will drop. If it aligns with the last track in the folder - it ends up in the track. IF the colored line is aligning to the extreme left (of the track view) then is should drop outside of the folder. Set a dummy project and try these moves and you will get a hang for it. The second method is the most accurate for doing this. I think that it would be nice if the "track line" showed up when the folder was collapsed. I would have included some screen shots, but I must in a bit. I just tried this several times to be sure that what I saying above works - At this time I thing it is just a technique you have to get used to. Once you get it working for it does not seem to be a big problem. Oh, and if your folder is in the middle of you track view - watch the "track line" - if it aligns with the folder, it goes into the folder. If it touches to the far left, it sits below the folder by its self. Hope this helps. Syphus

I'm running a stable i5-9600k PC with 32GB RAM, Win 10, Focusrite 2i2 at buffer size 256, although I've played around with that setting. Tried ASIO and WASAPI with same result even using the Wotja internal sounds. When I use output to VSTi, the MIDI seems to drop out first. I've been trying on and off for over a year to get Wotja to run stable in Cakewalk . Basically got tired of testing when I found that it runs without issue in Reaper. Not sure what it could be, as I have been pretty much over everything. Glad that it's working for you! Edit: see my latest post for a resolution.

Thanks (and for the YT comment, I thought the name looked familiar 😅). I still have the occasional hanging midi note or sudden midi drop out, but this is the best it can get. Until I get my Midronome that is.

I am having really bad audio drop out issues not matter how little or how many plugins or files are loaded, found a tutorial in regards to setting latency and other parameters but no change. Had none of these issue on the previous version I was using. Where is the link to roll back as I have work to do and this is frustrating.

Where is the information on rolling back from the current version release of Version 2022 11 Build 21 64bit? I am having major audio drop out issues and nothing is fixing it and its only since the version upgrade. Any help would be appreciated.

Hoping someone can point me in right direction of what to try/look at. Just upgraded my machine ( new mobo, cpu, ram and reinstalled new windows, cakewalk, and all my plugins) Now I can’t playback any of my projects without issue. Seems ok when I disable all plugins but as soon as I add a number of them it happens. Doesn’t seem to be one particular plugin, I’ve tried multiple combinations. It will either drop out for a split second randomly or sometimes when I reopen project it’ll be a quick burst of white noise or a crack or pop , anywhere from a minute in between these things or a few seconds- generally one every minute or so though. At first I thought maybe it was the PCIe firewire card i had to purchase to replace the PCI card I was using on old system, but I’m not so sure. I’ve rebuilt an almost exact replica of one of my projects in studio one and it runs rock solid and gained ability to do more as I hoped it would with computer upgrade. That said it seems to be something with cakewalk only as I installed reaper as well and loaded it up with plugins and runs fine too. been a cakewalk user for decades so really familiar with it and really don’t wanna have to switch. System is Win 10 pro 64 bit , Asus Prime z-590-a motherboard, 32gb ram. Pcie (w RME recommended texas instruments chipset) firewire 800/400 card, RME fireface 800 interface (using fw 800 cable/ port from interface to card) driver version 3.125, hardware revision 2.77. Storage drives are ssd. I’ve tried all manner of various buffer settings in cakewalk and in fireface driver- none of which make a difference. I’ve reset config file. I did a whole reinstall of windows, cakewalk and still same issue. Tried the legacy firewire driver. Can’t figure out what is wrong. Any ideas?

I'm hoping someone can help me here. Until recently, I was using Windows 10 with a 3rd gen Focusrite solo, and Cakewalk (latest), on a 16GB memory machine, with i7 quad cores and a fast SSD. I upgraded to Windows 11 recently. For simple projects, Cakewalk and Focusrite work (sort of ) OK. However, any project with more than 4 tracks, and I get all sorts of engine drop outs, pops, crackles when I try and record a new track. On Windows 10, I had a few projects with > 16 tracks, and never experienced any issues at all. If I want to record e.g. bass, guitar, midi, Focusrite gets set down to a buffer size of 64 samples, or else the latency is awful. If I want to mix or master, then I have to set Focusrite up to 1024 samples, or the engine keeps dropping out. I followed a Focusrite 'Optimize audio for Windows 11' (https://support.focusrite.com/hc/en-gb/articles/4408057193362-Optimising-your-PC-for-Audio-on-Windows-11) and still have issues. I found a few other Cakewalk and Windows 11 blogs that offered a sub set of what Focusrite suggested. I've run out of ideas at the moment. I am past the 'revert in 10 days' window of Windows 11, so going back to 10 would be awkward. If anybody has any ideas or further links, I'd be most grateful.

without hearing the grooves and assuming you're using either midi drums or beat slices, you could try; managing the tension (push/pull, rock&roll) between the kick and snare (classic kit dynamics) work on the hihats (articulations, timing and timbre) and to a lesser degree, the transients/ambience for key hits in the groove or drop out a kit piece (arrangement) and all relative to whatever else is in the mix.

It is a medley. The first 16 bars are me vamping over a 4 chord progression from Paul McCartney's "Dear Boy" with my melody. I then go into a song I wrote when I was 13 that had a very strong McCartney vibe, called "Brighter Days," for the remainder of the medley. My concept was that together it would serve as my tribute to the music and bass playing of Paul McCartney and how much it influenced and inspired me. I had written 4 new compositions for the demo and received the green light on one, but I recorded this one impromptu, as a little jam, and it just felt more enthusiastic to me. The part you like, I think, is the part with the drums drop out and the Mellotron strings (with a cello in the background) come in? I actually pulled the drums out of that section to draw more attention to the sound of the bass, which, of course, is the point of the demo. This is my cover of "Dear Boy" that I took the 16 bar intro from (this was before Orange Tree Samples released the Evolution Vintage Violin Bass library; I used MODO's modeled Hofner. During exposed parts I actually doubled the parts with a guitar, as the modeled bass, when exposed, lacked depth in the tone and it becomes transparent when it's exposed in a mix. BTW, that demo is the first music ever really shared publicly, beyond my SoundCloud account that I don't promote, but mainly share with my friends and get feedback from the Cakewalk Song Forum on. While I played drums semi-professionally in bands from 18 until sustaining a repetitive stress injury in 1999, none of the bands I played with (beyond an instrumental band I put together when I was 18 that had like 3 gigs) performed any of my music. So after all of these years, a song I wrote when I was 13 is now being shared publicly. I never really would have been comfortable with my playing being shared publicly, but Greg Schlaepfer, the CEO of Orange Tree Samples is a friend and has been encouraging me to play music again -- so anyone that hears my demo and thinks it's terrible, blame him and his encouraging me! Hahaha. But I seriously also rationalized it as something to put out there that shows even a guy like me, who is no longer a competent musician, can still pull off something semi-decent with the right tools and a little musical imagination. This was the cover I did of McCartney's "Dear Boy" that I pulled the first 16 bar progression and arrangement from:

It's a bit time consuming to un-check so many boxes. I was hoping there was a simpler way to just turn ASIO utility on or off or at least use the Windows Task Manager to kill the service. While I've got you on the phone, I have tried it on both my older Win 7 machine (slow but decent) and my newer Win 10 machine (very, very fast CPU with 3 SSD drives) and both appear to have the audio drop out from time to time just playing my usual song in Cakewalk. This is just an observation before even introducing a Zoom session into the equation. Are there any latency issues I should be addressing when using this utility? Other settings to consider? Things work fine with this song using the normal ASIO drivers in Cakewalk. The problem seems to start when I re-route ASIO through this utility. Thanks.

I was going to let this one just drop out of sight because I didn't like it that much, but I do like the video. Nigel, Hidden S and Dream Art, Thanks for the comments.

There's a number of things that could cause drop-out, although since you're recording MIDI and not audio, the fact that your 7200rpm disk is 85% full shouldn't really have too much of a bearing... however: If this is your system drive, and you've not got at least 16GB memory, disk activity could be high due to memory being swapped out. If you've got audio tracks streaming from your disk (or samples for your VSTi's), then this could slow things down... especially if your audio tracks are on the same drive as your OS. Do you have CPU hungry VST's on any audio tracks, or any CPU hungry VSTi's that could be causing dropouts? I'm assuming you're using ASIO on your Focusrite? If not, make sure you are. You can try increasing your ASIO buffer size to reduce CPU load. Another option would be to freeze any tracks that are causing drop-outs due to high CPU usage (although you then might have [2] to worry about). Your CPU is more than capable of coping with most projects (it's pretty much on par with mine). So personally I'd recommend: Consider investing in an SSD for your system drive. You could then re-purpose your 7200rpm HDD for audio. Having your audio on a separate drive from your system drive can make a huge difference. If you can afford to get an additional SSD for audio/samples do so. For me, swapping to an SSD was like night & day - Omnisphere could take 45 seconds to load a patch from an HDD, whereas the same patch on an SSD is 2 seconds. Look at your memory usage in Task Manager and in particular the swap file usage. If there's a large amount of swap file activity, or your memory is over 75% usage, consider getting more RAM. Before you make any purchase though, try to ascertain what is causing the drop out. Look at the drop out code, and refer to this chart: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=AudioPerformance.24.html . This should give you some indication as to what the underlying cause is.

I have a weird problem. When I start Cakewalk it appears in the task manager - until a project loads. Once any project or even a blank new project is loaded it disappears. But then, when I exit Cakewalk - it reappears. Then many times it won't go away until I manually end the process. After a project loads and Cakewalk disappears from the task manager, Windows will run programs that usually only run when nothing else is running. That, of course causes Cakewalk to run slowly and/or drop out often. It's as if Windows doesn't know Cakewalk is running. I am running Windows 11, but it also did the same thing on Windows 10 before I upgraded. Anybody else having this issue? Any ideas? Any existing threads about it I may have missed?

I have run into an issue and felt I needed to report it. The issue has only started since I did the EA update and has never happened before (that I remember). The problem is when I adjust a parameter while playing, (so far, track pan & send) an instrument (or sometimes more) will drop out. It will stay out until I restart the song (song position doesn't seem to matter). I don't have to be adjusting the track that drops out, it can be any track. It's ALWAYS my drums (Superior Drummer 2) that drops out and sometimes other instruments as well. As I said, I've never had this to happen before. I usually have several audio tracks as well as VSTi tracks, all with various plugins. Basically a backup band with multiple recorded guitars & vocals. I'm a looong time CW user (since DOS version) and know CW well. Nothing has changed on my system in several months, so it wasn't a Windows update or anything (updates are locked). I'm running: MS Windows 10 Pro ASRock MB w/American Megatrends BIOS AMD FX-6300 3500 Mhz (3cores, 6 Processes) 8 Gig memory (yeah, I need more) MOTU 24i Audio interface (latest drivers)