tulamide

@Noel Borthwick I will tag a developer to make sure, this post is seen. To start with, this is not about a mean person complaining or something along those lines. I love Cakewalk, and I love working with it. I love that it is a gift to musicians, free of charge. Please keep that in mind, for the following parts. I often experience Cakewalk either hanging (""not responing" forever) or crashing silently to desktop. It is not regular, not happening several times a day, but it is enough to be annoying, having jammed for an hour and losing all your progress that you can't really repeat. Now, a program ideally would never crash, but that's not reality. I know that. But these occurencies are so random in a specific circumstance. For example, from some plugins I just know, that a hang/crash will happen at some point. But it doesn't matter what I do when it happens, because the next time it will happen while I do something completely different. I know that it is Cakewalk specific, because I work with 3 DAWs pretty much equally, Cakewalk, Waveform Free and Reason. All the issues I have only happen in Cakewalk. I never experienced any of it in the other DAWs, using the same plugins, doing the same things, for the same amount of time. Also, I have a recent PC with good properties. Reporting such issues is difficult. 1) As a hobby developer I know the other side and realize it isn't helpful at all. You can't fix, what you can't reproduce. 2) Often times, when such things are reported, the reaction is always "that's not Cakewalk, but ... (enter plugin, driver, user, etc)" 3) Another standard argument is "you can't compare apples to pears". My reaction to this (over time) has become to not report them at all. A silent crash to desktop doesn't create a dump file, and Cakewalk hanging doesn't provide any background information as well. It is of course easy to say, that's user specific. Nobody else might have reported it, and nobody else might be able to replicate it, because of its randomness. But I also feel unsure, because -as I said in the beginning- I love Cakewalk, and I want it to be so reliable, that it can be used under production conditions. Others will use other plugins, that might work better with cakewalk, and therefore don't experience issues, and already see it as production-ready. For me it isn't. So I want it to be improved. But I just don't know how to deal with the described issues. Some guidance would be of help. Should we report such random quirks, should we not? Mentioning what exactly I did before a crash won't help, because I can name at least half a dozen of things I've done, before the crash happened. For example, a drum synth can be set to follow key for pitch, to make it playable chromatically. I activated key follow and Cakewalk immediately crashed to desktop silently. Doing the same thing in the other DAWs of course does not provoke a crash. And when I run Cakewalk again and do the same it doesn't crash. However, half an hour later, while changing the drum synth's oscillator shape... boom, silent crash to desktop. This all doesn't make sense, neither for me or for you. I just know something's wrong, without any evidence or proof to give you. How to deal with it. Should I continue ignoring it? Should I report them despite being of no help? And how to deal with the reaction, if reported. It is, frankly, disillusioning to report such strange things just to hear, "oh that's not Cakewalk". I just want to help, and I want to make it right. But the guidelines I'm aware of, don't cover such random issues. And if you're not staff, but will answer: Please make sure to understand my point here. There's no need to defend anything or nayone. I know the developers are working hard, I know the program was so much improved over the years, I know we get this program for free. That all is exactly the reason I'm using Cakewalk, and want it to be as flawless as possible.

Indeed, that helped. It was autosave. I'd set it to "15 minutes or 10 changes", but I'm not sure, how to set so that it only saves every 15 minutes. With some plugins it saved every 5 or so seconds! However, I used a setting now that got rid of this behaviour (360 minutes and 20,000 changes) There are still some plugins left that use a very long time, wether on project load, after dragging into the project, or when opening their GUI. In particular I can name iZotope BreakTweaker, which takes about 10 seconds. I know that it loads/opens quicker in other DAWs (Waveform, Reason), but I won't complain too much. The positive progress is definitely there and appreciated! Thank you!

This version changed something regarding my personal issues. The first start, until the project selection window opens, is not faster. But the plugins do load faster at project load. They also open fast now (at least all of which I tested) in the DAW. But the "busy" moment after stopping the playback has not gone completely. It does happen when I run a loop and work a bit, especially MIDI. The display that normally shows the current time in the transport bar, and is used also to show progress when rendering or opening, shows a progress bar after 1 second, for maybe another second. I can only read about "saving", the rest goes away too quickly.

I'm sorry, for answering only now. I'm not online daily. I tested installing from the full installer, which didn't solve it. I also noticed, that Cakewalk has another hang time right after stopping transport. It takes 2 to 3 seconds during which the standard windows "busy" cursor is displayed and Cakewalk's GUI unresponsive. I had this behavior a long time ago, when I still had a completely different PC and way older CW version (early 2019 or so). Regarding the plugins, it seems that those involved are either big .vst3 files, or use samples. However, this is only true for some, not for all. While at the same time, some other VST3 with sample access or with big file size don't lead to Cakewalk hanging. It leaves me puzzled, so I will definitely try the early access and report! Thanks!

Yes. And the prior version is 2022.09 I also don't experience this issue with my other DAWs, for example Waveform and FL Studio. As I wrote, I don't use any AV other than Windows Defender. I will happily try the full installer.

Will this be ignored then? Old version = everything's fine. New version = plugins bring Cakewalk to a halt One example, trying to open the GUI of Breaktweaker takes approximately 20 seconds, with Cakewalk being marked as unresponsive by Windows. We're talking of the same plugins and the same projects on the same system and the same hardware, with the only difference being Cakewalk updated to 2022.11! Win 10 Pro, 21H2, Build: 19044.2251, AMD Ryzen 5 5600G 6c/12t, 16 GB RAM, several SSDs and a mechanical drive Do I need to mention that no other app gets to a halt when loading something? Well, no other app (from games to video editing) behaves like that.

After this update, most of my plugins need a long time to open and Cakewalk freezes during that time (with the audio engine still running). There is some activity on my SSD, but nothing heavy. I use Microsoft's built-in Defender, no additional AV. And I didn't change any settings. Some plugins involved (there are too many to mention all), all as 64 bit VST3: Synthmaster, Breaktweaker, Pneuma, Orb Synth, Thorn, SampleTank 4, and many more.

Hi, I hope that someone has successfully used ADSR Drum Machine in Cakewalk (you can use the demo in case you want to test it, it is the full version, but restricted to 7 or so days). I can't get it to work, and the behavior is very strange. It installs to the standard VST3 path, no issues. The standalone also works fine. When you open Cakewalk after installation, you will see that it scans ADSR Drum Machine, but then claims that 0 new plugins have been installed. And indeed, it is non-existent. Not in the instrument pane, not in the plugin manager and also not in the excluded list of the plugin manager. Sometimes, when you exit Cakewalk and start again, it again scans it shortly to no avail. Drum Machine is simply ignored. But why? If it were a general error, it would have made the round by now. So I assume, that it is something specific to my system. However, 500 successfully scanned plugins tell me otherwise. And so, before going into the painful routine of finding the cause, I would love to hear, if you have it running just fine in Cakewalk on your system. It would then be helpful, if you could provide, how exactly you installed it, and which Win version you're using (I use Win 10 Pro, 21H2, build 19044.2130). Thank you so much!

Will do so, this might help! Regarding the audio interface: I've set all USB devices to NOT go to sleep, following a tutorial. But can that still be an issue? Because on the older 2 PCs I didn't do that.

Trust me, I wouldn't waste your time with lying.

Not sure what exactly you mean. Gigabit LAN, if that's what you meant. No WLAN. Or did you mean speeds?

My machine is listed here with all parts, except 2 additional drives via SATA. One SSD and a HDD. Note, this is my current machine. The older one had an Intel i5, 8 BG RAM, a Radeon 7870, and just one SATA HDD. The one before was an i3 with 4 GB and a HDD. On my current machine I'm running Windows 10 Pro, v 21H2, build 19044.2006 (one update pending), The machine before used the same OS but of course older build, and the third used Windows 7 Latest non-beta, non-early-access version of Cakewalk. Happened with all versions so far. It's not one specific project that's hanging. It happens, as I described, everytime I start a new project and play around for more than an hour. Plugins used vary a lot, VST2 64 bit and VST3 64-bit, at least two dozen different plugins have been active over the time, while experiencing a hang (not all at once of course). Some examples are Synthmaster2, Ascension, Vacuum Pro, Vital, BreakTweaker, ModoDrum, SampleTank4, Orb Synth, Drum8, Sektor, Hybrid, FM8 My audio interface is now Behringer U-Phoria UMC204HD in ASIO mode at 128 sample buffer, but it happened as well in earlier days without audio interface and ASIO4ALL, which I switched to WASAPI when the Cakewalk developers declared it incompatible. Waveform 11, FL Studio Demo, Audacity, Wavosaur, DaVinci Resolve. No. On my current machine I only used WASAPI and now the specific driver for my audio interface (FL Studio installed FL Studio ASIO, which I don't use). On the previous machines, ASIO4ALL was installed.

