Willy Jones [Cakewalk
]

Hi Everyone,

Please be sure you are reporting issues directly to us here: http://www.cakewalk.com/support/ProblemReporter/  and filling out the form completely with all of the requested information.

Aside from contacting Tech Support or Customer Service that is the only way our development team will ever be made aware of anything you are experiencing.

Thanks,

I find it to be extraordinarily arrogant that Cakewalk will force all these loyal consumers to file individual reports on the "Problem Reporter," when we have taken the time and effort to consolidate these bugs here for the company's convenience.  Willy, come on, you are an administrator and you are aware this thread is here. Don't be so beaurocratic, this should not be like working with the DMV.
 
I have submitted a report using the "Problem Reporter" while struggling with over 2 dozen bugs in AudioSnap. All these bugs are documented in this thread:
 
http://forum.cakewalk.com/tm.aspx?&m=2078582&mpage=1
 
(The thread is 2 pages long)
 
All I got in response was a form-letter email from Cakewalk, saying "ISSUE CLOSED- this issue has been considered a Feature Request."  AudioSnap is not a feature request. This feature already exists.  The issue was that an existing feature does not work.
 
Anyone who takes the time to fill out a bug report form, your efforts will be tossed on a massive heap of bugs that will never be looked at.  Reaper's website said it best:
 
If you currently use another DAW, you might be reading this because you're contemplating shelling out $150 for the next overhyped version that doesn't address any of the bugs you've been complaining about for five years while adding a bunch of features you couldn't care less about.

Big Lion

Willy Jones [Cakewalk
]

Hi Everyone,

Please be sure you are reporting issues directly to us here: http://www.cakewalk.com/support/ProblemReporter/  and filling out the form completely with all of the requested information.

Aside from contacting Tech Support or Customer Service that is the only way our development team will ever be made aware of anything you are experiencing.

Thanks,

I find it to be extraordinarily arrogant that Cakewalk will force all these loyal consumers to file individual reports on the "Problem Reporter," when we have taken the time and effort to consolidate these bugs here for the company's convenience.  Willy, come on, you are an administrator and you are aware this thread is here. Don't be so beaurocratic, this should not be like working with the DMV.
 
I have submitted a report using the "Problem Reporter" while struggling with over 2 dozen bugs in AudioSnap. All these bugs are documented in this thread:
 
http://forum.cakewalk.com/tm.aspx?&m=2078582&mpage=1
 
(The thread is 2 pages long)
 
All I got in response was a form-letter email from Cakewalk, saying "ISSUE CLOSED- this issue has been considered a Feature Request."  AudioSnap is not a feature request. This feature already exists.  The issue was that an existing feature does not work.
 
Anyone who takes the time to fill out a bug report form, your efforts will be tossed on a massive heap of bugs that will never be looked at.  Reaper's website said it best:
 
If you currently use another DAW, you might be reading this because you're contemplating shelling out $150 for the next overhyped version that doesn't address any of the bugs you've been complaining about for five years while adding a bunch of features you couldn't care less about.

I'm too quite pissed about this. I've already filled a form complaining about the quantize audio transients bug and the turn on/off audiosnap problem (everything gets resetted). No response yet.

There's more info here: http://forum.cakewalk.com/tm.aspx?m=2155081

Big Lion

Willy Jones [Cakewalk
]

Hi Everyone,

Please be sure you are reporting issues directly to us here: http://www.cakewalk.com/support/ProblemReporter/  and filling out the form completely with all of the requested information.

Aside from contacting Tech Support or Customer Service that is the only way our development team will ever be made aware of anything you are experiencing.

Thanks,

I find it to be extraordinarily arrogant that Cakewalk will force all these loyal consumers to file individual reports on the "Problem Reporter," when we have taken the time and effort to consolidate these bugs here for the company's convenience.  Willy, come on, you are an administrator and you are aware this thread is here. Don't be so beaurocratic, this should not be like working with the DMV.
 
I have submitted a report using the "Problem Reporter" while struggling with over 2 dozen bugs in AudioSnap. All these bugs are documented in this thread:
 
http://forum.cakewalk.com/tm.aspx?&m=2078582&mpage=1
 
(The thread is 2 pages long)
 
All I got in response was a form-letter email from Cakewalk, saying "ISSUE CLOSED- this issue has been considered a Feature Request."  AudioSnap is not a feature request. This feature already exists.  The issue was that an existing feature does not work.
 
Anyone who takes the time to fill out a bug report form, your efforts will be tossed on a massive heap of bugs that will never be looked at.  Reaper's website said it best:
 
If you currently use another DAW, you might be reading this because you're contemplating shelling out $150 for the next overhyped version that doesn't address any of the bugs you've been complaining about for five years while adding a bunch of features you couldn't care less about.

Hi Big Lion,

I pulled up the reply to your report, as listed below:

"Thank you for your suggestions. We have submitted this for review to be considered in future Cakewalk products. For future suggestions such as these, please fill out our feature request form here: http://www.cakewalk.com/S.port/FeatureRequest.aspx For submitting what you believe to be errors in the application, please keep each issue to a separate report. It is helpful to explain the procedure taken in a step-by-step formula, with the expected results and actual results given based on the steps you have taken. Please do not report multiple issues in the same Problem Report."

I understand text can often be misinterpreted so I apologize if this reply was confusing or came across as rude... this was definitely not our intention. Please understand that we have specific methods for contacting the appropriate departments within our company. Customers experiencing problems with their sound card drivers not installing, for example, would want to contact Technical Support. Something like this is probably easily resolved with help from a support representative and is most likely not a bug in SONAR. Customers experiencing issues obtaining their download links for SONAR X1, would want to contact Customer Service, not fill out the Problem Report Form.

