Anderton

jpetersen
From experience I can say it's impossible to know when or even whether a bug will be fixed. 

Bugs introduced in a new version are typically fixed within a month, sometimes less. However bugs involving old code are a crap shoot as to when they'll be fixed, depending on how deep they are in the code, and what else is going on. For example if CW is concentrating on automation or changing it, they'll try to fix automation-related bugs at that time; otherwise the automation bugs will wait until it's their turn.

that does make it sound like bugs "involving old code" won't really ever get fixed?

Unfortunately, and also why features/enhancements to existing (old) code also seem to be on the back burner.

Slightly off topic... I remember there was a possibility to look at problem report by number (I mean CWBRN). Does someone remember where? Rather hard to find.
 
For reports... I have created 2 so far. Neither was confirmed/commented. In general I agree with Craig, in case you report about new bug, there is a big chance it is going to be fixed. Otherwise the code is "old" and it will not be fixed in any predictable future. Bugs introduced more then 10 years ago will probably stay forever

http://www.cakewalk.com/Support/Contact/Problem-Report-Status/123456
(where 123456 is the report number you are looking for)

We'd better get reporting then, before they get old.
 
The audio engine improvements had a bug,
The drum replacer has an issue,
The new LP plugs have issues (just reported)
Let's think - what has recently been introduced?

Anderton
He's probably clicking on the icon below the track header; that icon is there for identification. The icon to click to open the synth GUI is the little one in the track header. This is logical. The little icon will always be visible, even if the track is minimized. 
 

I do that all the time ... it never works for me either, but it just looks so much like it's the right thing to click.

For whatever the worth - I had sent a malfunctioning Presonus AudioBox 1818VSL audio interface back to Presonus for $145 worth of repairs.  Two weeks later, it came back.  I pulled it from the box and immediately hooked it up, and it STILL had the same exact issues, even though the repair ticket indicated that they apparently replaced 2 different circuit boards in it.
 
They did generate a prepaid shipping label for me to send it back, and I am guessing they will replace whatever is left in it, so I am sure it will work out fine.
 
The point is that all of this stuff can go South at times, whether Cakewalk or Presonus or any of the music stuff.  Issues exist with virtually EVERY single DAW company's offerings.  When you get to a point where you have deadlines and time-sensitive deliveries and such, it's time to invest in creating and maintaining protocols for handling issues when they arise, such as:
 
1) Creating a system restore point prior to applying a major software update or configuration change.
2) Creating and implementing a workable backup/recovery process, consider additionally having an offsite copy of things - Someone just had their entire studio cleaned out overnight, and lost something like 10 YEARS of projects, because there was no offsite backup.  That is a not likely scenario, but it DOES happen.  (fire/flood/robbery/hardware are all possibilities too)
3) Learning to separate issues, to be able to work them independently and efficiently.
4) Understanding how to roll back a Sonar update, in case one introduces a show stopper bug to your flow
5) Understanding the likelihood that a given error is local to your setup/configuration versus global to the community of users.  (example, ProChannel not working would have been quite prominent in the forums if that were some global issue - that it is NOT being complained about by folks in general would point ME to consider that it is something I might have accidentally done to myself)
6) Being willing to engage with whatever combination of forum folks and Cakewalk support it takes to get an individual issue has a workaround or was resolved - whether the issue was operator error, some configuration change needed, or a bug.
 
To the OP - if you ARE willing to engage in the process, I will do my best to work with you on figuring out how to get you past your issues - so please let me know if you wish to do so, and I'll invest the time into trying to help.  (I believe others in the forum would do so, as well) :)
 
We might not be able to resolve all of your issues, but if they can be resolved through anything short of a maintenance fix by Cakewalk, these forums are a good shot for getting most things squared away.
 
Bob Bone
 

azslow3
Bugs introduced more then 10 years ago will probably stay forever

 
Actually, this bug that already existed in SONAR2 (which was my first version of SONAR) was fixed last year. IIRC, Noel said one or two other decade+ long bugs were fixed last year.
 
 
 

jpetersen
http://www.cakewalk.com/Support/Contact/Problem-Report-Status/123456
(where 123456 is the report number you are looking for)

 
This is a screenshot of my My Problem Reports today. 
 

 
All my reports vanished at one point last year (but I still have them all in Excel). I wondered if it was because I changed my username, but it can't be that because I only changed the name and kept using the same account.

Well, it wasn't just one or two other bugs, and they were 15+ years old. Here's what Noel said (I just found this post in the thread I pointed to):
 

Noel Borthwick [Cakewalk]
There were some other 15+ year bugs fixed with MIDI CC rendering. Pedal events could be rendered from the cropped out area of the clip which could lead to unexpected behavior. Controller searchback would also see stuff it shouldn't have.
There are lots of MIDI editing and rendering fixes and improvements in this version - a lot more than we've done in a long time.

 
So, very old bugs get fixed too!

icontakt

bgl1
I purchased a PreSonus DAW 

 

bgl1
If cakewalk rep said I was going to receive information from a troubleshooting report and never did (info above) I think y'all need to understand that cakewalk does NOT support its customers. That's why I purchased a different DAW.

 
I really hope PreSonus customer support has improved from a couple of years ago. Back then, a couple of inquiry emails I sent to them were completely ignored.
 

fwiw, and to level the playing field, in my very limited experience with presonus support i have found them to be excellent, second only to waves support in my experience, which involved my misunderstanding of the authorization, and some after sales installation questions if i recall. very fast, professional and spot on the money. my experience with cakewalk support on the other hand, via email is that it is/was horrendous, multiple emails and 5 or 6 years on still nothing. no the issue is no longer a concern to me, and i have stopped waiting a reply  the support at the forums by users or staff can be much better as can be contacting cakewalk staff via pm here. there is good and bad in all, people have good and bad experiences with all, there is no wonder company, we are all just human after all