Misha

"Bandlab has something to tell us, they will" Terry, you probably didn't read or understand my post. FAQ changed recently and I am asking someone from the team to clarify what is the meaning of new wording. I am not asking users for opinions on this, as your reply suggested.

A year in waiting for news on non-subscription Sonar passed, without any hard Yes/No evidence except for some, almost invisible sprinkles offered by Noel. Which is sad. However.... I see that the FAQ changed on Cakewalk.com. The wording of discontinuation of Cakewalk by Bandlab are no longer there. What does that mean? Do we get to keep Cakewalk by Bandlab? Will it require re-authorization every few months? Is it on a chopping block (as original FAQ hinted) after Sonar release (whatever that might mean)? Perhaps bakers can explain what is exactly is meant by: "Is Cakewalk Sonar replacing Cakewalk by BandLab? Cakewalk Sonar builds and improves on Cakewalk by BandLab, offering advanced technology, effortless workflow, and an interface that amplifies inspiration. However, Cakewalk by BandLab will continue to be free without a subscription requirement. While the software will continue receiving essential maintenance updates, no new feature development is planned as we prioritize advancements in Cakewalk Next and Cakewalk Sonar." Thank you.

Craig, I am not going to pretend that I know the "reasons". That what it seemed to me - companies tried to grab as much runaways as they could in 2017. If it was much more than that and had higher meaning, great. Here is a counter argument (and perhaps BL marketing would like to hear this too) Out of all people I've talked to (7 or 8 outside this forum, that were longtime Cakewalk users pre 2017 and switched DAWs on Gibson saga... I know only one that "came back" using Cakewalk and not even full time. Not because Cakewalk was "bad". They all loved it. They lost trust. The year long silence in my view doesn't help Bandlab's image. From my reading / understanding Meng Ru Kuok is not only corporate entrepreneur, but also a visionary and a music lover. I just can't understand why create unnecessary tensions & frustrations for fellow musicians that have valid reasons to be worried. Bottom line is this. I am willing to wait another 6 months or even another year if I know for a fact that new Sonar will be available as non-subscription within that time period. If they are still unsure, this should be stated in some kind of "nice" words that make sense, so people can plan ahead . "Coming soon" is not it. ----- Larry, I hear you. Unfortunately (or fortunately) specific "tracking" take lane workflow I am after is only available in Cake. I have tried about a dozen DAWs. A couple came close, but not there yet. If it comes to switching, I will have no choice but to adopt. It's life

I am certain vultures are important animals in the world's life cycle and have no issues with them, or their instincts, but: "bail out" abandoned SONAR users were hoping to gain some new users" - certainly seems like a prime reason for the gesture. Even if there was more philosophy to it, it came as a bonus. In my view there is a very stiff competition between upper dozen of popular DAWs. Lucky you (no pun intended). I was not that foreseeing. I am grateful to Mr. Meng for keeping and advancing Cakewalk all this time... I am. But now, unless they release non sub Sonar or clarify of near term plans for us, silly users, it's same fork of 2017 for me. This time it would be darker, because I will stay in the same 2017 spots, but now with over 100 projects added. -------------------------------- I am a slow learner. I estimate, it will take me 200-300 hours to get comfortable with another DAW and likely 500+ to fully adopt and start liking it. With family and work, free time is a big luxury, so just grabbing and learning another DAW is a tough call. I believe clarity is not too much to ask for from Bandlab. Especially now, since I do have more time in the summer for ventures like learning another DAW. I do spend a few hours every year test driving different DAWs there are a couple that I like. P.S. I was sincerely hoping they would release non-sub version on 1 year anniversary since announcement. They still have a few hours, but I doubt that will happen today.

"totally disingenuous to tar Bandlab with the same brush." Well, they have to prove it. Providing years of development, just to say it will be discontinued giving NO details in a year (!) time for NON subscription options, erodes 75% of the trust they gained in my book. "Coming soon" banner hanging for a year will not cut it. Near future CLARITY please.

Craig, that's an interesting take, but I will hold of my reply till tomorrow - a "One Year" anniversary since announcement