The Problem Report Form is simply a system of users letting us know they have found an issue, and us letting them know in return whether or not we are aware of the issue and whether or not it has been officially acknowledged by members of our staff who do not have time to read the user forums during business hours. All of this is explained in the literature at http://www.cakewalk.com/About/contact.asp

Feedback such as what you gave us is invaluable and we appreciate it more than may be aware. When someone fills out our Problem Report Form and we believe it is not necessarily a current error in the application, but rather excellent feedback on what would make the product better, we cannot direct this towards our Quality Assurance department. Instead, we fill out the Feature Request Form on behalf of the customer. This can be found at http://www.cakewalk.com/S.port/FeatureRequest.aspx

We do this so that your thoughts are directed appropriately. Our Product Managers routinely receive these feature requests in a report and they document and review everything.

Why am I explaining all of this? Because I want to help you understand that your report was never discarded nor thrown away.

Please understand that we have a well tuned system that we use. Our forums are an excellent way for us to communicate with our user base, and for our users to communicate with one another. However, these are user forums and unfortunately we cannot monitor them 24/7 and we cannot always consolidate threads.

I understand that it is frustrating to simply see status updates that say "Submitted to Development" or "Closed - Feature Request" but please understand that we do have employees whose full time jobs are to manage and maintain this. If they are changing the status of the report, it is because they are trying to direct your concerns appropriately.

If you are ever confused about the status of a report, please just let us know so that we can answer any questions you may have.

Orphaned envelopes cannot be deleted from tracks and remain there like zombies at a wedding

brundlefly

I'll be looking at the Pro Channel (in this instance the Master bus), and information will appear in the EQ, other times ... upon return ... nothing is there. On the master bus, the VU meter is dark ... but on other channels it's lit. Seems to work, but I've not figured what it's supposed to be doing so ... is it a bug?

 
I think the EQ not always showing the correct graphical display is an acknowledged GUI bug. What you're seeing with the Prochannel compressor is normal, though. It comes in two flavors: PC76 for Tracks and PC4K for buses. The PC4K meter face is black. There is also a GUI bug that the compressor meters will nto show activity when the tranposrt isn;t running in X1 x64.
 
The ProChannel GUI bugs are expected to be fixed in the X1a patch to be released before Xmas.

Thanks for the info B! I'm an avid user of Sonar, but it's only for recording my music -- so I have a narrow band of usage and process and don't spend all day at it.
 
I don't really wander into some of the deep feature sets offered and therefore I'm never quite certain that the occasional confusion and wonder is either me or bug. I'm thankful for the good folks here who are so kind as to share their expertise.
 
Thanks again!
 
Kev-

2re


Instrument tracks can not be routed to a different output than whichever is set by default. But if you split the instrument track in to a midi and audio track, you can route the audio track's output to the bus of your choice. When you make those tracks into an instrument track again, the routing of your choice will be there, but you'd have to split it again to reroute to a different bus.

For instrument tracks you can change the output without splitting them. Use the 'Selected Track Outputs...' option in the output dropdown. A new window pops up in which you can change the track output.
By the way, I have already submitted this to Cake, and I'm really hoping for a fix in the upcoming patch.

It works when holding down CTRL while changing output. This also works for changing outputs for several tracks at once.

EDIT/ Solved: ProChannel System Crash error when saving the project.

Many companies start forums for the sole reason to cut down on tech support.
The user base of a piece of software is often more knowledgeable & helpful then the design team in real world situations. & often non biased. I have countless examples of that for many software products.
Example - When I switched to Sonar from PT "I asked how do I record the output of a bus to an audio track?"
The tech support answer was in more or less words "You can't & this is why you shouldn't". It was the collaboration of ideas via these forums that helped me create my workaround.

I get the feeling that this is more of a "bad press" deterrent.
People should do both. Send an official support request & come here to see if a solution is available. I think people "we" are smart enough to realize these are public discussions not official sanctioned support.

Nice one X1 developers. Can't work with it at the moment though, but looking forward to patch files. Can anyone (Noel) give us an indication, timewise, when this could come about? In the event of such patch release, will cakewalk let us know so that we can download?

Organize Tracks and Busses in Console view are broken!
CWBRN-3551



Organize Tracks and Busses in Console view are broken!
You can't Organize Tracks or Busses in Console view.
This has work in SONAR 8.5 and backward. I presume its a bug, it must be?. WHY should anyone want to take this LOGICAL workflow away from any DAW system?
 
1. Got to Console View.

2. Select one track with help of Left "MOUSE"-Click in Console View.

3. Hold Down the "MOUSE" and try to drag the track either Left or right to organize the tracks order.

4. Result = Nothing MOVE, the track doesn't move?

5. Same Result happens if you try to organize the Busses in BUS section in Console-View.

Conclusions: You can organize the tracks and Busses track order from the "Track View" but not from "Console"-View.


Best Regards
Freddie

spelling mistake on one of the button's mouse over, CW spelled "Tansients" instead of "Transients"

Enabling and disabling saturation in ProChannel not working properly. Sometimes when it is on, it doesnt work. After exporting audio with saturation off, it enables!!!!

Plugs not staying docked in multi dock: CWBRN-3554

Good thread. Wonderful tech support.
And the bakers are watching.
Doesn't get any better!!!

garrigus

Using the Smart tool, Shift+click on the envelope to edit it.

Scott

Thanks, Scott. I was tearing my hair out on that one.