Hi:
For me, it happens with the lower notes, the lower the note the more it happens.
Changing the size of the staff view, meaning enlarging it, makes it possible.
Or closing the staff view and reopen it.
I think it has to do with the graphics card of each machine.
Basically, it rarely happened, and now it happens a lot.
 

I kind of think it has to do with the graphics card too for some reason... Just a hunch. But to everyone saying enlarging the staff view makes it possible to right click the note, that's just not true, at least for me. I can go as big as it possibly goes and you still can't right click it if it's the lowest note on the staff.

Jlien X

CakeAlexS
Let us know the issue number thanka. 

 
The Problem Reporter ticket closed as unreproducible ("Contact Tech Support" to be more precise) is CWBRN-23709.

The case I'm currently dealing with tech support is Case 128412. I received a reply several hours ago saying they can't still reproduce it, so I've replied to them with a video clearly showing the issue attached.
 
Below are the steps to reproduce the issue (reproducible at least on my end):
 
1. Create a new project using the Normal project template.
2. Insert a MIDI track and hit Alt+3 to open the Piano Roll view.
3. Using whatever method you like (I used the Smart tool), enter/record note events on C5 and D5, like this:

4. Hit Alt+6 to open the Staff view.
5. Select the Smart tool in the Control Bar and right-click each note to open the Note Properties dialog box.
 
[Expected Results]
All notes open the Note Properties dialog box when right-clicked.
 
[Actual Results]
All C5 notes show a right-click menu when right-clicked, like this:

Couldn't reproduce with X3E. I tried improvising as well with no effect. Sorry...

Don't worry, the video I sent to tech support clearly shows the issue so they should be aware of it now...

Thanks for pointing this one out to Cakewalk. You can usually work around it by zooming the staff view in to clown mode but it would be nice if they fixed it. I use the piano roll so infrequently, I didn't think of using it for editing a note I can't get at in the staff view, DOH!
 

polarbear
The one where you can't right click the lowest note on any given track in staff view to get its Note Properties page, but they fixed it in X3e? Well the bug seems to have come back again out of nowhere for me. Any one else having this problem? In most cases you can draw a note underneath it, then go right click the note you were trying to change, make your changes, and then delete the lower note you drew in... But that's a major pain and it doesn't seem to be working on this one track (I'm not allowed to draw a note lower for some reason).

 
Try either 1) grabbing the note and transposing it any place within the staff.  release mouse button.  Now move it back and it should be OK now to right click on the note.  2) If it isn't, use the Event Inspector (it should be on your Control Bar). Click in the note and the Event Inspector shows its properties.  It's a pain and should be fixed, but it probably won't get fixed, at least not intentionally.  
 
I thought it was fixed too, but I don't think it ever was.  On my machine the problem is intermittent, sometimes I have no issue right-clicking on a note below the staff, sometimes I do.  The fastest workaround is to use the Event Inspector. 
 
Jerry
www.jerrygerber.com

People are talking about low notes, like C4 or D4 or E4 and I have experienced that too, all the time.
Not the C5 and up.
Going back to the issue of graphic cards, I think this is what happens:
 
1. CW have always used the best computers, with the best graphic cards, whether they are on board or not, and very good audio converters. This is typical corporate behavior.
 
2. I have asked before, that why don't CW just come out and tell us which computers they use, so that we can all buy and use the same computers.  Then if we have a bug, then it is really a bug.  That is what Apple is all about. For instance for X4, they should tell us which computers they develop X4 on, so for people who are not very technically inclined. meaning trouble shoot their computers on their own, they are sure to get one that works well with Sonar.
 
3. I understand the diversity of Windows based computer, and it is a very good thing, since we don't have to buy the very expensive computers to have Sonar working, like what Apple has been doing with Logic.
 
4. hence everytime someone claims that there is a bug, half of the people on this forum can't reproduce it, and sometimes even ridicule the OP, and the other half swears up and down, that it is really a bug.
 
My thoughts.
 
dan
 
 
 
 
 
 
 
 
 

dan le
People are talking about low notes, like C4 or D4 or E4 and I have experienced that too, all the time.
Not the C5 and up.
Going back to the issue of graphic cards, I think this is what happens:
 
1. CW have always used the best computers, with the best graphic cards, whether they are on board or not, and very good audio converters. This is typical corporate behavior.
 
2. I have asked before, that why don't CW just come out and tell us which computers they use, so that we can all buy and use the same computers.  Then if we have a bug, then it is really a bug.  That is what Apple is all about. For instance for X4, they should tell us which computers they develop X4 on, so for people who are not very technically inclined. meaning trouble shoot their computers on their own, they are sure to get one that works well with Sonar.
 
3. I understand the diversity of Windows based computer, and it is a very good thing, since we don't have to buy the very expensive computers to have Sonar working, like what Apple has been doing with Logic.
 
4. hence everytime someone claims that there is a bug, half of the people on this forum can't reproduce it, and sometimes even ridicule the OP, and the other half swears up and down, that it is really a bug.
 
My thoughts.
 
dan

Sorry but you really don't really need specific hardware to test Sonar bugs unless the bug is with specific hardware. Also please note people use different versions of windows, different drivers and different patch levels. Testing bugs just on one special platform won't work at all. What is more help is if people would list their hardware and software specs. In this case tell us their graphics card and mice makes and models plus driver versions, and OS version, could prove useful. Also Sonar version and whether it is 32 bit or 64 bit. BTW so far Cakewalk have been unable to repro.

My hunch here is that it isn't a driver or hardware related issue,. We probably haven't identified the full steps to repro this yet and it is probably a little more complex than it first appears (e.g. let's say something needs to be set in preferences that we haven't identified).

BTW We've had some success in reproducing other bugs see post #1here.
http://forum.cakewalk.com...aspx?m=3009969

I don't think anybody here has claimed this isn't a bug so far or has been dismissive. It's just difficult to repro, some bugs are like that. Without full steps it's often hard if not impossible for the developer to fix.

At this stage I do recommend people update their graphics card drivers with their vendor, remove any vendor specific mouse drivers and mouse software they may have downloaded (unless it makes the mouse inoperative), and run windows update several times (including most optional updates on offer) to see if it does clear the issue. Also make sure you are on X3E and afterwards see if the issue is specifically reproducible in new projects.

Cheers

I think I just found a trick to work around this.
I noticed that when this happens, the on screen pointer moves down or up ever so slightly. If you compensate by dragging the mouse to the note before releasing the right button, you will get the note properties dialog instead of the context menu.
Give it a shot and see if it works for you.

POLAR BEAR, THIS THREAD SHOULD HELP YOU MOVE FORWARD: http://forum.cakewalk.com...LAY-FREE-m3059511.aspx
 
HOPE THAT HELPS!
 
- SHAWN LEE X PRODUCER FARRELL