1) Sermon Recording

Sermon recordings for Calvary Chapel Redmond are done using Audacity an audio editing freeware that can be downloaded here: https://www.audacityteam.org/

2) Sermon Editing

After sermon recording is made save a backup of the audacity project before making edits. You may then need to amplify the sound and reduce background noise.

a) Start by selecting the entire audio track

  • You can do this by clicking the Select the box on the track
Select Audio

b) Amplify the audio (I usually find 12.0 dB good for Calvary recordings)

Effect > Amplify...
Set Amplification, Allow Clipping, Hit OK

Amplification may take a little while. Be Patient.

Remove background static

Removing background static is a two part process and can take a little fine tuning. This is where it's definitely good to make sure you made that backup before editing, if you do noise reduction wrong it may make Mike sound like he's in a tin can!

First select a section of the audio that ONLY has the background or white noise.

Select some white noise

Second: get a noise profile of that section through the Noise Reduction window:

Effect > Noise Reduction

Open Noise Reduction
Get Noise Profile

Once you click the Get Noise Profile button the window will close. The profile for the selected section is in Cache and now you need to select the audio to apply the reduction to. In the case of sermons, you want to apply the reduction to the entire sermon (to cut out that static behind the speaking).

Select the Track (again)

Effect > Noise Reduction

Open Noise reduction Again

You may want to fiddle with the settings or not. Preview the changes if you're uncertain. When ready hit OK:

Apply Noise Profile

This will take more time than Amplifying the audio. Be more patient.

If you're please with your changes, then it's time to export an MP3 of the sermon.

3) Sermon Exporting

So you're ready to export the sermon audio as an MP3. You've finished your edits and are happy with the quality. This is pretty straight forward.

File > Export > Export as MP3

File > Export > Export as MP3

You'll be asked to give a file name. For convenience I like to title the sermon using the following template:

YYYY-MM-DD_BOOK_CHAPTER_PART

# Example:
2019-12-08_Colosians_4_b
IMPORTANT: The file name should avoid spaces. Hyphens and Underscores are safer. The reason for this has to do with fragility once the file is moved to a server for streaming. HTML String encoding usually converts spaces into a %20 which can confuse some file servers that interpret that command literally. Avoid the headache altogether by avoiding spaces in the file name.
Pick a Name. Quality: 80kbps is usually safe. Hit Save

Once you hit save you'll be asked for some metadata about the mp3. Make sure you know where you're saving it to (I usually stick it in OneDrive in the Archive / MP3 section).

Artist Name: Calvary Chapel Redmond
Track Title: ...keep it similar to the file name...
Album Title: Book Series (or topical)
Year: <Current year>
Genre: Sermon

Once you're finished with the metadata hit OK and wait.

Sermon Exporting takes EVEN LONGER! Try to be patient. Please.

4) Sermon Uploading

We store our sermons on the Amazon S3 ccr-sermons bucket:

If you're not already logged in you'll need to get credentials from Zack. The church laptop usually has the password saved, though.


Sermons are stored in folders by series, choose the most appropriate location to upload. once finished you'll need to make the object public (if this is confusing call Zack). Once you find the folder step into it and hit upload.

Choose a location. Hit Upload.

When the uploading screen appears select the file.

Make sure the Object permissions are Read / Write

This is a bit of a security risk, but it's the only way to make the sermon publicly available for streaming.

Make sure Storage Class is set to Standard

Different storage classes have different rules and data rates for access. Standard is the best since it has no minimum duration or additional fees for accessing the data.

Hit Upload!

When the sermon is finished uploading select it from the list

Select the sermon you just uploaded

You'll get an overview of the new S3 object. This object manages the access permissions of the Sermon on the S3 cloud.

In order to make the sermon accessible, you need to Make Public

Make it Public

Once it is public, click the object URL

  • If everything worked up until this point you'll open a web page that will automatically play the sermon.

Copy the URL to a notepad or other plain text application (you'll need it to embed a sermon post)

Copy The URL

5) Sermon Embedding:

At this step you should have a valid URL to the sermon audio in a note pad (I'll be using Typora for this example, but any plain text editor will do.

If you're following along from the website, you'll need to open a new tab and head on over to:

You'll see a list of all the sermons posted to the home page so far. You want to create a new Post:

New Post

Give the post a title. For Sermons I typically give it a similar name to the file just to make it easy.

Write any other details you want, something like

Continuing Book chapter Number, Mike teaches us about...

Finally when those details are in place it's time to embed the sermon.

On a new line in the author workspace click the + button on the side It'll expand to display a window with embed options

Embed options

Here you want to select HTML. That'll create a little box for you to paste the following code into:

<audio preload="none" 
       controls="" 
       autoplay="" 
       name="">
	<source src="">
</audio>
Copy / Past this HTML

Go back and copy the sermon MP3 URL and paste it in the source field It should look something like:

<audio preload="none" 
       controls="" 
       autoplay="" 
       name="">
	<source src="https://ccr-sermons.s3-us-west-2.amazonaws.com/2+Corinthians+2018/2_Corinthians_c_11.mp3">
</audio>

Hit publish and head to the home page. If you did everything correctly there'll be a new post in the Recent section with a working audio player. If anything went wrong, talk to Zack.