As mentioned earlier in this thread, tomorrow will be exactly one year since the "change" was announced. Could it be that tomorrow "anniversary" will be the day of release? That would be sweet... However, my patience is running extremely thin. A full year after announcement to come up with pricing or at least approximate "release" day/month, is more than enough. Why marinate those folks who are not interested in subscriptions?? Seems a bit cruel. It would be OK if they stated that Cakewalk would be yours to keep regardless how they decide to offer Sonar, but since it was stated that it will go away... Feels a bit like like dejavu of 2017. Fortunately or unfortunately Cakewalk has a very particular "takes" workflow that for now is only available... in Cakewalk. The unfortunate part is that 2017 version had a bug (that I reported during Gibson time) that was only fixed in Bandlab's version. So if SHTF, I will end up using 2017 with that particular bug until learning another DAW. Hopefully it will not come to that. I guess, the main point of my reply is this: Bandlab, if they care about integrity, keeping trust of people who didn't leave in 2017 when vultures were offering sweet crossgrade deals on the former Cakewalk forum, should either release Sonar ASAP or the least offer clarity if normal licenses are expected in near future, so people can make informed choices. P.S. If you leave the Cake in the oven for too long, it will not be edible and people will Walk out.

If it only relates to a single project, you can try opening it the way it worked for you and try to save AS in a different location. I can only think of 3 instances if you eliminated sick plugin(s). a) Actual Cakewalk file is somehow got corrupted (Saving As resolved issues for me in some instances, not only in Cakewalk) b)File location has some permission issues c) One of your Audio/Midi files is corrupted. P.S. Not sure about this one, but once you have project running, you can try saving it as Bundle file and then try opening it. If you can open it successfully, re-save it as normal.

Not the first one.... Kind of a brutal & autocratic way of selling the sizzle, but not the steak. (There is a person that comes to mind that locks people up for speaking out) But hey, it's their reputation at "steak", not ours - dear loyal followers > future customers.

I love Cakewalk, but whoever stands behind the decision of not publicly releasing basic information on future licenses & release time frame (season/year?)are just acting a bit distasteful and cruel. Most of us here remember 2017 very well. And also remember that it was said that Cakewalk will be free. I am pretty sure most of us stayed not because of the "free" factor... I see no benefit of keeping folks in the dark for so long. All it adds is repeated anxiety of 2017, especially when death of Cakewalk was announced some time ago in FAQ. I just hope it will be a Happy Death with reincarnation of shiny Sonar perpetual licenses available at fair prices. P.S. I recently installed my last Gibson Sonar version, everything is working fine.... A few bugs unfixed in that version do annoy me, but not to the point to be depressed or sign up for subscription. I am glad I have this plan "B" which should last for a few years if things go sour with BL.

That is one funny Etsy seller Yeah, they definitely should consider amending that Wiki page. Today, we are one month shy from 1 year since initial Sonar/Next announcement was made. I hope there will be some clarity given within the next month.

David, I think there's a some kind of bug with that 4track "factory" template, I have no issues when I use the one I that mainly use. Expanded or not, my custom template works exactly how Record options are set. No surprises.

57Gregy, Thanks for clarification. I've done some digging and it seems happening with a generic (factory) "4 Track template", which I use rarely, but is (was) a quick way to do sketches. I've used my custom template that I used for 3+ years and it seems issue of Take Lanes merging is not present when using it. Another strange thing was... It was merging everything to Take lane #1, so for testing purposes I deleted that lane (with content). Well, on the next rec take it created Take lane #1 and placed it on the top. Ohh well. My guess, BL will keep Cakewalk alive for at least several months, after the BIG announcement. If perpetual licenses will be offered - smooth ride, previous and current Cake projects are opening fine in new Sonar and it doesn't have this merge issue. If Sonar will be subscription only, it should give me enough time to finish a few projects that I've started already and move on. I will not investigate deeper as I found a workaround (using my template), but will not mark this as resolved as the issue is present.

John, thanks. So there's no way to revert to previous build? "It must be something else." With rec settings: >Mode: Sound On Sound., Take Behavior: Create New Lane with New Takes on Top "checked". And only the parent track armed, it should not place new take lanes on muted lanes at the bottom. Last time that was doing that was under Gibson, until BL took over and Noel fixed it in the first couple of months. It also seems it's inconsistent. Sometimes it would create a new "take lane on top", sometimes merge to muted. So just by observing this behavior it's a bug in my book. I am hoping I can go back to previous build, so at least for sometime there would be a working copy on my computer until they sort out the things with Sonar licensing.

Installed is 2024.02 (Build 098) One of my favorite features in Cakewalk, "take lanes" seems to have some sort of bug that I didn't experience since Noel fixed it around 2018... In record options I have: Mode: Sound On Sound., Take Behavior: Create New Lane with New Takes on Top checked. Sometimes "take" recordings works like it should/did for years, some takes are merged to muted lane on the bottom. Very inconsistent. I have no desire to troubleshoot this as likely 2024.02 might be the last version. Is it possible to revert to previous version, so I don't get stuck with final version that has a major issue (for me) or this is the end of the road? Thank you.

