OTR + Reaticulate please feel free to share
Will thank you so much for this thread. I too really hope it gets some interest. I was tipped to this thread by Jonathan of Storyteller (developer of OTR) and having developed a fairly sophisticated REAPER project this year that handles a whole pile of live audio issues for twitch live streamers, I have become a real fan of the incredible hard work Jonathan has done in creating and supporting OTR especially all these years and particularly after deciding to change it to a free-or-pay pricing model from its original extremely reasonable price. I can remember seeing all these “no template is worth $200” (it was $189) posts from people in 2017 when he released it; and I can only assume those people by now have had a chance to see how much time it saves and their opinion has changed.
I’m probably a pretty typical REAPER user; I have a couple of sample libraries, a lot bundled or free VSTs, and a need probably much greater than I realize to cut down the amount of time I spend on setup of all that to more efficiently produce content. I am trying to figure out an approach that will tie all my sample, synth, and process choices into a unified template, and I see OTR as my best-bet approach. But wait! Another learning curve lol.
Jonathan at OTR put together a frankly magnificent array of walk through and tutorial videos to support OTR, but as all DAW users know, every use case is different.
Everything seems to boil down to learning. So I’d like to learn how to create that “perfect” template for my ragtag collection, and even though I haven’t got EWCC at this time, thanks Will for echoing OTR’s (ie Jonathan’s) ethos in offering OTR, and sharing.
I would throw in another wrinkle to up the efficiency and utility aspect: and that’s the incorporation of Reaticulate into the workflow. That would seem to be a super matchup with OTR.
SO all I have to do is learn how, and then do all of it lol. Please, continue!
|