This issue should be fixed in the next patch. I just regressed i

Thanks Seth :)
 

I'm pretty sure CJ isn't complaining about the scroll by track/fractional scrolling, but the in-ability to scroll the track pane regardless of track count to only display 1 track.

That is correct Seth. You nailed it!

Danny Danzi: Your voice is SO JERSEY.
 
I know I *used* to sound like that  

here is the reaper vs sonar.


reaper: (messy)

and Sonar X2:(clean)

Keith Albright [Cakewalk]
If you want to scroll by whole tracks, click on the scroll arrows.

That doesn't work.  You cannot scroll to see track 32 at the top of the track view in a project of 32 tracks.
Those arrows are useless!! You cannot scroll using the Arrows, the mouse wheel or the page up and down to only see 1 or 2 tracks at the top of the track view, like you could in all the other versions

CJ, we must be missing the boat and must have to revise how we do things. Do you guys not use your middle mouse wheel to scroll tracks? For those that consider it minor, unfortunately it's huge for some of us. Especially if you run a business and may have 60-80 tracks with 10 or more buses. Trust me when I tell you, it's been one of the most annoying things for me in this release. I can't say enough good about X3...but this is such a frustrating thing, it makes me seem more negative than I need to be only because of how often I am constantly mouse scrolling tracks....only to have them not end up where I want them. They go right on by, or I get a quarter of a track, or a half of a track...so I either have to make them big where I lose real estate or I use Shift and have to do two mouse scroll clicks to see one track in full view. The smaller I make my tracks, the worse this becomes.

 
+1

I understand cjs need. Frankly, I think he can be accommodated. Cakewalk has provided work arounds.

Then you do not understand what i'm saying. What there is, takes 4 or 5 steps to do what a mouse scroll wheel did, the arrows did and the page up and down did on their own..
Those kind of so called work abounds are not feasible to the work flow.

When I said 'I think you can be accommodated', my meaning was that it seems like something they can put back into the app.
 
Limiting the window tracks and bus pane scroll windows to 1/2 full seems like it was an arbitrary decision when implementing the fractional scrolling. It was probably slightly simpler to do this than to enable you to roll to exactly the last track or bus, given the changes they were making.
 
Also, snapping the busses so that it's easy to scroll a bus keeping it 100% in the pane seems to make sense (Danny's complaint). You could adjust the strength of the snap just like we do in the current snap.
 
The only reason that I can see to prevent the user from scrolling the last track or bus to the top of the window would be to show the user that there is more up there (in case she forgot). I don't think this is worth constraining the user for, imho. And if they do, they should make the constraint optional.
 

I left X2 for S1 some time ago.
 
Going to give X3 a try.
 
I notice in S1 I can't scroll up and down unless I click in certain places.
 
 

CJaysMusic

CJ, we must be missing the boat and must have to revise how we do things. Do you guys not use your middle mouse wheel to scroll tracks? For those that consider it minor, unfortunately it's huge for some of us. Especially if you run a business and may have 60-80 tracks with 10 or more buses. Trust me when I tell you, it's been one of the most annoying things for me in this release. I can't say enough good about X3...but this is such a frustrating thing, it makes me seem more negative than I need to be only because of how often I am constantly mouse scrolling tracks....only to have them not end up where I want them. They go right on by, or I get a quarter of a track, or a half of a track...so I either have to make them big where I lose real estate or I use Shift and have to do two mouse scroll clicks to see one track in full view. The smaller I make my tracks, the worse this becomes.

 
+1

I think that this kind of thing is important to SONAR Users who are trying to work quickly because of time restraints.  I've been using Studio One for the simple reason that once I learned where most of the features were located and I got past the "what the frick just happened?" moments, I've been able to track clients and work solo more quickly.   That's not to say that Studio One is perfect because it surely is not and there are weaknesses that I have to work around there as well.

X3's ARA implementation is a step in the right direction as well as the new comping workflow.  I have one particular client who does some pre-production himself in SONAR and he likes to bring a bundle file and use my better mics and pres along with freeing himself to be "artist" instead of engineer.  He usually buys five hour blocks so I have to use SONAR from time to time.  Me, I don't care what I use as long as I can move fast in it.  Having to fiddle with scrolling would be a pain to me in a long session especially if someone is waiting for me to get finished.

tacman7
I left X2 for S1 some time ago.
 
Going to give X3 a try.
 
I notice in S1 I can't scroll up and down unless I click in certain places.
 
 

Yes, that is an annoyance to me at times as well.  In S1 you have to mouse in what SONAR users would refer to as the Clips Pane.

In fairness to the Cakewalk developers, Studio One behaves pretty much in the same fashion as SONAR in this scrolling situation.  I've never noticed it because when I am wanting to see single track, I have the mixer view docked at the bottom of the screen with the mixer expanded vertically until it reaches a single horizontal track (which I have sized to fit) in the track view.  Using the arrow keys I can scroll up and down the tracks and simultaneously place focus on the displayed track in the mixer.  When I scroll in this manner, S1 automatically fills my narrowed track view with a single track.

I've done the same sort of in Reaper as well.
 
EDIT: I always believe in fairness so I checked the behavior of X3 and it is (from what I can tell) a match to the way Studio One behaves.  Since I haven't done a project in X3, I didn't notice the change.  That said, when compared to X2's scrolling behavior, I think the way X2 behaves is the superior option.   Now if only X3 could display at least 4 sends in the console.