• SONAR
  • trouble report 5448
2014/04/09 21:31:47
peregrine
Some time back a forum moderator said I needed to keep reminding them about this bug fix.
So just FYI Cakewalk, I'm still very interested in seeing this one in coming release.
2014/04/10 12:23:17
CJaysMusic
You need to fill lout a 'bug report form' for the bug you are seeing, if you are serious about it being fixed
 
Cj
2014/04/10 15:32:51
Splat
So here is a few of the threads you've posted on...


http://forum.cakewalk.com..bug-fixes-m2662589.aspx

http://forum.cakewalk.com...r-than-1-m2508014.aspx

http://forum.cakewalk.com...-release-m2885038.aspx
 
 

So what is the status of 5448? Please check here:
http://www.cakewalk.com/support/contact/Problem-Report-Status.aspx
 
And more to the point, what was the problem?
And have you tested to see it still exists in X3E?
 
Thanks..
 
2014/04/10 19:47:30
peregrine
Alex - I check the status every time I start a new project, simply because the templates for my large stuff
(180-200 tracks) need to be set up to accommodate our work around. If you want to read the status, you can.
I already know the status, and it hasn't changed since it was reported. My understanding is that when status
on a trouble report changes, like when it gets fixed and released, an email notification goes to the address you
have on file for that report. I was also told the following by Ryan the last time I asked about this:
"If you're upset about a bug not being fixed, it's easier just to communicate it
                               as bluntly as possible.If a new update or release comes out that doesn't
                               address it, simply say "I'm upset that bug xyz was not addressed with this
                               release. It's still affecting my workflow and I still want to see it fixed".
                               Personally, I find it more useful for us to know that you're upset about the
                                issue at hand versus how you think our management is structured."
 
So - here I am again letting you know I'd still like to see this worked. If you don't agree with Ryan, or there's
a new process you'd like me to follow for this, just let me know.
2014/04/10 19:55:44
Splat
As I don't know your email address I cannot check to see what the status or your issue is via the link I supplied above. Personally I don't see the point of this thread if you are unwilling to disclose any information whatsoever about your issue but each to their own.
 
I suspect the issue won't be fixed for a very long time looking at the content of the previous threads I linked to.
2014/04/10 20:02:42
peregrine
Alex - excuse me - I just assumed for a second you were a baker. I'm not actually looking
for help from users in the forum. I'm just posting this way per instructions from Ryan Munnis.
Please don't come back and tell this makes no sense; I already know that too. FWIW I
appreciate your interest.
2014/04/10 20:15:44
BENT
peregrine... Well said 
2014/04/10 23:35:01
Ryan Munnis [Cakewalk]
Yeah, unfortunately this didn't get resolved. It's still open and active in our bug tracking system.
2014/04/10 23:46:32
Ryan Munnis [Cakewalk]
BTW, no need to keep reminding us. The quote is taken out of context a bit.
 
I'm not saying don't voice your concerns, but regardless we still have an internal bug tracking system and staff that makes intelligent decisions regarding the direction of our products and what features and fixes we would like to focus on. Bumping forum threads as "reminders" that things haven't been resolved really doesn't change how we do things internally. There's a lot more thought and organization behind how we do it.
 
In any case, sorry to see this one is still around. It's definitely still active though and not closed out.
2014/04/11 07:24:43
Kev999
peregrine
...I'm not actually looking for help from users in the forum...



Sharing information is good though.  Please give us a clue about the nature of the bug.
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account