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.