Did you read our posts? Doesn’t happen for us.
Can you post a video of that?
Because, that is what Suspend means in this context. It is temporary.
What one wants in a workflow at any certain point is of course personal. This is how I work: In the occasion that I “catch” a note to make a quick edit while Autoscroll is ON and Suspend autoscroll when editing is ON, I generally want to resume scrolling after I’m done editing. If I’m actually doing any serious editing, I stop playback anyway. As long as Return to start position on stop is deactivated, the display will then freeze right where I am, and I can do the editing I want, and then hit Play to continue. The Suspend feature for me is mainly for super-quick fixes during playback. If I have done a super-quick edit without stopping playback, I hit F when I’m done to turn Autoscroll back on so I can see the cursor (and yes, then the view jumps straight to the cursor – where else indeed?). And If I make a quick edit, then stop and start again, I’m happy that Autoscroll is back on, since that would be my current preference. To me, this all makes perfect sense.
Please read this bit again:
That is the whole point, that I have been trying to get across as well.
When we are advising you to not use Suspend, it is not to be rude or not because we don’t understand. It is because we actually do understand the difference.
I also understand the fact that you might feel some ownership over a feature that you helped suggest, and that you are disappointed that it (no longer) works the way you would want. That is pretty evident, and maybe that is really your core issue? Since you helped suggesting the feature, you also like to have a say at what it should be. I get that.
However, we who don’t feel that kind of personal connection to this feature, see this: You insisting on using feature B, even though feature A already does basically everything you want. But you really really want to use feature B instead, even though the basic concept of feature B contradicts what you want to achieve. And when we point this out, we are “not professional”, or “don’t use the program enough”, no matter that we do it for a living, every day.
In the event that SB developers would listen to your suggestion, and modify the Suspend feature to act exactly like Autoscroll On/Off, then what is the point of the extra feature really? It makes conceptually no sense to call it Suspend then.
So really, if that one extra keypress on the F key is that big of a problem to your workflow, then the only logical suggestion for an actual improvement for SB developers is this:
Lastly:
I’m curious what you feel is the point of the Suspend feature in the first place. Honestly curious, and not in a rude way. What was it that you suggested to Steinberg, and once they implemented the feature – did it work like you wanted it to? Has it ever worked like you wanted it to? If so, when did this change?
Cheers
Was that last question for me?
No, sorry if that was unclear. It was for @emotive.
1 Like
Since @emotive says he was the one who requested the feature from Steinberg in the first place, it would be interesting to know what the actual feature request was, and how it used to work, if it worked any differently from now.
I again repeat, I do not want Autoscroll to turn back on just because of a timeline change, i.e., via click in the timeline, so is that too difficult for people to comprehend?
Second, Autoscroll should not be reactivated, from suspend just because playback has been restarted.
This is now the fourth time I have reiterated my request for Autoscroll improvements.
As for how the feature (set) behaved prior to Autoscroll suspend being introduced, users would have to ask SB. All I did was ask for an improvement, and it was granted (thank you SB!).
The feature(s) work well up to a point but I am really questioning in what situations should Autoscroll turn back on, in particular when reaching the edge of the display.
We know what you are requesting…
It’s clear you’ve stopped listening to what people are saying.
Good luck with your request.
3 Likes
Hi madihaeman444, i understand that the situation was running out of proportions because of this autoscroll suspend.
Some people like to change so bad, that the mouse was growing to be an elephant, so he coul’d program some brass… pwe pwe.
lol.
So to have some fun to i was trying to explain emotive, but the emotions, we must calculate to, was in a hurry i think.
Wich run faster automatic in Cubase, the mouse, or the elephant, we can read that later in the sunday papers… 
So i get a little off topic now, but this whole issue and request was a bit blown up at this way.
So, this suspned mode, in the beginning of this topic, was the annyoing part, because that suspend mode you can use, or not, for fast editing.
Maby the mouse was to fast, but it was the F-key that was involved to, that key-command that do the same as that mouse click on the autoscroll button, that get the color orange when we use the suspend mode.
So indeed, very amazing… as we speak about this request real time, so do not worry, i think emotive can buy more software to get it automatic…
So while autoscroll follow the Locator, under the key F from FOLLOW the locator haha, this was allready changed in the mythe FISH…
So if emotive gonna use WIX PA he can use Cubase autoscroll to play the game “Catch the fish” 
So, thanks for helping, i suppose everybody is happy now, at the end of this autoscroll tunnel… 
So, i liked that anecdote with that slices pizza to
1 Like
Oké, we all wish you good luck i think.
Not much more to say, i think.
But, do not forget to have fun in live…
This is what I use:
Zoom, of itself is troublesome as well, since it is not predictable when zooming in.
I also use a small monitor too so the Autoscroll feature set works for me, albeit often with massive annoyance and aggravation, hence my requst for improvement(s).
I stand by everything I have said, the feature needs to be improved and how it is right now, shows that if it hasn’t annoyed anyone using it by now, then they probably don’t use the application anywhere near as much as they should.
Don’t put down other users like that. At least not before you know who they are and what they do and how they do it. I’ve delivered 10 shows in the past 8 days. Plenty of editing and mixing. It’s a full time job. There are other people on this forum with a ton of experience and a ton of skill. Maybe be a bit more humble.
3 Likes
I will support any worthy feature request, because I know SB’s time is limited.
I don’t have an emotional attachment, to this particular feature, even if I pre-empted it into existence but the fact remains, it is over a decade since this particular feature set has been looked at, and I know I am not alone:
Hi emotive, i see you bring a new card in this card play, oké, this mouse, do you have a mousewheel?
A optical mouse that you must move have the mousewheel between the mouse buttons.
But with this type of mouse, you move the ball to move the arrow (cursor)
So, i do not need Autoscroll so much, but it is usefull anyway sometimes.
If you do not have a mousewheel on this mouse, you better get a mouse with a mouse wheel.
Then i learn you how you can scroll by yourself.
That goes much faster.
Yes, it is but only sometimes.
and what of this, particular post?
Well, i advice you to read your own words.
We read it to, so then you are not the only now that read that SB time is limited.
We are limited to at this moment, and just are allready forgotten that whole autoscroll issue, offcourse you are here to remember us.
But, the info in this topic that other users give, start at the beginning and read it again.
Because those people are not alone to.
alone enola.
Can you see the concept?
P.S.
the solution is:
get yourself a mousewheel.
First the solution was to abstain from using Autoscroll, now it is to get a mousewheel.
Zoom, as it can suddenly (seemingly randomly) bring an area of the screen into focus, far from the previous zoom level, is just yet another annoyance that SB have not addressed, which feeds into the overall annoyance of the Autoscroll feature.
I am starting to wonder if some people here, besides my bringing their professionalism into question, are also potential apologists for SB, or in the very least, Fanboyim is rife.
Hi emotive, yes indeed it is changing every minute now, but, you give step by step the information, while you concider the next question:
Is this a topic for an ISSUE to get a solution fast?
Or:
Is this topic a request for the developers and your request works better for everyone, or for people that do not have a mouse wheel?
Now, in this world you can compare many things so listen to me, i am gonna tell you this only ones:
Cubase without a mouse wheel is like a mill without wings.
The millstone does not turn with the wings in the wind, and the millstone cannot grind the grain.
Bread and beer are waiting…
If there are no wings to turn the heavy millstone, you need donkeys.
Of course, this equation will not get you there.
But with a mouse wheel you can:
Where you point with your mouse arrow in the editor:
scroll up and down
With the Ctrl key pressed, zoom in and out to the place where you point with your mouse arrow.
With the Shift key pressed, scroll to the rigth and to the left.
The fastest way to scroll.
Do you want more equations? Then take math lessons, math is Greek in the roots, and equations are always used there too.
In constants and variables.
Computers, it was not that simple.
In 1985 Microsoft launched Windows 1.0, which crashed because the kernel was overwritten when RAM was full, the first idiot proof system, was it still a bit idiotic?
Yes that was 1985, the multifunctional operating system could load more programs into memory than 1 as in DOS.
but that is offtopic because it was no longer about autoscrol: an Issue or a Request?
separate those 2 first.
I do use Zoom of course, either via the magnifying glass or else zoom buttons, with the former not being so reliable, hence feeding into the overall annoyance of the application.
If Autoscroll when suspended would actually stay suspended, i.e., when clicking in the timeline; that would be a great start, so there is FR no.1
FR no.2 would be, to not have Autoscroll switch on because of a transport start event but that would seem more troublesome, as in when or in what particular situation, would it actually be useful to have it turn back on.
FR no.3, Autoscroll often turns back on when edging towards the right of the display, this is not at all useful for me, and is aggravating in the extreme so I don’t see how zooming or manual scrolling actually addresses the problem(s) but I do appreciate the conversation.
Best,
Hi, at this way you have described your issue in a better order, with less chaos because of the annoying moments.
We as users, offcourse, can give you the advice (agian) to do your request, or you did that allready, but in an order, that you always can use the F button till there is some changings by an update.
Users can not write new updates.
And maby, we can look for more things, that can be nice as a request.
So in the future you can see those 2 as 2 different lines of ask for help.
A request or an technical issue is more for the developers, and users try to give you advice, and are not stupide.
Offcourse i can consider people without a mousewheel use Cubase as a digital invalide.
As if you miss that after you use that.
But, offcourse you can make your own decisions.