Procedure for reporting errors in or ommissions from the User Guide

[nicholas]

Thanks! will fix.

[soundpebbles]

Chapter:
1. Setting Up and Getting Started

Section:
1.12.1 Setting Up For Audio (PC Windows)

Page reference:
Page 22

Error:
"...If your sound card includes ASIO drivers then most probably these should give you a satisfactory perfprmance..."

Fix suggestion:
"...If your sound card includes ASIO drivers then most probably these should give you a satisfactory performance..."

[nicholas]

Thanks, fixing!

[MonkeyBars]

Hi Nicholas! Thanks so much for your User Guide.

I know it must be a little tedious, but do you have any plans to link the index entries?

[nicholas]

I agree that would be helpful. As far as I am aware, though, Libre Office doesn't make this feature available. If anybody can correct me I'd be delighted.

[MonkeyBars]

Heads up about this change coming in the next version. This will help a lot to avoid confusion between track/media lanes and takes. I recommend you sweep the UG to replace occurences of "take lanes" with just "takes" as well. Thank you

+ Menus/Actions: refer to "takes" instead of "take lanes" everywhere, to avoid ambiguity with media item lanes

[nicholas]

Thank you. I do follow the prerelease versions closely (as I have been doing for the last 12 years) and have already done this, and also incorporated about a dozen or so other changes into the document ready for the next release.

That's how I am able to.publish the latest updated version of the User Guide the same day the software is released.

[MonkeyBars]

Please add a mention of the "Sync to arrange view" MIDI Editor option to Chapter 13.

It's also listed as "Toggle sync to arrange view" which appears to be a dupe...

[nicholas]

Apologies for the delay in replying, I've been off the grid for the last 5 or 6 days.

As far as I can tell, this essentially does the same as the MIDI menu command View, Piano roll timebase, Sync to project - but I'm quite happy to add these actions to the Actions table in Chapter 13.

If you can figure out any differences between the menu command and the action, please let me know,

[MonkeyBars]

Originally Posted by nicholas

If you can figure out any differences between the menu command and the action, please let me know,

I thought timebase was quite a different setting, but I can't tell in this case – regardless, the wording is completely different so it probably should be mentioned separately.

[nicholas]

No worries, already done, will be in next edition.

[djaychela]

Thanks for the User Guide - I know how much work is needed to create something like this, so I wanted to point out some minor typos (and thank you for your work!)

P55 - says "HX" - should be FX?
P119 - "Before exploring these, there are some basic 4concepts" - should be concepts
P120 - "To split on44e selected item" - should be "one"?

Darren

[nicholas]

Thanks for this. It's that damned 4 key - keeps jumping under my fingers!

Will fix in next update!'

[MonkeyBars]

Hi nicholas!

- Was just searching for a mention of the capability to arm actions in Reaper in the User Guide and couldn't find anything. Is it in there somewhere? If not, it definitely ought to be.

I had to ask my friend how armed actions trigger (every item left-click).

- The other item I'd like to mention as missing in the User Guide is an important feature (released in version 2 15 years ago!) that's very hidden: relative edit edit mouse modifiers. These enable the user to edit a bunch of selected items' edges and fades in one mouse movement.

[nicholas]

Thanks ...

I'm working on relative edge edits right now, will be in next update.

I'll dig around into armed actions as well, but probably won't make it to next release.

[sockmonkey72]

I have a "feature request" for the docs which might not be easy to deal with the in short term, but maybe it's something to consider.

I just picked up a bound copy of the manual from Lulu. I waited until 6.67 was released to order, and although 6.67 was written on the website when I pulled the trigger, I got a 6.66 manual. That's fine, of course, I'll live. But it got me thinking that for the months between 6.66 and 6.99, I would like to have a compact way to apply the updates from version to version to my print copy.

So for instance, I want the 10 updated sections formatted as a single addendum document for 6.67, rather than having to jump around the hyperlinks in the PDF.

Maybe it's a lot of work for little payoff, maybe it would make more sense to do every 10 updates or so, but it would be a nice companion to a printed copy of the manual, which is necessarily outdated the moment it arrives. Thanks for considering the idea, or anything along those lines!

[MonkeyBars]

Originally Posted by nicholas

