Publishing

This page covers what happens after a service is recorded — finding the recording, trimming out the sermon, and publishing it to your podcast feed and YouTube channel.

#The Recordings screen

Open Recordings to see every service recording on this Mac, newest first. Each row shows:

• The service title (or Untitled service if none was linked) and the recording's date
• · still recording if the session hasn't ended yet
• · file missing if the file KERYX expects isn't on disk anymore (moved, deleted, or on a drive that isn't connected)
• The full file path

Each row has two buttons:

• Show in Finder (folder icon) — reveals the file on disk.
• Trim & publish (scissors icon) — opens the Trim screen. This is disabled while the recording is still running, or if the file is missing.

#Import a file…

If a producer edited the sermon outside KERYX (iMovie, Final Cut, etc.), use Import a file… in the Recordings header to pick a finished MP4/MOV/M4V. KERYX registers it as a recording so the normal Trim & publish path — export, podcast, YouTube — works on it exactly like a recording KERYX made itself.

#Trim & publish

Opening a recording brings up the trim screen: a video player, a timeline, and an episode form.

#Transport and setting In/Out

Keyboard shortcuts (shown in the header): I sets In, O sets Out, ←/→ nudge the last-set point by 1 second, Shift held with either arrow nudges by 0.1 seconds, Space plays or pauses, Esc goes back. Shortcuts are ignored while typing in a text field.

The timeline shows the selected clip shaded, plus a tick for every recording marker (a marker where the operator changed plan items during the recording); sermon-item ticks are highlighted in orange.

#Automatic in/out from sermon markers

If KERYX captured markers while recording (the operator was moving through the plan live), it suggests a trim window automatically: it looks for the item(s) that match the sermon (Planning Center items tagged as the podcast segment, or a title containing "sermon," "message," "teaching," or "homily"), starts a few seconds before the first one — set by Trim lead-in in Settings → Publishing — and ends at the next non-sermon marker, or the end of the recording if there isn't one.

If no marker matched a sermon item, KERYX selects the whole file and shows: "No sermon markers were captured for this recording, so the whole file is selected. Set In and Out by hand."

#Episode details

Fill in Episode title, Description, and optionally link a Service from the dropdown. The title and description default from the matched sermon plan item when one was found. The title is required before you can export.

#Export & publish

Pressing Export & publish does three things:

1. Renders a 720p MP4 (for YouTube) and a mono MP3 (for the podcast) from your In/Out selection, saved next to the original recording.
2. Queues a podcast upload job and a YouTube upload job.
3. Starts draining the queue immediately — you can close the screen or quit to the Edit screen and the uploads keep running in the background.

#Podcast and YouTube jobs

Every export creates one Podcast job and one YouTube job. Job status appears on both the Recordings screen (under each recording) and the Trim screen (in the sidebar), and updates live.

Needs attention and Failed jobs both show a Retry button — fix the underlying problem (reconnect YouTube, add R2 keys, confirm the re-upload) first, then press it to requeue the job.

#Connecting YouTube

Go to Settings → Publishing. Under YouTube:

1. Create a Google OAuth client as a "Desktop app", on the Google account that owns the church's YouTube channel, and paste its OAuth client ID and OAuth client secret.
2. Press Connect — this opens Google's consent screen once in your browser.
3. Once connected, Status shows Connected — <channel name>. Use Reconnect if the connection was revoked, or Disconnect to remove it.

Also on this pane:

• Visibility — the privacy setting new uploads publish with: Unlisted, Public, or Private. Default is Unlisted.
• Playlist — an optional YouTube playlist ID; uploaded videos are added to it automatically.

If YouTube's refresh token is ever revoked (access removed at myaccount.google.com, or Google's token expiring/erroring), the next upload job goes to Needs attention with a message telling you to reconnect.

#Podcast settings

Also under Settings → Publishing, the Podcast group shows:

• Storage — read-only: says Keys set on this Mac if you've pasted Cloudflare R2 credentials locally, or Keys come from KERYX Cloud if they haven't (KERYX then pulls the R2 key pair from the web app's Podcast settings through this Mac's cloud sign-in, so the key pair never has to live on the church Mac at all).
• Trim lead-in — seconds before the sermon item that the trimmer pre-selects (0–60, default 3).

A disclosure labeled Podcast storage keys lets you paste a Cloudflare R2 account ID, bucket, public URL, access key, and secret directly on this Mac, overriding the pair saved on the web app. Leave these blank unless you specifically need to override the shared keys.

#Where the podcast feed lives

Episode audio uploads to Cloudflare R2; the RSS feed that podcast apps (Apple Podcasts, Spotify, etc.) subscribe to is served by the web app at keryx.samuraicode.ai/podcast/feed.xml. The public show page is at /podcast, and the episode list/management view is at /podcast/episodes on the web app.

#Re-uploading

Exporting the same recording again queues new podcast and YouTube jobs:

• Podcast: re-running always replaces the existing episode (same show GUID, same storage key) rather than creating a duplicate.
• YouTube: re-running asks you to confirm first (see the Warning above), because YouTube has no equivalent "replace" — confirming always creates an additional video rather than replacing the first.

If uploads fail partway through (recording won't start, computer sleeps, network drops), the queue backs off and retries automatically — you don't need to re-export unless the job reaches Failed.

For streaming and recording controls themselves, see Recording and Streaming. For every setting on the Publishing pane and the rest of Settings, see Settings. If something in this pipeline goes wrong, check Troubleshooting.