> > 46. The manual, in general, needs more "Step by step" examples > > of doing common tasks and more screen shots. The manual seems to > > concentrate more on "what" the program can do rather than on "how" > > to do it. > Yeah, task based rather and common work strategies would be good for the tutorial. How to time correct. How to record audio. How to edit midi using linked windows. How to bounce a mix or bounce a track. The common stuff. > I agree 100%. The manual has been overhauled a couple of times in the Yeah, it is better in a lot of ways. Its now written in plain English and to the point. No more references to "fenster" or snide jokes. But in some ways it somewhat better before in that it was compartamentalized and seemed to have more screen shots. I also wish there was a "Whats New" brochure - or at least put a star next to the new features so someone using logic for 10 years can get and upgrade and not have to read the manual cover to cover. > last two versions, but the basic problems with the manual remain. > Features are still undocumented that preclude continued use of > previously useful pages. Yeah, like a complete lack of info about the all of the many ways of editing track automation ... except the never before seen "track automation event list" which is advised against. > For example, has anyone figured out how to use the "Choose" feature The thing I think is really important for the manul and the online reference ... is to put in common English words. Suppose you want to MOVE a note or region. You will get nowhere unless you know the magic word "Nudge". There's also some lack of consistency in using the same term in different parts of the key commands too.