OA VAULT 42 · USER & ADMIN DOCUMENTATION

42-day radio archive operations guide.

How to understand, use and administer Radio Vault 42: continuous stream recording, hourly MP3 archives, access control, 42-day retention, health checks and export workflows.

24/7 recorder1-hour MP342-day retention1,008 hourly slotsFFmpeg
OA Vault 42 All Recordings archive interface
01 · OVERVIEW

What OA Vault 42 does

OA Vault 42 (Radio Vault 42) is a dedicated radio recording/archive service. It pulls an existing direct HTTP/HTTPS station stream, records continuously with FFmpeg, creates clock-aligned one-hour MP3 files and maintains a secure rolling 42-day archive.

Service characteristicWhat it means
24/7 supervised recordingThe recorder is designed to run continuously against the configured station stream.
Clock-aligned hourly filesEach day is organised as 00:00–01:00, 01:00–02:00 and so on through 23:00–00:00.
42-day rolling archiveNew recordings enter the retained window while expired recordings age out.
1,008 hourly slotsA complete 42-day period contains 24 × 42 hourly recording slots for each channel.
Controlled accessAdministrators manage recording channels and user access; authorised users can play/download assigned archives.
02 · RECORDING PIPELINE

From live station to retained archive

Use the station’s existing direct listen stream

Vault 42 works as a retention layer beside the current radio platform rather than replacing the listener-facing stream.

FFmpeg records the stream continuously

The capture process consumes the configured HTTP/HTTPS audio source and produces the archive stream.

Files are aligned to the clock

The output is divided into predictable one-hour windows instead of arbitrary recording chunks.

Completed MP3 files enter the secure archive

Users browse by recording channel and archive date, then review the hourly slots.

Retention rolls forward

Older segments expire as the archive moves beyond the configured 42-day window.

03 · ACCESS

Administrator and channel-user access

The supplied Vault interface separates administrative functions from archive access.

  • Administrators manage recording channels, service state, users/access, plans/billing, notifications and system health.
  • Channel users sign in to play and download archives assigned to their account.
  • Sign-ins and administrative changes are represented as protected/auditable access in the supplied interface.
Give each user only the recording channels they need. Vault 42 is intended to keep archive access controlled rather than exposing recording files as a public directory.
04 · USER GUIDE

Using All Recordings

The All Recordings screen is the core day-to-day archive view.

Select the recording channel

Choose the station/channel whose archive you are authorised to view.

Select an archive date

Open a retained day within the 42-day window.

Check available hours

The daily view shows each hourly segment and whether the file is available.

Play a segment

Use the built-in audio player to review the selected hour in the browser.

Download only what you need

Use the download action for the exact hourly recording that needs to be retained locally or supplied for review.

A newly completed segment can appear after the recording file has finished being created. The dashboard wording in the supplied interface makes this explicit.
05 · ADMIN GUIDE

Vault administration areas

The supplied administrator dashboard exposes the service lifecycle around the archive.

AreaPurpose
Admin DashboardHigh-level service and recording overview.
All RecordingsBrowse archived days and hourly recording files.
Recording ChannelsManage station sources and recording services.
Billing OverviewReview billing/service visibility for the account.
Service OrdersTrack/provision Vault-related service orders.
Users & AccessControl which users can access which recording archives.
Plans & BillingManage plan/billing configuration exposed by the service.
Email NotificationsConfigure operational/account messaging.
System HealthReview recorder/service health separately from archive browsing.
My ProfileAccount profile and sign-in details.
06 · RECORDING CHANNELS

Provision a station recording source

Each recording channel needs a reliable direct station listen URL and the correct operational timezone/context so the archive is meaningful to the broadcaster.

Recommended onboarding checklist

  • Confirm the station’s direct HTTP/HTTPS stream URL is stable and reachable from the recorder.
  • Confirm the correct station/channel name.
  • Confirm the timezone that should be used when presenting clock-aligned archive hours.
  • Start the recorder and verify the source remains connected.
  • Wait for the first completed hourly segment and check playback.
  • Assign authorised users to the channel archive.
Do not use a web player page URL in place of a direct audio stream URL. Vault 42 needs the actual audio stream endpoint.
07 · RETENTION

How the 42-day rolling archive behaves

Vault 42 is designed around a bounded retention period. For a fully populated channel, each day can contain 24 hourly files and the full 42-day window can contain 1,008 hourly recording slots.

  • New files are written throughout the current day.
  • Completed hours become available for playback/download.
  • Older days remain accessible while they are inside the retention window.
  • Expired material is removed as the rolling window advances.
If a recording must be kept longer than the rolling Vault window, download/export it to an authorised long-term location such as OA Storage Box before it expires.
08 · OPERATIONS

System health and notifications

Archive browsing and recorder health are different concerns. A clean archive interface does not by itself prove the source recorder is currently healthy, which is why the supplied product includes separate System Health and Email Notifications areas.

Operational checks

  • Confirm the station stream is reachable.
  • Confirm recorder service is active.
  • Confirm completed hourly files continue to appear.
  • Check file sizes for unexpected zero/very small output.
  • Verify a sample file actually plays.
  • Use notifications for meaningful recording/service events.
09 · SUPPORT

Troubleshooting common archive issues

IssueWhat to check
An hour is missingCheck source-stream availability and recorder health for that time period; verify the hour has completed.
Player shows no usable audioVerify the generated file is non-empty and the input stream contained valid audio.
User cannot see a channelReview Users & Access and confirm that recording channel is assigned to the account.
Recorder repeatedly disconnectsTest the direct HTTP/HTTPS stream independently and review the recorder/system-health state.
Archive date unavailableConfirm the date is within the retained 42-day window and that recording existed for that channel.
Need to keep a recording longerDownload/export the required file before its Vault 42 retention expiry.
10 · RETENTION NOTE

Broadcast record keeping and licensing

Vault 42 is built to support broadcaster recording-retention, evidence and audit workflows by keeping a predictable rolling record of what the station transmitted.

Important: exact recording obligations, retention periods and licensing requirements vary by broadcaster, licence, regulator and jurisdiction. A 42-day archive is a technical retention service; it does not by itself guarantee that every station has satisfied every licensing or regulatory requirement.

Need help with OA Vault 42?

Use the project/support contact route for provisioning, migration, platform configuration or a custom deployment.

Contact OACAST ↗