Old Production Takes From an Old Guy

Reaper Render Templates

Last time, I wrote about using Project Templates to speed up your Reaper workflow. Today, I’m going to talk about another feature I’ve been waiting for since I started using it: Render presets. 

Like many of you, I record the message each week, do a little editing, then need to export a couple versions of the finished product: Our info center still needs to burn CD copies of the message each week, and we need an MP3 to upload to the web. In the past, setting that up required a trip to the Render dialog box, and the changing of quite a few variables. Today, in version 4, it’s as easy as picking a drop down. Here’s how it works.

The first thing we did was create a few project templates to give us the track settings, routing and basic render settings for our normal weekends. You can read more about creating those templates in my previous post.

Once that’s all done, I record the service, do the editing I need to for the podcast, then create a time-range selection to mark my in and out times. Alternately, you could move the track into a blank project if you want to, but I’ve found it’s just easier to keep it all in the weekend project (and all the editing is non-destructive anyway). 

Check out some of the new features in the Output section (highlighted). You can do some cool stuff in there now.

I’ll open up the Render menu (using a custom shortcut I created; Option-Command-R), and enter the title of the file. You’ll also notice that in v. 4 the file name window is now separated from the path window. I really like this feature as it is much simpler to find and edit. As our project template pre-loads the Podcast settings, I simply add this to the Render Queue. 

These are the settings I use for our podcast each week.

Next, I re-open the Render menu and prepare for the CD file. To select the template, I click on Presets, then Options & Format, and my preset, CD AIFF. You can see that the options for the format all change, and the file will now be rendered as an AIFF file. Since our naming conventions are the same for both, I didn’t need to change that. Add to Render Queue and you’re set. Finally, I open the Render Queue—again with a custom keyboard shortcut—and hit Render All. Reaper goes to work rendering the files in both MP3 and AIFF formats. 

Note the different file type and output settings.

To create a render preset, simply set up a render with the options you want, then go to the preset button, choose your category and click “Save preset…” Note that you must add the file to the render queue or render it directly from the render dialog for the preset to be saved. I’m not sure why this is, but closing the dialog box without adding the file to the render queue will cause the preset to be lost. 

Set it up one weekend, and from that point forward, all you have to do is select the preset and you’re all set. 

Do you have any neat time-saving Reaper tricks?

Today’s post is brought to you buy Heil Sound. Established in 1966, Heil Sound Ltd. has developed many professional audio innovations over the years, and is currently a world leader in the design and manufacture of large diaphragm dynamic, professional grade microphones for live sound, broadcast and recording.

8 Comments

  1. tylermckellar@gmail.com

    While I can't say I have any Reaper tricks, there are a few things we do that save quite a bit of time. Our recording machine is a Dell running Ubuntu and we record into Audacity. When we export our service we save it as a mono Flac file for space saving purposes. I wrote a script a few years back that handles everything after that. It firsts backs up the Flac file to our server in a corresponding year folder in the event anything wonky happens. It then uses FFmpeg to make an mp3 and uploads it to our web server. It's a completely hands off process. All we have to do it save the service into the queue folder and we're done.

  2. tylermckellar@gmail.com

    While I can't say I have any Reaper tricks, there are a few things we do that save quite a bit of time. Our recording machine is a Dell running Ubuntu and we record into Audacity. When we export our service we save it as a mono Flac file for space saving purposes. I wrote a script a few years back that handles everything after that. It firsts backs up the Flac file to our server in a corresponding year folder in the event anything wonky happens. It then uses FFmpeg to make an mp3 and uploads it to our web server. It's a completely hands off process. All we have to do it save the service into the queue folder and we're done.

  3. hook@ps139.com

    For anyone using Reaper, I highly recommend checking out the "Reaper 4 Explained" DVD (by Kenny Gioia) from http://www.groove3.com – it greatly improved my workflow in Reaper (I use Reaper for my home recording setup as well).

  4. hook@ps139.com

    For anyone using Reaper, I highly recommend checking out the "Reaper 4 Explained" DVD (by Kenny Gioia) from http://www.groove3.com – it greatly improved my workflow in Reaper (I use Reaper for my home recording setup as well).

  5. yeshua11@me.com

    My Process:
    1.a. iCal event triggers opening reaper and selecting custom command @10:30AM Every Sunday
    1.b. custom command starts a new reaper project, then makes sure all tracks are armed, then starts recording.
    2.a. iCal event triggers bringing reaper to the forefront, then selects custom command @12:30PM Every Sunday
    2.b. custom command stops recording, opens save dialog, (user enters date as a project title), then quits reaper.

    Its all automated and left alone…..(got the idea from your first post on reaper a while back)…never have to think about recording ever again….

    I haven't actually started rendering the sermon or anything because no one has asked for a copy (yes I've made it known that I record and people can ask for it), so I have it more for if someone wants it at this point…..once I get a good way to put it on our website, I'll start rendering every week…..but until then it just takes up some space on my laptop…..

  6. yeshua11@me.com

    My Process:
    1.a. iCal event triggers opening reaper and selecting custom command @10:30AM Every Sunday
    1.b. custom command starts a new reaper project, then makes sure all tracks are armed, then starts recording.
    2.a. iCal event triggers bringing reaper to the forefront, then selects custom command @12:30PM Every Sunday
    2.b. custom command stops recording, opens save dialog, (user enters date as a project title), then quits reaper.

    Its all automated and left alone…..(got the idea from your first post on reaper a while back)…never have to think about recording ever again….

    I haven't actually started rendering the sermon or anything because no one has asked for a copy (yes I've made it known that I record and people can ask for it), so I have it more for if someone wants it at this point…..once I get a good way to put it on our website, I'll start rendering every week…..but until then it just takes up some space on my laptop…..

  7. emmasters2@gmail.com

    That’s such a great post!

  8. emmasters2@gmail.com

    That’s such a great post!

© 2021 ChurchTechArts

Theme by Anders NorenUp ↑