I find the following list workarounds effectively addresses most of these minor niggles with the GUI:
 
1. Get used to it.
2. Get over it.
 
Just kidding... mostly. 

dkeHonestly I just don't see why it would matter whether that you can't scroll the last track to the top.

 

SuperGMe too. The most this could possibly be is a niggle, and a extremely minor one at that, which is why some of us can't help but wonder at the five-alarm sirens being posted.  Changes to workflow do affect our comfort zone, but this one doesn't seem to be such an all encompassing change that the Apocalypse has begun.

I started to read this thread and then realized it was 5 pages and gave up, so I'll just troll as best I can.
 
The above responses are commonplace in this forum.  Someone posts a question and instead of getting anything helpful in response they get a lot of "why would you want to do THAT??"  Sorry just pointing it out.
 
To the OP, I am also confused by the "taking away features" method of improving Sonar.  Why are there LESS color options?  Why can't I select a track anymore by clicking on the track name or clicking on the MSR buttons?  Why isn't there a visual display of whether automatic crossfades is selected?  I am enjoying my transition to X3 but those three are my biggest gripes... all things that were taken OUT of Sonar.

Another conundrum:
http://forum.cakewalk.com/Turning-snap-onoff-in-PRV-only-possible-with-mouse-click-Cakewalk-says-As-intended-m2917922.aspx
 
How is it that changing the global snap key binding to not actually toggle ALL snap functions be the intention of anybody?
 
"This key (n) will be used as the Global Snap toggle. Except when it's not...." How is that not NEWSPEAK?
 
 
 
 

Often, when I ask the question of "Why would you want to do that", it is simply to better understand the goals, because there may well be other ways of achieving them then what someone may be insisting they need to be able to do.
 
Here's an example I just ran into yesterday, while helping my 83-year old mom over the phone. No, she is not a hop producer, she is an adjunct professor of English, and was struggling with downloading Word attachments from her students.
 
She had begun the discussion asking about how to enable editing on documents, and it was only after getting into the whole process she was trying to follow that I figured out that there was a WAY simpler way for her to download and deal with the documents.
 
It turned out that she was doing this gigantic convoluted set of steps to download docs, simply because she wasn't clicking directly on the download arrow within the displayed icon for the document downloads, and rather than doing a simple download, clicking elsewhere in the displayed icon told it to open the attachment in a 'preview' mode, which automatically protects it from editing, and when she saved it from there it retained its read-only status, and THAT'S why she needed to learn how to 'enable for editing'.
 
Sorry for the lengthy example above, but it illustrates the reason for asking someone for an explanation of WHY they want to do something, as in the example case, a simple and minor change made things a WHOLE lot easier for her to accomplish her goals.
 
I DO agree that sometimes folks ask the question in a ridiculing kind of way, where something done differently means it is 'wrong', rather than just different.  :)
 
Bob Bone
 

I'm still very confused with this thread. I'm also a "pro" and use up to 120 tracks over 30 busses and havent noticed anything to do with scrolling.
 
I tried to DL the DBox link that Danny uploaded but its 404 now....
 
Sometimes I have to click in a certain area of skylight to get scroll to scroll how I want it but it really hasnt affected my workflow, I just became used to the new style of workflow and before I know it, its become second nature....I am however on 4 monitors tho....
 
A bit miffed about this thread to be honest.
 
 

I tell you another thing, a GUI from hell? Try Pro Tools.

Being able to show only the last track is a great "workflow" enhancement feature.
 
The graphic displayed way above in this thread illustrates the happiness of being able to work on the last track without having to move other stuff out of the way.
 
This is an example of workflow downgrade.
 
I am sure many people have been happy to NOT have to move the stuff they are working on out of the way to work on a related bit.
 
This issue, and the global snap toggle not working, are not just little annoyances. And what makes these bits more annoying is to have no clear explanation as to why they were changed. "By design" is too often the excuse for "not paying attention."
 
Feed back from users provides direction to product developers. Just accepting that we should be completely satisfied for what we paid for, no matter how unreasonable it is, will not provide realistic feedback. We all know of examples of how all the "yes men" agreeing with what is obviously not so results in stupidity. We were required to read "The Emperor's New Clothes" so we could understand what can happen when no one tells the truth. Prolly should be required reading every year.
 
The part that is really confusing for me is why it seems the CW managers never ask the major users if something makes sense to change. Especially when contemplating removing stuff.
 
Is CJ a beta tester?  Anyone posting in this thread a beta tester? I would like to review their comments about complaints.
 
 
 
 
  
 

jm24
 
The part that is really confusing for me is why it seems the CW managers never ask the major users if something makes sense to change. Especially when contemplating removing stuff.
 

For anyone who doesn't want to take the time to read through this entire thread, read post #13, which explains why the fractional scrolling tradeoff was made. According to Seth Kellogg: "[The] 'snap' scrolling introduced many undesirable UI and editing behaviors in regards to automation/take lanes, auto-zoom, track zoom, quick grouping, audio snap, editing, etc." These issues had been noted before, and now they're fixed but at the expense of not having a different feature. The missing feature seems to be really important to some people and totally irrelevant to others. Seth also gave two workarounds. While workarounds are not as convenient, they at least return a certain level of functionality.
 
Another issue brought up was a bug, and was fixed in a subsequent version.
 
It took several posts for most people to even understand what the problem actually is. Keith Albright chimed in with "If you want to scroll by whole tracks, click on the scroll arrows." Post #44 added more info about the relation to auto-zoom. I just finished a project with 164 tracks and didn't feel there was an issue with scrolling but perhaps I have a different workflow.
 
As to asking major users if something makes sense to change, post #26 sums up the issue very succinctly. Different people have different priorities, and rarely will you get an answer where everyone agrees (although I think "N" being truly a global snap would be one of them). People who have gotten used to the smoother scrolling and more predictable editing behavior with respect to automation, auto-zoom, quick grouping, AudioSnap, etc. would probably be unhappy if it went back to the way it was. Remember, implementing one person's feature request may involve a tradeoff for some other user. It doesn't seem like there was an overwhelming +1 about the problem experienced by the OP. That doesn't make the issue any less important to those who miss the feature, but CW tries to balance needs to satisfy the majority of users.
 
As to why there aren't options so people can have more choices, post #36 explains it quite well.
 
Again, this isn't to criticize those who have a genuine problem with the tradeoff, but it's not that something was removed for no reason. It was removed to make a tradeoff that CW felt would, at least in theory, benefit a greater number of users.
 
 
 
 

markyzno
I tell you another thing, a GUI from hell? Try Pro Tools.

To each, his own.  I happen to like the PT GUI - especially the mixer view.  I can get to a send without having to mouse down.

Cake is as cake does