Jump to content

Recommended Posts

11 hours ago, Teegarden said:

You regularly report bugs, which is great. If those 10+ producers also report those issues each time they occur CbB will soon become a DAW outperforming in stability (as far as is possible with the infinite number of different hard/software installs and projects...).
From what you can see on the forum, issues directly reported to the bakers are handled fast and well (I've got the impression the last few months even more than before, maybe because after introducing large very welcome additions, there's now more focus on the lasting bugs?) so if your friends participate that will be for the good of everyone. 

Thanks @Teegarden 

Yes, I try to bring my part. Like I've said: It's because I'm one of those handful that started their careers with Cakewalk. Handful meaning: Cakewalk being the 1st DAW I have touched. 

but, I'm one guy out of 18 guys I know and work with / AND / they all have their own guys they work and collaborate with on their own production. So if you put this under that "Pyramid umbrella chain thing" I can easily be part of a 1000+ producers underneath this chain. So it's difficult to get everyone to report here. Those I am close to, them I can't force if they don't want to. 

Try telling someone whom has been longer than you in the business and only starting out with cakewalk since it became free, to support the brand by reporting the bugs. You'll hear the answers you get. 

Now here the the thing: You that's forcing to look into Cakewalk to just try it out - that's promoting the product. Now come up here to report or give feedback and get answers like this - it gona start raising some questions like - why should I care about cakewalk anymore when I'm just here to help, but het answers like this in return? In return you also just dont care anymore. Coming on the forum with the mindset: If I report this they gona blame my system or windows or my workflow.

That's exhausting. 

Share this post


Link to post
Share on other sites
Posted (edited)

I think it's a shame that criticism on the CbB development always gets that emotional! 😄

But on the other hand I felt sympathy for the concerns of @loqand @Will_Kaydo, though I refuse the provoking tone of their complaints! I agree that there are still a lot of issues in CbB (although I rarely have crashes), e.g. clip manipulation in take lanes is nearly impossible that's why I always insert a working track that is empty for clip manipulation! This works so far! Actually I had also preferred more bug fixes than things like the Arranger and Articulation Maps, though I agree with @Noel Borthwick that it's impossible to satisfy all users (especially such ungrateful ones like me 😆). If I go thru the bug fixes in the last couple of releases, then I also see that many fixes are related to the new features!

But after all I see it positive and hope that the new release is a turn and it will bring a lot of long awaited fixes! 😄

Edited by marled

Share this post


Link to post
Share on other sites

>>If I go thru the bug fixes in the last couple of releases, then I also see that many fixes are related to the new features!

This is completely normal to the way we work. When we release a new feature we continue refining and making it as solid as possible before moving on to the next area. We also tend to fix issues by category. In every release we tackle areas like Plugins, editing, UX, workflow, performance and stability. So there is something there for everyone and the product gets better in every release.

I’ll be the first to say that we still have plenty of room for improvement despite the fact that focus has been very high on making the product more stable since 2018. We look at the forums social media groups but the best way to get attention to problems and solve them quickly is to write specific and demonstrable reports of problems encountered, include a project file or video demonstrating the issue (if necessary) and include dump files if the issue is a crash or hang. And of course send the case to support and get a ticket to follow up. Following these basic steps has a much greater effect than making general statements like “I run into issues on every project”, etc. Not everyone has the time to do this, but if you care about getting issues fixed this is the only way.

  • Like 8
  • Thanks 2

Share this post


Link to post
Share on other sites

When I plug in a midi device after starting the DAW, I get the popup to add the new device, but when I click yes, it still never appears in the list of devices in preferences.

  

Share this post


Link to post
Share on other sites

video view disappeared in version 2021.01 build098, and doesn't work even if I right click on "open video view" on video track. "version2021.01.build098.png"  shows video view is absent in build98. I've got another machine installed an older version of cakewalk sonar "version23.10.0.build14[2017.10]" shows video view is exist and works. 

version23.10.0.build14[2017.10].png

version2021.01.build098.png

Share this post


Link to post
Share on other sites

You are using a workspace that doesn’t show video view. Choose a different workspace like advanced and you will see it.

  • Like 1

Share this post


Link to post
Share on other sites

I have the same problem with CbB/ Kontakt. I don't know where the problem is exactly, I have tried basically everything to fix it but no joy. The strange thing is that this problem with the Kernel. dll crash is that it's only in CbB, it works fine in FL Studio and Reaper. The only solution I could find was to use Reaper as a rewire device but this shouldn't be. Kontakt have been working fine in CbB up to about a month ago, then started crashing at random. Now it won't open at all. I tried reinstalling both CbB and Kontakt but still not working. Just wish there was a simple solution!!

Share this post


Link to post
Share on other sites

I've used Kontakt for years with CbB and Sonar. I have 3 instances of Kontakt in the synth rack of my template, so every song has Kontakt. I only have 1 of those 3 connected in my template. The other 2 I need to choose "synth connected" to use them.

For the last several months I've noticed that sometimes when I go to the Synth Rack open the Kontakt Synth properties, I get a message at the very top of the window saying "not responding" this lasts for about 10 sec and then it's ok. 

This only happens for 1 or the 3 instances of Kontakt in my synth rack and it's the one that is "synth connected" by default in my template. It is a multi with 3 synths I've tried reinstalling Kontakt to fix this to no avail. 

I'm not sure if this is related to the crashes, but I thought I'd post it in case it would be helpful. I'm not getting crashes.

Share this post


Link to post
Share on other sites
3 hours ago, Noel Borthwick said:

@bertus weyers Have you reported these issues to NI? Also did you send crash dumps to us? If so what is your case number?

We have a good relationship with NI engineering and can forward any issues if any,

Hi Noel...

Sorry if my detail is below par. I haven't been too focused lately. I don't remember the case number but I will search to see if I saved any info.

 

NI? Why? Did you notice something leading or am I trampling a thread? I have no idea which (if any) of the plugins in this program are the crash cause. I also sent the template to support. I know they are not likely to have all the plugins, at least they can note which they are?

 

If you can give me any other instructions I'll be glad to follow them asap...

 

Edited by Keni

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...