Hi - I have moved this thread back to the Sonar foryum for now - you will get more people looking at the issue here, and the Cakewalk folks want to have issues confirmed by more than one person, and for a given issue, it should also be looked at to make sure something is an actual bug, instead of just working differently than someone wants it to.
I noticed from your post count that you would not have gotten a private message, so I thought I would post here to let you know why I moved the thread.
If it turns out to be an actual bug, then you can submit as such to their problem reporting process, and then come in and edit the subject line of your original post for the thread - and add in the assigned bug report number, called a CWBRN number, into the subject line. We should see that, and will also keep an eye on the thread to make sure it is also confirmed by at least another person, and then we will cheerfully move it back to the Problem Reports forum.
The above is how Cakewalk is intending to have the normal progression of potential bug threads follow, so that their developers can count on the threads in the problem reports forum as being actual bugs - which makes very efficient use of their time, which then helps them develop fixes for bugs faster, which rocks. :)
Welcome to the forums, and if new to Sonar, welcome to Sonar as well. The forum community is a VERY powerful and helpful resource with the software, and if you look through the foryums list, you can get an idea of where to post things, and where to look for things you want to learn more about.
Additionally, the forum search mechanism SUCKS, and likely always will, so if you want to search the forums for something, add: site:forums.cakewalk.com to your search terms, and Google will search only the Cakewalk forums for whatever the rest of your search terms are, and that will help you look for threads - like to see if someone else has a workaround or explanation for something you may be struggling with, etc...
Bob Bone