Frank! are you using the German version of SONAR X1?


Best Regards
Freddie

rhythminmind

BluerecordingStudios


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!!!!

I can confirm this issue as well. Randomly on/off. Kills all confidence with using the "pro channel"

+1 confirm this too... and i have already report it but please report it again..
 
Noel said he thought he knew what couses this graphic bug. It will be addressed in next update 20th of December.
 
 
Best Regards
Freddie

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

This has been fixed in X1A

no offense, but do not like the "do not post here, just call support or create a ticket"

No one is saying don't post here, post away but please log the issue with us as well so that we know about it.

Reality check:

Has anyone mentioned the interleave audio track save problem? For me, saved projects always revert to mono so I have to go back in anything and make all audio tracks stereo. This does not happen with busses as far as I can tell.

Ryan Munnis [Cakewalk
]

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/Support/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/Support/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.

Hey Ryan, thanks for the response, I really appreciate it.  But I guess this is what I still don't understand:
 
Why would my Bug Report have been filed as "ISSUE CLOSED- FEATURE REQUEST?" 
 
The report that I filed was regarding bugs in AudioSnap. AudioSnap is a feature that already exists. 
 
For a full documentation of the problems that I've been exeriencing with this existing feature, please see here:
[link=http://forum.cakewalk.com/tm.aspx?&m=2078582&mpage=1]http://forum.cakewalk.com...;m=2078582&mpage=1[/link]
 
 
  It's 2 pages long.
 

Mod Bod

chrisharbin


Reality check:

Has anyone mentioned the interleave audio track save problem? For me, saved projects always revert to mono so I have to go back in anything and make all audio tracks stereo. This does not happen with busses as far as I can tell.

Just tried it and I'm not seeing that one.

Thanks for checking!

Here's a couple:
CWBRN-3531 Browser View wont close in Multidock with B shortcut but does open. Status: As designed, when open B shortcut brings Browser into focus.

CWBRN-3532 Browser View in Multidock closes Folder pane when switching Screensets Status: New, haven't heard back

CWBRN-3553 Floating console view state is not retained when minimising & restoring Sonar (CV doesn't stay maximised) Status: Under Investigation

These are under XPPro SP3 32 bit.
 

Split would not split untill restart the program.

I was going to try twice today to report some of these to Cakewalk, but when I go to their bug report creation page, I get a message that reads:

Due to high volume and the incredible demand for SONAR X1 sections of the Cakewalk web site are temporarily unavailable. We are performing some updates and hope to restore service as soon as possible - our download servers will continue to work during this maintenance period so if you are in the middle of your SONAR X1 download service will not be disrupted.

So, at least for now, here are some I've seen, in no particular order other than that in which they come to mind here:
 
1) Changing ASIO latency turns the playback metronome on.  Steps to recreate: a) Make sure playback metronome is turned off, then go to Edit/Preferences/Audio/Driver Settings. b) Press the ASIO Panel button. c) Make a change to ASIO latency, and say OK to your change (via your soundcard's applet for that).  d) Play your project back.  Expected Result: Metronome is not heard.  Actual Result: Metronome is heard.  Workaround is to enable the playback metronome then disable it again.
 
2) The Mute Tool doesn't work.  Steps to recreate:  a) Turn on the Mute tool however, you like (e.g. Right click on the Erase/Mute took in the Tools section of the Control Bar, then select the Mute tool, or just click on the Mute tool if you've already selected that option for the Mute/Erase tool). b) Click on a clip.  Expected Result: a) Mute Tool cursor should appear.  b) Muted/Unmuted status of clip should be toggled.  Actual Result: a) Cursor shows arrow (Select Tool).  b) Muted/Unmuted status of clip is unchanged.  NOTE: There is a workaround where you can select the clip then use a menu or keyboard shortcut to mute it, but this is a major pain when comping, so not a terribly useful workaround.  It doesn't seem to matter how the Mute Tool is selected, either.
 
