kc23

This is the level of argumentation in a discussion sustained, supposedly, by adults. Ones that seem to not have the emotional control or maturity of a, well, adult. Shouldn´t this behavior be checked by moderators? Are there moderators in this thread? Maybe they are busy somewhere else, trying to get other things in to people´s heads. As long as "nobody messes with MY daw!", guess everything goes. Let the display of... "wittiness"... keep on going.

This is exactly the kind of attitude that made the cakewalk "folk" so famous for. Responses and reactions to posts, with unneeded snobbery, belittlement, and disregard for any other opinion but yours. The "how dare you criticize MY daw and MY views?" stance of a toddler, that is actually the behavior that indicates the... hurt mentality of someone who actually would need tissues to clean... their tears up. 100% agree with this whole post. Just will make, again, the same remark: a "pay 12 months and then keep whatever state your daw got frozen" is not a "pay to own perpetual license". If payment is demanded just for bugfixing it, it is in fact a subscription. Also, despite been asked the question repeatedly, they have been very careful to NOT say that the 6 month authorization "requirement" will be lifted. So I would say, rest assured that it will not, which gives the current version a 6 month lifespan from the moment of your last authorization, or the new paid version is released. Well, actually no. Do you think they have been working for free? They are being paid, it´s their job, and hopefully they like it. But it´s not like they have been doing this "out of the goodness of their hearts." Keep in mind, again, Bandlab is not a little independent company, run by three or four guys in a garage. Quite the opposite.

No, there´s no debt payed whatsoever. Off the top of my head, I can think of at least one daw that is doing lifetime updates, and it has been around for maybe 20 years or so, and a plugin company doing the same for the last seven or eight years or so. So, that business model is real. Anyone that doesn´t see that, well, they can´t see. Again, no. That "12 month payment option and then no more updates" is a subscription model. After those 12 months, one will be left with a daw in the same state as what CbB will be, that is, a daw frozen in time, with no updates, no support. If one has to pay again (and again) to receive more updates and support, then it is, in fact, a subscription. Anyone that doesn´t want to see that, is just deluding themselves.

The thing that has to be understood for everyone is: Bugfixes are not updates. They are fixes. So, if it turns out that on the last release of your so called "rent to buy" scheme, you get a version that won´t load your favorite or most needed plugin (e.g.: kontakt for that cue you have to deliver in two days, or that eq that is all over your mixing session), just because "bug"... you´ll cough up more payments just to, fingers crossed, get a bugfix, so you can continue working? How is that correct behavior? How is that not holding your work hostage? So no, no subscriptions, especially if disguised as a "perpetual license". If I would be willing to pay upfront for 12 months of updates, I would expect, at least, a new feature once a month. At least. And new. Bugfixes? not gonna pay extra for those.

"if your subscription stops, keep using the program... you just don't get any updates" it´s not "rent to buy". That is a subscription, plain and simple. So, they want me to pay for a program, and when bugs are found, they expect me to pay them again for me to get those fixes? Pay them to get the fixed version of the thing I already payed and that was faulty to begin with? pffff... I would say that definitely qualifies as holding your work hostage. And I also would say, that in daw-world, the best business model in my opinion goes to Reaper: "Pay your license, whichever of the two tiers corresponds to you, and we´ll give you every update we roll out until the next mayor iteration comes to an end." And those updates come with fixes and new features. And, the program is the same for everyone. Either that, or lifetime updates. But... yeah.

