gustabo

williamcopper
As to focus: here's a screen shot, sorry it's a big image, three screens.   Can you tell, Craig, which window has focus, and if it's the track view, upper left, which track has focus?  

The Piano Roll does, change your visual settings in Windows and get rid of the transparency...

This.

John T
I think you're wasting your time Craig. If William actually wanted help with a problem, he'd ask for it, I'm sure.

 
I think you're right. However I am dedicated to helping the Bakers improve the program, and like the operators who have to answer all 911 calls (even from people who call to complain that a fast food place's service is too slow), I do chase this stuff down. However my time is probably better spent listening to the comments from people who actually know what they're doing, and describe issues with clarity. 
 
That said, we all know there are areas for improvement, and also, that SONAR is a sufficiently deep program it is almost impossible to know all its nuances. There is no shame to being ignorant about a program's features. This is why the majority of the people in this forum make constructive comments, and are appreciative when those who have expertise in a particular aspect of the program take the time to share it. A solutions-oriented user would be grateful at having learned something useful, and show some appreciation for those who helped solve a problem.
 
If Mr. Copper wants a simple, elegant solution, I highly recommend TASCAM's 32-track PortaStudio. Unless or course he is not capable of playing his music without having to do extensive, detail-oriented MIDI editing to cover up for his flubs, mistakes, and inadequacies .
 
Over and out here as well, time to do a Friday's Tip of the Week.
 

Another Friday night in Caketown. There are ongoing issues that need to be sorted out but I find it faster to deal with them one at a time. Chose the one that bugs you the most and get it sorted. Then, move on to the next. Laying out an extensive list of issues never seems to work for anyone.
 
It's not like the developers are taking the extra effort to make things clunky. I think William would be happier with Logic Pro on the Mac. I'd be happier if he was using Logic Pro on the Mac.

Anderton

williamcopper

Anderton
When I close a folder, it stays wherever it was. Your description of what you are doing is sufficiently opaque I have no idea how to reproduce your issue, which means I can't tell you how to solve it. Meanwhile, the rest of your problems are generally attributable to a lack of knowledge.

 
Are you really sure?    Or rather, yes, what you say is true, the FOLDER stays where it was.  But the SCREEN pops so that the first track is at the top, and the FOLDER, down there at #188 is still down there.  The problem is, you have to scroll to get back to it. 

The screen doesn't scroll either. Maybe it's because I don't have 188 tracks, but I do have more than will fit on the screen. I can't do anything with such vague descriptions, you need to provide steps to reproduce.
 

I have seen this issue - it can be frustrating. However I am yet to find the exact reason it shows up. I suspect it is something to do with locked/imported screensets as for me it seems to occur late in the process of preparing files for live performance, or working on older projects.
 
I would think from the obvious fondness for your own education and achievements demonstrated by your signature WC that you would know there is little point in whining about problems until you can consistently demonstrate the issue by defining contributing factors. In my  experience, once you do this Cakewalk are only too willing to listen to what you have to say. As a bonus,  if you took the time to do this you would also discover that many perceived 'problems' already have solutions.

I feel like the real problem is low standards in post composition. Trying to read those posts made my head hurt.
 
General hint to people: If you want help and wish to be taken seriously, do your best to clearly state your issue, try to use proper syntax, grammar, punctuation, and spacing, and try not to ramble. The more concise and understandable your post is, the most likely it is that you get useful help.

Almost every time I try a new feature for the first time I hit bugs. So, so often.
 
Clearly the original programmer never tests properly (or doesn't understand it's context, or is under time pressure), the person giving the job never tests it and the help writer never tries it out before writing up the help.
 
Sometimes I think I'm the only person that uses Sonar.
 
By the way, taking up the OP's initial argument: There really is a case for dialogs to reset their contents only at the start of a Sonar session, not every time they open.

I am guilty of hyperbole; absolutely true, and I'm sorry from the bottom of my heart.    Posts edited.   The main point remains, however.   Here's another little annoyance:  sometimes, in track view, you can see the Patch Change as a number ("p67").   Sometimes you can't, even if it's there in the track.    Which makes it real difficult to trust what you are seeing.    Finally realized the source of this tiny bug:   if you move a patch change message within a tick or so of a pitch wheel change, or a controller event, the patch label disappears from track view.    Screen view below: the insert, before shifting the patch change by one tick; the main screen, after shifting the patch change by one tick -- it's still there, but it disappeared from view.    (edit -- it's possible this is another consequence of windows font size increase, like the disappearance of track labels in the PRV track pane -- mine is set at 125%)
 

I would suggest that these problems or bugs be reported in the proper manner, in the Problem report page of this web site to be found here or perhaps get them verified here first.

It is the only way that Cakewalk can schedule for them to be properly examined and possibly rectified. 

Good presentation on this issue and something I've seen in a few different programs. I've had various degrees of problems with windows when using increased font sizes. I've seen issues in Sonar, Harrison Mixbus and others. I think it's a windows issue more than a Sonar issue, but it is annoying. Mixbus has font scaling built into the interface and it still causes problems. I just leave it at 100% now.

the font thing is because the apps don't follow system font settings ;-)