"stressing over things out of our control is truly a waste" Yes. Stressing things that cause dissatisfaction of perspective paid customers and questioning strange / delayed release tactics is OK. So the company is aware that some are not happy about this and have a valid reason to be concerned. I don't view this as "circular" debates, but a reminder. Some companies tend to care what users have to say, some don't. I have no illusions about it. I think it's simply unfair to keep in the dark those who put trust in the company in the last 5 years. Those who could of learned different DAW in that time, but decided to stick on the premise that Cakewalk will be around, which seems is not the case going forward. I am not getting younger and it will be more challenging for me to get used to another DAW than 5 years ago. Subscription model is out of the question for me. BandLab please define "COMING SOON" P.S.I have this strange feeling that BL is at crossroad at this time. They can make things amazing (which I am sincerely hope for) or take path of companies like Reason, Waves and a few other murky players. I guess we will find out "SOON"

Noel B said: "Yes there are plans to have purchase options outside of backstage pass which was intended to be the quickest way to get it right now. When details of it are known it will be announced." I interpret this, as there will be perpetual licenses available, same as with 90%+ with all other DAWs. Why would it be different? I believe the wait game does not benefit BL, especially considering Gibson fiasco. They need to show they are different (better), particularly since coroner pronounced the death of Cakewalk. CLARITY ---- "No we ain't dead" That's a good thing.

"I won’t be shocked if I never get my perpetual license. " "I am part of the user base that’s fading away." I disagree for 3 reasons: #1 - Noel confirmed there will be "other" ways to get Sonar. #2 The "fading" base is still relevant for foreseeable future. #3 Most DAWs, even "beatmaker" centric FL Studio, all sell perpetual licenses. ----------------- My take, a BIG announcement should be made before June 16, marking a year after the public announcement, otherwise it would be very strange. Just speculating. I do see that Bakers are working hard, polishing and adding features to Sonar at a very impressive pace. Hopefully unveiling will take place shortly.

Heath Row, So the next upgrade will cost to you another yearly subscription. Not cheap, but fair if they have something to show for it. If Sonar will be priced similarly, I will gladly get it, and for example if next year they will come up with a clever Chord Track, I will upgrade again. And so on.

Steev, Ohh, I am patient. (a user since late 90s) Been especially patient last 10 month since Cakewalk death sentence was announced and coming "soon" wording was stapled I am not worried about licensing, as different options were mentioned to be available. In my view delay and unnecessary secrecy of release simply frustrates people. Also seems BandLab doesn't move fast enough to capture DAW audience it needs, while others do. P.S. If BL offered similar deal to Studio1, I would be first in line. In a sense I am glad that S1 done this promotion. Hopefully it will ring some bells to speed up release of perpetual Sonar licenses.

While I will not sign up for subscription only plan which is the only available plan at this time... I do checkout new features and workflow on un-activated copy until proper licenses will be available. From the last set of features, I love that you can change custom display scaling independently of Windows, right in the program without restart. While it says "experimental", it seems to be very stable. Great that mouse cursor items were fixed too! I wonder how hard it would be to have a custom font setting to "thicken" text/fonts without touching display scaling? To me fonts are a bit too fine.

Sorry if it was asked before... New Sonar seem to add a node in automation (volume, gain, etc) by double clicking - Cakewalk adds a node on a single click. Is there a way to change Sonar to get add a node from single click? P.S. Maybe double clicking is "natural" to some, but I find it counter productive to have this as a default setting in new Sonar. UPDATE: Must of been a glitch of some kind. Maybe a shortcut triggered dbl click behavior? Restarted Sonar, everything works as expected. Single click adds a node!

Seems S1 is also listening to the ground.... Tempting. C'mon BL. 10+ month is not "coming soon". Child is born in less time. Time to roll out those perpetual licenses. We saw the goods, we want them. No falling asleep. Your competitors are pretty much awake and alert

Seems OP was able to get away without ASIO for years. Hopefully this was just a glitch for him. Different Cakewalks for different folks.

Frequency / bitrate mismatch? ------ "except Chrome" that might be a boo boo. For testing purposes I would try to avoid using any "browsers". Did you disable FX globally (FX button on upper bar) or individually? Some synths like Sonic (Halion) had given me headache in past few years because of it's license manager. Would hang Cakewalk completely. I believe they fixed it last year, as it was working OK since, but if you have older version... or similar synth in project that calls for "something" that might be issue too. I've given up on Waves plugins mainly for that reason. Make a copy of the project, so you can use it as a sandbox to pinpoint issue. I would start by deleting first 1/2 of the tracks with their FX straight down (on a copy of course). If project plays, do Undo, grab first 1/4 of the tracks.. delete, etc. Deduction.