I didn't, as you can see in my post. I just don't think a program should crash just because it is running for an hour or two. Other than that, I get your point.

This problem follows me since the very first Cakewalk by Bandlab version. I can't say anything about Sonar, as I never used it. However, since I started using Cakewalk I went through 3 different PCs and 2 different OS, and the latest addition of an audio interface a few months ago didn't change it either. This is what happens: I start Cakewalk. I start a new project. I add a plugin, start to play around. When I feel something's good, I start recording. I work on the midi, may have a 4 or 8 bar loop, that I set up. I now run this loop indefinitely. Add another plugin, work a bit. Add another, say, a drum plugin. Working within the plugin, loading a few dozen wav files, shape the drum sounds to my liking. Then all of a sudden, Cakewalk just hangs. I can still hear the loop playing just fine, so no plugin crashed, but the window is non-responsive anymore, and no matter how long I wait, at one point I have to kill Cakewalk through the Task Manager. I also have the impression that this hanging is related to not saving. Because if I manually save the project, the hanging is at least happening way later, if at all. I have autosave active, which I rely on for my projects, and I do save often. But not, when starting a new project. It can take up to 2 or 3 hours, before I think that it is worth saving. My suspicion is that there is some kind of overflow, maybe a limit that overshoots. See the introduction sentence before concluding my system. Also, I never experience this with Waveform or FL Studio, under the same conditions. I tend to see this as a bug, because it is present for years under totally different circumstances. Also, no program should silently crash, and Cakewalk normally does a good job at catching errors, writing a dump file and properly closing itself.

