View Single Post
Old 01-30-2017, 01:57 PM   #12
storyteller
Human being with feelings
 
Join Date: Aug 2016
Posts: 232
Default

Quote:
Originally Posted by Andrew479 View Post
Anyone should gather knowledge IMHO and build their own orchestral template based on what they have available. It's made for specific workflow and one gets to know their content, as well as all the routing capabilities of REAPER. One size fits all solutions tend to be messy, bulky or expensive.
I don't disagree that knowing what is going on beneath the hood is important. That appeals to certain mindsets. But that's also like telling everyone they should manufacture their own car, build their own house, or do the plumbing themselves. Some people actually do all of those things. Some would rather just live in the house, drive the car they picked out, or call a plumber when there's a clog. Some will stand over the plumber's shoulder to figure out how to do it for themselves the next time.

But OTR might actually surprise you. It isn't built for a pre-made workflow. It is built for everyone's workflow. Using the car analogy, it doesn't enforce everyone to take specific roads to the destination. But it does serve as a GPS system that helps navigate the route and gives the user a set of luxuries that makes driving enjoyable. The alternative would be given no directions, then using hand signals while driving, and eventually having to stop and ask others for directions when lost. The alternative is actually more messy.
storyteller is offline   Reply With Quote