tulamide

As long as you don't confuse a complete list with the recent updates that you linked to, I'm fine with whatever your view is.

I love that you share your experiences. Thank you very much for it. I will make good use of it. For example, if it turns out that your experiences from 2015 are still valid in 2023, it will be a warning sign for me regarding Studio One. I also see that we have different demands for a DAW, which is just natural, but allows me to set your experiences in context. Which is also important. And without going into details (I don't think, this thread is the right place for it), I just point you to the fact that CAL is deprecated. As long as it runs on current OS versions, it will be part of Cakewalk. But it won't be updated nor bug fixed anymore. Thanks again for the valuable information shared here!

Interesting. I come from another perspective. I chose Cakewalk, when it became free software. The reason was simple: It was the most versatile free DAW. Ardour? LMMS? SoundBridge? The other two, often titled "free DAW", while they are actually not, Reaper and Waveform, are as versatile, but for me personally too difficult to handle smoothly. Why I chose a free DAW at all? Because for 10 or so years, I was using Cubase. It became unbearable for me to pay for a DAW, then for any update and, of course, any upgrade. All that money (in the thousands) for just one DAW. I had enough, and went the radical other route. Now that Cakewalk in the form of Sonar will become a paid DAW again, the game changes. If I have to pay for a DAW anyway, I will carefully check my options. Because on the paid market, Cakewalk simply isn't the most versatile DAW. Bitwig, the full version of Waveform, Studio One - they all are more versatile. Currently the only pro argument is that I know Cakewalk so well. In the end, it's therefore simply the price, that will decide it for me. If Cakewalk is cheaper, I will buy it, because I then know my DAW. If it is on par with the likes of Bitwig or Studio One, I will buy one of the latter. You see, there are no feelings involved. I'm not a fanboy, wether Cakewalk or any other DAW. It's just a tool. And if I think that a price for a tool is adequate, I'll buy it. But only then. I also keep an eye on the free market. Anthem looks promising. They use the Tracktion Engine (the audio engine, Waveform uses), which is open source, but design their own UI, tailored for modern producing needs. I don't expect it being released any time soon, but when they do, I'll just see, if it is versatile enough to suit my needs. Wether paid software or not, is unimportant for me.

My statement after having thought for a few hours. Please understand, this is just me, one of many users, telling you what I will do. Don't argue, it isn't worth it. I only share it in case, other users might be just as confused as I was regarding the commercial aspect. It might help some people, to get a view from somebody else, or it might not. 1) I'm not interested in Next. 2) I'm basically interested in Cakewalk Sonar. 3) CbB is a fantastic free DAW. In fact the only REALLY free DAW. 4) Rebranded as Sonar and sold for whatever price, it is just one of many commercial DAWs. 5) If the offer is subscription only, i'm out. I personally have no interest in that in general. 6) If there is a one time payment that is higher than Reaper, I'm out. The reason for this decision is simple. On the commercial market, I compare carefully my options. And if I have to pay anyway, I will go with the one that has the newest codebase. That ensures it is a fast DAW, with faster bug fixes (because the developers don't need to dive into 30 year old parts of code) and better future proof. I will use the next year to slowly transfer my projects to the new DAW and then look forward. Subconsciously it might also play a role, that I don't feel good with Noel's aggressive and almost arrogant defense of subscription services. It signals to me, that the devs are on another mindset than me. That is understandable, but it makes me uncomfortable. Again, this is just what I, a small little user, will do. I don't try to convince anybody to do the same, nor do I suddenly think bad of CbB. So please be friendly.

Not sure, what direction this goes, but of course. Which in the case of the company Teksonik obviously refers to would mean, that you could have bought it in 1997 and will still get free updates on version and features. Pretty impressive.

What I expect from a free software: Nothing. No, really. Yes, I have wishes for features, but I take whatever is offered and am thankful. What I expect from a paid software: Full licence ownership from day 1. A one time price to pay (maybe rent-to-own). Free error fixing updates. Strict seperation of core product and expansions, to see exactly what you get for your money. No subscription, no matter how it's designed.

Plus 1 for Scook, I also always use the inspector and it is very easy, fast and versatile. Lasso select (or use ctrl to add more notes either by clicking or lassoing) and set a relative/absolute value to change all selected notes at once.

Last time I counted, it were 14 that are known. Plus those who currently develop without having announced anything yet. There's a list somewhere on the web, you can read through. So, by dozens, I mean dozens.

Interesting answers to my post. I summarize: "I have no fear, I just don't want it." I still fail to see any sense in posts that try to explain why it is good, or even better, that Cakewalk does NOT support anything else than VST. There's also little understanding of the CLAP format in some replies. CLAP allows any plugin to adapt to hardware and scale with it, unlike VST. That's just one example, of course. In VST, the hardware must support a specific standard. If it's there, the plugin runs, if it's missing, it doesn't. And that's it. If the hardware has more potent features, it is just ignored. CLAP otoh uses more potent features when present. The result is less CPU load, more stability, and a plugin that grows with your hardware. Win-Win. It's things like these that make CLAP a much more interesting format than VST. And once again: Nobody takes your VST plugins away. CLAP plugins just come in addition. And in regards to the Cakewalk devs. Yes, I'm sure they know about CLAP. That doesn't take away that we can express our wish to support it. Just like you suggest features, I suggest CLAP support.

I wonder, where all this fear of another plugin format comes from? It's not as if it would hurt you in any way. It's just a plugin format. And about the effort needed: Reaper needed a few weeks to implement CLAP support. Fact is, that Steinberg currently dictates, what a plugin can or cannot do. That's why developers started other plugin formats in the first place. CLAP and LV2, for example, have the same basic concept. Allowing a modular approach to extend capabilities with extensions. No DAW is required to support any of those. It's a bonus, not a necessity. But by being afraid of a format, that developers of instuments and effects designed to specifically allow more functionality, less CPU usage and a leaner programming, you actually prohibit those who want to give you these better products. The more DAWs support CLAP, the more CLAP plugins you will get. Of course, the whole U-He package and dozens of smaller developers already offer really good plugins in CLAP format and some even CLAP only. So you don't want variety, just because of a diffuse fear of a plugin format. That's strange.

Cakewalk, as a free DAW, should support at least one free plugin format. Therefore I would love to see support for CLAP in Cakewalk.

I don't have a Stream Deck. But naturally I would ask, if it is able to record and run a macro? That's the only way I see to get it that deep into Cakewalk.

I have an Oxygen Pro 49 controller, and normally have no issue. I have it set up with Mackie in Cubase mode, and everything just works fine. Until today. I don't know, what exactly I could have done, but it must have been something I did, because all of a sudden moving the modwheel ignores the current active track and instead moves the level of the master bus between -inf and -70 dB (so, silence). This is bound to a specific project, and therefore not breaking too much, but I would like to know how to get rid of this connection between modwheel and master bus fader. It might be some kind of ACT learning issue? Or another kind of accidental binding? How do I get rid of the binding? Where do I find a list of all bindings?

That seems to indicate, there's something wrong with your drivers (outside of the music world). You have a GTX 1650, which not only runs OpenGL just fine, it also takes away the load from CPU threads busy with GUI stuff. Make sure you have the latest drivers, installed manually, not via Windows! That goes especially for your graphic card. FYI, OpenGL is an API, just like DirectX or Vulcan. The app just instructs the graphic card using this API, and all the graphic work is taken away from the CPU and brought to the graphics card. That you have a better performance with plugins' OpenGL disabled points to a software renderer used (which is done, when no graphic card is found). But a software renderer for OpenGL is actually more demanding than just using GDI+ (the normal software rendering, Windows uses).

I might misunderstand the question, in which case I apologize. But, are you aware that there are several things that stop scrolling? Clicking in the view, for example, zooming in on the time ruler, and more. For the latter, right clicking the time ruler continues scrolling.

This should not happen. It should continue to play at its internal tempo, getting cut when a new clip comes, etc. But not just glitch unpredictably. It sounds like your PC can't handle the load, which can have many reasons. If you've set online rendering to the quality of offline rendering, for example, or (I think we can rule that out) a too weak processor, or too many background tasks, or a defective driver of your audio interface. By default, audio clips always use their internal tempo and don't follow tempo changes. You have to activate this behavior first. Many use AudioSnap for this. If you want to use that, you should however always check the popup menu that says "average tempo: " Sometimes it couldn't successfully detect the actual tempo it was recorded in. If you then set it to follow tempo changes by activating "Clip follows Project", the results will of course be weird. So make sure, AudioSnap uses the correct original tempo of the audio clip. If you can't, you can follow John Vere's video, which will make sure that the clips definitely have the correct tempo. But remember, allowing audio clips to follow tempo changes introduces realtime rendering: all audio has to be stretched with heavy calculations involved to preserve formants (otherwise you would end with the Micky Mouse effect). On my CPU, a Ryzen 5 5600G, I can set the realtime quality equal to the offline quality without issues, but I also never used it on more than two tracks at once. It might be neccessary to lower the quality for realtime rendering, to avoid problems.

Thanks for the quick answer. However, I said in my post "when one of the two instruments involved have a midi out option (for example SynthMaster 2), although its use not activated" It just reacts as if. And it only happens (so far), with VST3 instruments. I want to emphasize this, as your screenshot shows a VST2 plugin. I also heard from two other users with the same issue, over at the Cakewalk user group on Facebook. - VSTi only - VST 3 format only - MIDI out option exists, but is NOT activated - MIDI echo is only active on the track that's armed for recording (and it's the only track armed), yet the recording goes to the other track.

