Horizontal scrolling

Is there a shortcut key to scroll the project window back and forth horizontally? I’ve looked everywhere and can’t find anything about this. I set my Logitech mouse up to do this with the wheel but it only lasted a minute or two until Cubase puked all over the place!

There are times I think the engineers who designed this interface are totally disconnected from reality :angry:!!

If you shift+scroll it moves horizontally.

Thanks, Raino. I’ll give that a try.

It’s so sad that basic functions like these take so long to find. I couldn’t find it in the documentation or search functions. It’s these little things that completely DESTROY creativity. It’s not like I’m trying to figure out how to do parametric equalization or side chain effects.

It’s so sad that basic functions like these take so long to find.

That’s where videos such as this (which mentions horizontal scrolling) beat the manual (IM0):


Thanks, ieaston. I received a survey from Steinberg about 10 months ago asking me what I thought of their documentation. I said the formats and basic information were pretty good, however there were two major flaws:

  • Their documentation is only written to an expert audience. That is, Steinberg assumes no customer is a rookie or intermediate user.

  • Information is not retrievable. As per the subject of my post, the most basic operations are difficult to find. Even when information is well written, it is totally useless when users can’t find it!

I told them I was a technical writer and technical writing instructor, and that their documentation needs a lot of help. In true Steinberg fashion, I never heard back.

In a previous life I had to on occasion hire (rent actually) tech writers and approve their results. I think the current docs are decent reference manuals with all the limitations that implies. They really need some sort of “how to” guide to fill the gaps. While videos can be great, one advantage of a manual is they are easy to skim through - videos not so much.

They really need some sort of “how to” guide to fill the gaps.

Quite agree. Being a teacher, we’re constantly reminded of different learning styles. I quite like reading technical manuals, but can see the benefit of videos for those who like to be walked through.

Just as an experiment, I searched “horizontal scrolling” in the manual, finding 55 documents, none of which seemed remotely relevant. The closest showed how to zoom using the on-screen slider: much fiddlier than using a mouse! 10 seconds in YouTube, I found this: https://www.youtube.com/watch?v=mUzsLsnWZh0

Excellent points, guys. Besides teaching technical writing at a college in Toronto, I also do some freelancing. A lot of my clients’ documentation is written by the engineers and secretaries, if you can believe that. That’s like having your large animal veterinarian perform a hip replacement on you instead of your orthopedic surgeon. Both doctors are highly skilled and well trained but your orthopedic surgeon specializes in human hips. He or she is your best bet.

I’d wager, the Cubase manuals were compiled by someone who read over the engineering notes and just summarized them. Summarizing subject matter expert notes is only a starting point toward usable documentation. Just like my doctors analogy, it takes a specialist to get it 100% right.

My Yamaha Genos comes with two manuals: a User Manual and a Reference Manual. The User Manual provides all the basic functions. It is well-geared toward the user who wants to open the box, set up their Genos, and play it for enjoyment in their living room. The Reference Manual provides in depth information for those who wish to explore the advanced functions.

Steinberg needs to write a User Guide for the novice and intermediate audiences and while they’re at it, fix the Reference Manual! It’s been proven that well written user documents leads to increased sales.

Thanks for the video links :slight_smile:!

Not only believe it, seen it.

One fairly quick & easy thing they could do to improve the manual is to expand what is listed in the index. It could probably be twice as big or more.

Good point, Roger. In hardcopy media and in the perfect world, the Table of Contents (Contents) is written from the engineer’s or developer’s point of view. The Index is written from the user’s point of view. Therefore, the Index had better cover every possible scenario the user can think of.