I'll dig around into armed actions as well, but probably won't make it to next release. It would help me and be a time saver if you're able to give me a simple example which uses this

Yes, I don't blame you on that as I also lost track of what it does too.

It's not just a scripting thing – any action can be armed.

If you right click on a toolbar button (that isn't set to do something else on rt click) and the button turns red or select an action such as "Arm next action", that action will trigger every time you left-click an item.

There are myriad use cases such as add item to selected group, color item, etc etc...

[nicholas]

Originally Posted by MonkeyBars

Yes, I don't blame you on that as I also lost track of what it does too.

It's not just a scripting thing – any action can be armed.

If you right click on a toolbar button (that isn't set to do something else on rt click) and the button turns red or select an action such as "Arm next action", that action will trigger every time you left-click an item.

There are myriad use cases such as add item to selected group, color item, etc etc...

Thanks for this, apologies for the scripting comment (which I've since edited out of my post), I was mixing it up with something else.

Hopedully I'll get this into the enxt update!

[nicholas]

Originally Posted by sockmonkey72

Maybe it's a lot of work for little payoff, maybe it would make more sense to do every 10 updates or so, but it would be a nice companion to a printed copy of the manual, which is necessarily outdated the moment it arrives. Thanks for considering the idea, or anything along those lines!

This idea makes sense, I'll need to mull it over though to figure out if and how it could be implemented.

[nicholas]

@monkeybars:

It seems to me that section 15.25 of the User Guide, Creating Smart Tools, is very close to what you're asking for. The main difference is in terminology (easily fixed) and that the explanation/description is incomplete and inadequate - again, easy to fix.

I'll clean this up for release 6.68

Thanks again for pointing this out.

[nicholas]

Originally Posted by sockmonkey72

I just picked up a bound copy of the manual from Lulu. I waited until 6.67 was released to order, and although 6.67 was written on the website when I pulled the trigger, I got a 6.66 manual.

Unfortunately, due largely to time zone differences, there can be a gap of up to 24 hours before the hard copy is updated on the LULU web site.

The trick is to check either the graphic on the web page, or the descriptive text, both of which will show the version number.

[nicholas]

Originally Posted by sockmonkey72

Maybe it's a lot of work for little payoff, maybe it would make more sense to do every 10 updates or so, but it would be a nice companion to a printed copy of the manual, which is necessarily outdated the moment it arrives. Thanks for considering the idea, or anything along those lines!

Would it helped if along with each release we also published a separate document of a few pages which contained only those sections which were new or had major changes. Probably to keep it simple and not include minor tweaks here and there, which are listed in the page 13 changelog anyway.

If you'd care to PM me with your email address I'll send you a sample mock up of what I'm preparing for 6.68 for your perusal.

[sockmonkey72]

Originally Posted by nicholas

Unfortunately, due largely to time zone differences, there can be a gap of up to 24 hours before the hard copy is updated on the LULU web site.

The trick is to check either the graphic on the web page, or the descriptive text, both of which will show the version number.

Thanks, I did wait for the description text on the site to update, but again, not a big deal. A 6.66 manual is also cool.

[_Stevie_]

6.66 is pretty epic!

[MonkeyBars]

Originally Posted by nicholas

I'm working on relative edge edits right now, will be in next update.

I recommend adding a note that this mouse modifier means that all selected items get their edges and/or fades edited in tandem. I find the name quite confusing and doesn't express this clearly

[nicholas]

Originally Posted by MonkeyBars

I recommend adding a note that this mouse modifier means that all selected items get their edges and/or fades edited in tandem. I find the name quite confusing and doesn't express this clearly

Yes I've been struggling a bit with the wording. It helps me to think that relative means relative to each item's position.

[MonkeyBars]

Hi nicholas,

I was looking in the User Guide for an explanation to the change made to the track routing parent channels UI. There is now an additional dropdown which allows the user to choose how many channels to send to the parent (I think?). And next to that is the old dropdown, it appears.

I actually don't understand the change and was looking in the User Guide for info, but all the sections on parent channels have screenshots from the old routing dialog UI.

If you or anyone else understands the new UI, please respond here.

[nicholas]

Looks like I've missed something. I will investigate and include in next update. Thanks for posting ...