Unfortunately there is no quick way. I'm missing that as well. But I use to switch to the event list view, because each note (stacked ones as well) has its own list entry. Selecting the doubled notes is much easier there.

Wow, that's really interesting. Instead of answering a simple question, you decide to judge the op and talk the question down. And that in the Q&A section. Are you just ignorant and arrogant, or is there also idiocy in there? Thanks for nothing, and good job!

You really shouldn't answer, if my question is already overcharging you.

I would, but I can't hear the track then playing while I edit. I just want the notes in the PRV to be silent when editing them. (so when shifted, dragged, moved, etc.) That is standard in other DAWs I use, but I can't find the option in Cakewalk.

I hope this is simple to answer and I'm just too stupid to find the option. But I'm really annoyed by those crescendos of half-steps over two octaves! I know which note I place where and why. I don't need to hear it. On top, this behaviour is so counter-productive when playing while editing. And finally, many plugins react with stuck notes doing it. So, where is this simple little switch to turn note audition off? I don't care if I have to edit an ini file or go deep into Cakewalk's kernel, as long as the notes remain silent when moving afterwards! Thank you so much in advance!

This did it for me! It's not perfect (loop control doesn't work, and all knobs do nothing), but it is a good start! Thanks so much!

Got a Oxygen Pro 49 yesterday and have the same questions and problems. Join me in this thread, because I think it is the one, most people with Oxygens posted in:

Any more tips from successful attempts? I got my Oxygen Pro 49 yesterday, and since then try to get it to work. I followed @Mike Z's list, but it already broke for me when I was advised to use "MIDIIN3". That doesn't show up. On my settings, I see "USB MIDI", "DIN MIDI", "Mackie" and "Editor". I chose Mackie, assuming it is channel 3. But the automatic ACT entry also didn't show. I added a Mackie entry, which helped nothing. If I add an additional ACT, I can learn the transport controls, and the faders are working as well. But none of the knobs, nor the buttons below the faders (wanted to use them for solo state), the keys aren't working and the pads also refuse to work. If I select USB MIDI, delete all control surface entries and restart Cakewalk, I can use the keys and pads, but none of the other controls. I'm not a technician, I simply don't know about all of that "behind the scenes" stuff (ACT, Mackie, HUI, etc). Isn't there one consistent way to get it to work? It seems so strange, that for some it works by selecting Cubase and Mackie, for others it works like Mike Z described, and yet again others need to select another DAW than Cubase or MPC. My firmware is 2.1.1, btw.

Just a reminder, in case I explained it too complicated, and a picture says more than thousand words: If you have 64-bit engine ticked in the preferences, like in the first picture, there's no need to tick it in the third picture (it is already active). The second picture shows the export formats, that are detached from the 64-bit-engine. If you select 64-bit there, you don't change how Cakewalk works with audio, but export a 64-bit audio file (which will hardly be accepted by any application other than a DAW)

Oh. I see! This slipped through. According the the documentation, this option exists, in case you have your engine set to 32-bit, but want to export with the 64-bit engine. You don't need to tick it, if you already use the 64-bit engine (because you activated it in Edit > Settings > Audio > Driver settings).

Yes, that's what I mean. Exporting to 64-bit has nothing to do with the setting of your engine. You can export to 32-bit and 64-bit (among a lot of other formats). Those two options would be used, if you know beforehand that, say, the studio that does the mastering for you, uses a 32-bit or 64-bit engine in their DAW. It can than access the original data, without converting it. Any audio file you load into your DAW, is automatically converted to whatever format the engine is in. If you run your engine at 32-bit, the 16 bit audio file you load will be converted to 32-bit for use within Cakewalk. It gets out at whatever format you choose to export. Under normal circumstances, you want to export in 16 or 24 bit most of the times, though.