They keep throwing these veiled confirmations that, indeed, what is coming is a subscription model. For which a lot of people here keep saying is not what is desired. Comparing a daw with a car? To justify a subscription with the same arguments as corporations wave when dismissing your right to really own what you pay for? Just because people have lost perspective on the entitlement of a business over the reality of what you allow them to do, does not mean it´s correct, moral or ethic behavior. Remember, Bandlab is not a little independent company, run by three or four guys in a garage. Quite the opposite. So no, to whoever said "100% of people here agree", it´s just not true. And also no, "rent to own" or "perpetual license" is not "buy a 12 month upgrade plan", which actually is a subscription in disguise. So far, the only "new" thing offered seems to be this vector based gui. But for the rest, it´s even been said it´s going to be the same, all the way to the base code, which has been used countless times as excuse for not implementing very long requested features that are granted in other daws. Even things that were introduced by cw, and then left for dead. Remember multitouch support? Not a single change nor development since it was introduced in the win8 days. Not one. As someone asked, what then is the new value proposed for the asking price, whatever it will be? So far, not much in my opinion. And you want people to pay periodically? Also, I see the general attitude here is the same that made the old cakewalk forum famous for: "If you question this daw in any way, shape or form, you will be berated, shamed, belittled and thrown out of here... how dare you?!?" I have run in to this a couple of times, and there´s not much to argue against that narrow mindset. It seems times ahead are certainly not rainbows and sunny days. BTW, to those that payed for lifetime updates (even older cw versions, from sonar x2) and still keep proof of purchase, it can be used for crossgrade discounts for Cubase and for StudioOne. So, even other software companies are still willing to, in a way, honor that. Just so you know, to keep things in perspective.

Well... I was among the ones that payed for the lifetime upgrades, not just to support the software but also to not be tied up in the awfulness of a subscription model. The arguments trying to justify not honoring this are not valid in my opinion. Yes, gibson was another company, but the developer team was the same (a.k.a. "the bakers"), and they did benefit from the "fruits of my labor" when I bought it. In my view (being using cakewalk for more than 25 years), to honor that in some way would be, in the least, a sign of acknowledgement to that user base, which most likely has been the most faithful and supportive through all this. Also, I´m sure this news mean that, at least in CbB, we won´t see some things have been requested since more than 15 years ago, like fixing the external insert plugin and negative delay in milliseconds for midi tracks. Which makes me even more doubtful as to if I´ll keep supporting and using cakewalk (so far, I´m no longer mixing in it, and already starting migration of midi composing to maybe Cubase). Let it sink: fifteen years of users requesting these fixes (yes, fixes because functionality was not complete and broke correct usage of other assets), and at the most the answer received was "it´s not high in our priority list". So, to me that says a lot. Just to get perspective, when the negative delay was requested for Reaper in a forum, it took them a couple of months to implement it and roll it out in an update. And for the people thinking about migrating, there is a "plugin" for Reaper (developed independently) that allows opening .wrk files. It translates almost everything in a session, even replacing some of the prochannel modules with Reapers´s stock processors. Google it, it´s not hard to find. For me, this most likely will accelerate my migration process and end for good my run with cakewalk. Which, to be honest, is kind of sad thinking of what this software could have been.

Hello In the release info for 2022.11, in the Bug Fixes section, it says: -Regression: Mono hardware outputs always output as stereo Does this mean that, at last, the External Insert plugin has been fixed and it will recognize a mono output without hijacking the whole stereo pair? Hopefully, it does.

Almost two years have past since this request, and so many people adhering to it. Plenty of updates to other features, but nothing about the necessary support for true mono send and return for the external insert plugin. It was mentioned that because of CW´s support of multiple driver modes its "harder to do". But it certainly can´t be impossible... so many other daws have support for multiple driver modes, and yet they have had true mono external send and returns for so long. It was also said that it was "lower on the priority list" a year ago. It would seem that some items in that list are simply not moving upwards in the cue, as so many other things keep being updated, but not a fix for this in sight. Again... please address this. After almost fifteen years of the external plugin being introduced, it´s due time for an update that fixes it and brings it to a contemporary standard for serious mixing duties. Hopefully it will soon.

Indeed, truly disappointing. More so when something that should be considered an essential feature doesn´t get acknowledge by the developers. Please, give as an answer as to what to expect. Will it be implemented? Is there a timeline? Or is it simply not seriously considered, even after so much time and almost every other daw having it implemented? This feature is essential for anyone trying to do any midi programming. Is not only a thing with orchestral libraries (in which it is indispensable), but with all virtual instruments. A midi-tick based approach is just not workable. Hope this gets an answer.

