I'd welcome as much input from as many here as possible, to help me make a decision here. In addition to many changes in functionality and new features, it's obvious that REAPER 3 will also include a lot of (sometimes stunning) visual improvements. To recreate every screenshot in the manual where the change is only cosmetic would be a huge time-consuming job, and I have to prioritize my time. Take for example, folders. My thinking is to update screenshots with the new software (i.e. no folder button) during those sections dealing with folders, but not to worry too much if on screen shots on other topics the odd folder button might be visible somewhere, in situations where that has no relevance to the topic. My question is also, do people think that it would be misleading or confusing to see the old screen shots (for example, the old Virtual Keyboard or envelopes with square nodes) where the functionality hasn't changed. For the more significant changes I could reference in the text (e.g. "Depending on which version of REAPER you are using, envelope nodes could be square as shown or round", with just one shot showing both styles). I hope this is making sense. Basically I'd like if possible to update the documentation without a complete rewrite being necessary. Comments please ....

I think maybe if you had some kind of caption for the older screenshots saying that they depict an older version, most of the confusion would be lost. That would still be pretty time consuming though, which is a bit of a bugger. Not sure. -Pembo.

Nicholas, I lean toward thinking that the screenshots should be updated. However, I think it's totally OK for you to utilize the power of the REAPER community (as Malevo suggested above). I suggest you write a post like this: Hey everyone, I could really use some help updating the user manual for REAPER 3.0, especially the screenshots. If you're up for it, please reply to this post with the pages in the manual for which you're willing to replace the screenshots. Then, go through and duplicate the manual images with REAPER, take screengrabs, save them as full res .BMPs (name the files PageXImageY.bmp) and zip them up and email me before midnight next Sunday. Please use a WinXP machine with default theme, and reaper v3.00 with the default theme to keep the manual consistent. As I get submissions I'll edit this initial post with what's left to do. And if you decide to make such a post, I'll reply with: Sure, I'd love to help! I don't have a ton of time, but I think could definitely handle the shots on pages 1-25 for you. :D Not sure it would work for the entire manual, but worth a shot?

nicholas, I think that Art's suggestion "a summary addendum of the changes" would be the appropriate way to go. At least intially. Then, given time and energy you could step by step update the manual, using this forum as help on updating the screen shots. And, just like bullshark says, there is redundant material that could be edited out. Not only similar screen shots, but also similar text in different places. Editing this out (you know, "kill your darlings" :-) would provide a cleaner document that is slightly easier updated. You've done a really great job, but don't let the work load drag you down.

Guys, I know you're both trying to help, please don't fight on my account... ;) To everybody else, thanks all for your input, all and any more comments, ideas, advice etc. will be gratefully received...

I suppose a lot of screenshots will need updating eventually for clarity, but there may be others where it serves no purpose, in fact I would go so far as to suggest the old S/s might add a little charm and interest. So while a lot of them still hold good, I would suggest where there is some chance of misinterpretation they ought to be changed some time soon-ish, but maybe hold fire until more changes in the actual software - lest you have to change them all again It could be made clear in the introduction that S/s spread over a number of versions and each S/s has a reference. This could be done by date, manual version, or some sort of visual code etc. I like that Reaperites can be involved, but lets remember if I can see no particular reason to change all of the S/s now, getting users to work on a set of pages is going to add unnecessary work. Also all this stuff has to be up/down-loaded and sorted. I'm not sure how much easier that would make it in practice. Don't forget either while our user base is very willing in general, there may be times when volunteers won't be able to meet their commitment and that could mean a hold up. :( I tend towards an enlistment of a few known good helpers, and creation of a team for Nicholas to delegate duties to, such as updating older parts of the manual to free up Nicholas' time to work on new features. People often put themselves up for doing stuff that later turns out to be rather demanding and this should be avoided - in fact pressure and stress should be avoided PERIOD! :D Everything in this thread is valid, even the things that disagree with the other things :D.

[QUOTE=nicholas;255238]Guys, I know you're both trying to help, please don't fight on my account... ;)[QUOTE] I had no idea we were fighting :D

In the fullness of time, I'd be more than happy to churn out a load of screenshots for you, as I'm sure would some other chaps I could round up. If the sizes were kept the same as the shots they'd be replacing, you could just drop them across, and that should minimise your workload. Meanwhile, you could also write a big list of the new shots you'd be needing, and we could just work our way through them.

Hey Nicholas, the only thing I ever found to be a little disturbing reading the manual is that the screenshots are coming from different themes. IF you/we are gonna dive into this nightmare of rebuilding every screenshot, then it should be done with Reaper set on the default theme IMHO.

my 2 cents: Yes, I'd help to create screenshots (and I'm sure many others would too). Yes, I find it irritating to have screenshots with different skins/looks/elements. Not for me but for beginners ("well, how do I make it look the same as in the picture..."). Reapers community is so thankful about the quality of the product and the responsiveness and being involved in the whole process. The result is a huge manpower waiting to be used. The biggest problem seems to be the coordination of it all, but I guess it will take less time than you doing the work yourself. Oh, and thanks for your dedication anyway, nicholas !