Yes, as the title says. It is a wierd issue, that I only have since the last update (which to my knowledge did no changes to midi input). Sometimes, when trying to record, the recording is done to the wrong track, and 2 plugins react simultanously (example, you record arm track 2, midi echo is auto on, track 2 is selected, but recording is done to track 1 and its audio played in addition to track 2 audio). I'm still trying to isolate the issue. It may be a coincidence, but so far I noticed this, when one of the two instruments involved have a midi out option (for example SynthMaster 2), although its use not activated. And I use VST3 synths only. As a workaround I can set the falsely reacting one from "all inputs" to "external input" (choosing my controller).

While most VST3 plugins work, there are some, especially those using the newest SDK, which fail to load. Ronan Fed's plugins, for example, or ADSR Drum Machine, and some others. It seems that mostly synths are affected, I couldn't pinpoint a VST3 effect refusing to work with Cakewalk right now.

There is no input to the effect. When freezing a track, it does not run the whole project in some magical way. It runs only the track enabled for freezing. No midi arrives at the effect, thus will not be trigggered.

Thank you! The setting I didn't find! The image makes absolutely clear where to find it. Thanks again!

Hi, there's this one problem, that I can't seem to solve. I'm pretty sure it's just a setting, I can't find. If you can help me and would provide images, that would help so much! Imagine the following scenario: You record a few notes that you play with your controller. The individual notes have different lengths. You have snapping enabled and it's set to 1/16th. If I now drag a note's right border to extend the length, I would expect it to snap to the next 1/16th. But that's not happening. Instead it adds exactly 1/16th to the length, resulting in me having to manually cut the note to end exactly at a 1/16th. In numbers this is easier to describe. A 16th length is 240 ticks. My note is 24 ticks long. When changing the length, I want it to snap so, that the note length is 240. Instead I end up with a length of 264. If there is a setting, or a modifier key, that helps me reaching this goal, please help me Thansk in advance!

@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.

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.