This feature is absolutely necessary. It´s no use having it on a midi tick basis, as the absolute time would depend on the tempo of the piece. Libraries that need this require a consistent time offset, set in milliseconds, regardless and independent of the tempo. No, nudging does not help, as stated by other posters here. Every articulation within an instrument usually requires a different offset time. Indeed, that´s why so many other daws have it, like Cubase, Studio One and Reaper. It took Reaper one minor update to implement this. How hard can it be for Cakewalk to implement it? It makes CW almost useless for setting and orchestral template. Sadly, these are the things that keep me from fully returning to it. Guess we´ll have to see how long it takes to be implemented, if at all.

This is a request that has been made for several years now. Sadly, it was never acknowledge, until almost recently, when the answer was that it was "lower on the priority list" because "Cakewalk supports other driver modes that have stereo channels so it makes it harder to do". A program like Reaper (which I have had to start using more and more because of this problem) supports WDM, WASAPI and ASIO driver modes too, and can handle true mono inputs AND outputs. So, its not like it can´t be done. Updates keep coming and coming, and this issue keeps getting left out. So, after so many years of requests, I wonder how long is the priority list for this to be so low? Will we ever see it solved? Hopefully more people will join in this request... besides all those who already have over such a long timespan, including the ones that have fled to other daws in search of this feature alone, which is indispensable in a professionally oriented mixing platform. Anyway, here is the thread from which I´m quoting Noel Borthwick:

Indeed, driver bit depth is NOT the same as audio file bit depth. To OP: You need to go to Preferences/File/AudioData and toggle the File bit depths as needed. If your audio files are 24bits and the Import bit depth is set to 16, cakewalk is converting them to 16. If Import bit depth is set to Original, they will still be 24 even if the Recording bit depth is 16 (which makes the transport show "16").

It is necessary to understand correctly signal routing as a universal concept, and then understand how the tool at hand (in this case cakewalk) functions, to make these kind of things work as one wants. -A send is a send. It SENDs audio to where ever you want it to be received. It can be a bus, or a track (used as an aux track in cakewalk). In analog, a send does not need a dedicated "return", you can return it to a bus (if it has an input port) or a track, as you can do in cakewalk. -In a patchbay, a mult is the result of an input being duplicated in a given number of outputs. You would have to patch the output of a track to the mult input, and then the outputs of the mult to the inputs of the tracks you want it to be duplicated at. In cakewalk, if you want a track´s signal to be received by multiple other tracks (thus creating a "mult") then: set the output of the track to a patch point (the "mult input"), then in as many tracks as you want, set their inputs to said patch point (the "mult outputs"). If you want to receive that signal also on a bus, send it through a... send, having decided for it to be pre or post fader. Understanding the signal flow and the software´s functions, this should take a couple of minutes to figure out, and another couple to experiment if it will work. Hope it helps.

Sadly, I can see this as being an inevitable path for everyone that would like to use CbB as a serious hybrid mixing tool. We will all end up migrating elsewhere. So far, for me reaper seems a viable alternative, it can even open most CbB projects directly. Would rather keep supporting and working in CbB, though. But it just won´t be possible. And also sad, is that the problem is still not being addressed by anyone on the developing staff. Again, this has been going on for more than thirteen years. Multiple request have been made in this time span. Not a single serious response from anyone. Not a timeline, nothing. Lots of other features that cater for composition and midi work. Lots of other requests get responses and feedback from developers. Barely nothing for audio work. And lets not get started on multitouch support, GUI resizing support, routing menu organization, and some other stuff. Remember, when Cakewalk made the jump from only midi, it called itself Cakewalk PROAUDIO. I wonder were the PRO part went, as it seems to have been left behind for the serious audio work.