3) Lasso selections of non-identical length clips in layers does a time range selection of the range from the earliest clip start to the latest clip end instead of selecting just the selected clips.  Steps to recreate: a) With multiple overlapping layers in a single track (e.g. multiple takes of a vocal), use the Split tool to cut the layers up into phrases that do not start and stop at the same points (e.g. just before breath marks in a vocal).  b) Using the Smart Tool or Select Tool, vertically lasso select a small section of all clips that overlaps in time range (make sure the range does not overlap any clip end points so horizontally continguous clips do not get selected).  c) Hit the Delete key to delete the selected clips.  Expected Result:  b) Just the clips the lasso passed through should be selected.  c) Just the clips the lasso passed through should be deleted.  Actual Result: b) Just the clips the lasso passed through are inverted in color as if selected, but the entire time range from the earliest clip start to the latest clip end also gets shaded beyond the bounds of individual clips.  c) The entire time range gets deleted, not just the lassoed clips.  Workaround: Various tools can be used to individually click on each clip in turn then delete it.  NOTE: Another real slowdown for comping purposes for those of us who comp in phrases and cut things up ahead of time including deleting dead air.
 
4) Slight variation on #3, probably the same bug:  In a similar situation, if you lasso select a clip in one layer of the track horizontally, for example using the Smart Tool, then delete that clip, any clips in other layers that overlap that clip in time range also have anything within the time range of the selected clip deleted, when they should not be deleted, or have any part of them deleted, at all.  Again, a workaround is to select the clip with a non-lasso selection where it can be selected just by clicking on it (e.g. with the Select Tool or Move Tool), in which case deleting it only gets the one clip in the one layer.
 
5) Middle button to pop-up the Tool selection box is inconsistent.  Step to recreate: Press the middle mouse button anywhere in the clips pane of the track view.  Expected result: Tool selection box pops up.  Actual result: Sometimes it does, sometimes it doesn't.  It seems that it is especially likely that it won't pop up the first time or two it is clicked in any given track, but that isn't always the case, either.  NOTE: It is at least conceivable this could be hardware dependent.  I am using a Microsoft Comfort Optical Mouse 3000, where the "middle button" is actually the mouse wheel.
 
There may be a few other things I've noticed here and there, but these are ones I've encountered multiple times, and numbers 2-4 are definitely a major hassle for comping.
 
I might add that, for the most part, my general use of SONAR X1 to date has been pretty satisfactory.  I still have to get used to where to find some things in the new layouts, but I'm starting to get used to the general orientation, and I'm also finding it particularly efficient for project starts such as in picking softsynths in the early stages of working up an arrangement and doing MIDI editing (I love the Smart Tool and not having to constantly be switching between the Select tool, Pencil Tool, and Erase tool).  I've also experimented a little with ProChannel, and I'm definitely liking that a lot, despite having loads of plug-ins already.  It's also been rock solid for me thus far, and performance seems to be at least on par with SONAR 8.5.3 as far as I've been able to tell.  However, at the moment, it is extremely frustrating for vocal comping, at least for the way I do it, which is layer- and clip-based.
 
Rick
 
 

There's a misalignment between the maximized multidock and the browser and inspector. I draw red lines on the screenshots to show it (it's easier to see by downloading screenshots and zoom).

When multidock is docked and maximized at the bottom, there's a empty space at the top (5 pixels).
When multidock is docked and maximized at the top, almost same empty space at the bottom (6 pixels) and only a no-selected tab is not one pixel out (not the case when multidock is docked at the bottom).

And whe can see that the name of the track is a bit to low (the arrow shows it in the first screenshot).

Not a big deal but if it can be perfect...

Multidock docked at the bottom

Multidock docked at the top

By listening to midi files in the browser though TTS-1, it only follows "Preview at host tempo". No way to listen at the original midi file tempo.

Hope it helps.

may have already been posted. may not be a common bug even... but for some reason i can't change the routing/output of any of my tracks. I select a bus from the output options of a track but nothing changes... still routed straight to the master

anyone else getting this? 
 
 
edit: it seems that this only occurs with instrument tracks. regular audio tracks are fine. so you can just split the inst. track to solve it. long

good stuff! cheers.

I apologize if this bug has already been mentioned in this thread:

I can't change the output in the output dropdown on simple instrument tracks -- selecting other outputs (i.e. busses) has no effect. As work-around, I have to go to the track detail (if that's what it's called) displayed on to the left, and change the output there. 

Sonar X1 crashes every singel time it receives a sysx dump.