RTFM?

[MrFigg]

Right…Reason. I’ve never RTFM. I’ve kind of just puzzled through over the years and maybe looked in the manual once or twice for a specific function on a specific device and then not really understood it all out of context anyway. My own workarounds for things which I’m guessing don’t even need a workaround. Doing stuff and then undoing it in the edit menu and redoing it until it kind of works.
So…should I read the manual? Like really read it. I’ve got the time. Maybe take a chapter a week. Look in it as a course. Learn everything I can about Reason and then some.
Should I? Maybe. I don’t know. Or…should I?

[Chizmata]

the reason manual is really good actually

[jam-s]

Yes, it's very well written.

[Chi-Individual]

I actually started reading it in December when I got a new laptop. I can honestly say I’ve learned tons that I should’ve known years ago. Still working thru it though.

[DaveyG]

I read the Reason 9 manual from start to finish. Since then I've just dipped in to the later editions.

[Baylo]

Yes - you should. It’s very accessible and full of good tips. I remember reading the physical copies that came with the early, boxed versions of Reason and was shocked (but shouldn’t have been) to see how big it is now. But it is still an excellent resource.

[BRIGGS]

....and RTFM for your devices.

[PhillipOrdonez]

Do it!

[BRIGGS]

I had a printed Reason 4 manual, in the bathroom for years.

It's good reading, when you're away from the computer, taking care of 'the business'.

[dvdrtldg]

Yep well worth it. Lots of tips & tricks in addition to all the how-to info

Problem for me is that I always come across some cool tip or feature in the manual that inspires to me open Reason and start futzing around. Hence, I only ever RTFM in small chunks

[rorystorm]

I RTFM for everything. I have almost all of them saved to a folder. I read them for fun, even, because some of them are fantastic in themselves. The Jiggery Pokery ones for eg are works of freaking art.

[Oenkenstein]

Yes, you should. It took 63 days to write the Operation Manual for the Rumbler Compact Synthesizer. It hurts to read a remark someone never reads a manual. Please do yourself and the developers a favour and open those bibles.

[motuscott]

I've never read the Reason manual cover to cover, but I'm in there all the time. Most RE manuals are shorter and I do the whole thing. Reason manual is well written though.

[orthodox]

Yeah, why not? Especially if you're stuck in monotony. You could find real pearls of wisdom there that would change your life forever.

[arnigretar]

Just take your time and read it It's a good read and you always learn something on the way. I read Reason 5 or 6 manual back in the day -- after being here since v1. But I haven't read the newest ones , only about added new devices. You just reminded me I maybe should read Reason 12 manual, since there might be some tricks and treats in the sequencer part I don't know about or have forgotten.

[arnigretar]

I had a printed Reason 4 manual, in the bathroom for years.

I did the same lol. When I had the Reason 5 or 6 manual -- it was a good toilet read. Got some great moments then lol.

[MrFigg]

Ok then. From the start or delve in randomly?

[Chi-Individual]

I’d say start from the beginning. Most of it was skimmed over when I read the first few chapters because I’d figured out most things just from using Reason. But like most have said, you still find great tips and tricks. For me, so far, it’s been learning all the keyboard shortcuts I’d never known about. Just reading and learning those has been game changing. So I’d say start fresh and if you know that section just skim over it.

[BRIGGS]

Ok then. From the start or delve in randomly?

I doesn't read like a story, so the are no spoilers.

[motuscott]

Either way.
Just make sure you're on the throne.

[mcatalao]

Reading manuals is very tedious.
HOWEVER you should because it's worth it! Specially reason's one, it's quite often that you have 2 or 3 ways to do something and reading the manual you will learn it inside out.

Also, I find A LOT of user rants could be self solved if the user would give himself the trouble of checking that area of the app in the manual. I guess a lot of bytes in ReasonTalk's and Facebook's database could be saved... Oh well!

[lowtom]

Spare yourself online embarrassment - RTFM!

[DaveyG]

[MrFigg]

Also, I find A LOT of user rants could be self solved if the user would give himself the trouble of checking that area of the app in the manual. I guess a lot of bytes in ReasonTalk's and Facebook's database could be saved... Oh well!

To be honest with you I think that being able to come on the forum and ask specific questions about Reason stuff even if the answer is in the manual is one if the things which has made the community. Even if it’s in the manual the discussions generated are like a knowledge database .

[mcatalao]

To be honest with you I think that being able to come on the forum and ask specific questions about Reason stuff even if the answer is in the manual is one if the things which has made the community. Even if it’s in the manual the discussions generated are like a knowledge database .

I've always thought the forums should be extra to the manual. They give you context where the manual can't, bridging the gap between technique, execution, artistry, workflow. This is imho the benefit of these forums. But hey, it's a free forum, right?