Record
Safer Pro

Record Safer Pro is a multichannel recording safety workstation for macOS. It brings device selection, sample rate, channels, storage, monitoring, alerts and post-recording reports into one workflow: identify risks before recording, report problems early during recording and leave a reviewable record afterward.

It is not a DAW and does not replace editing, mixing or mastering software. Record Safer Pro captures location audio reliably and hands material to Pro Tools, REAPER, Nuendo, Logic Pro or an ADM-BWF workflow for further work.

1.1Capabilities and limits

1.2Suitable work

• Concerts, theaters, forums, lectures, interviews, podcasts and location sound where retakes are difficult.
• Projects capturing many inputs while preserving channel names, colors, markers and timing for post-production.
• Studios and production teams needing a main recorder, backup recorder or safety recorder for immersive capture.
• Users who want a local AI client to assist with session preparation, status checks and explicit operations.

1.3What software cannot do for you

Software can monitor disks, buffers, power and devices, but cannot eliminate loose cables, interface power loss, clock faults, overheating storage or incorrect routing. Prepare spare cables, stable power, enough disk space and a clear channel list. Run a complete test before any recording that cannot be repeated.

2.1Installation

1. Obtain the official installer and install Record Safer Pro in Applications.
2. On first launch, allow audio input, file access and necessary local communication when macOS prompts.
3. If Gatekeeper blocks the first launch, right-click the app in Finder, choose Open and confirm. Do not use untrusted scripts to remove system security checks.
4. Connect the audio interface, external recording disk and stable power before entering the recording wizard.

2.2First-launch checks

2.3Main menu

The menu provides recording sessions, online activation, audio format, system settings, toolbox, About and updates, language and quit. System Settings uses categories on the left and details on the right. Switching categories does not alter saved recordings.

The interface supports Chinese, English, Japanese, German and Russian. The selection applies to the main interface, system dialogs and menu-bar text without changing current session data.

2.4Recording status beyond the main window

During recording, the macOS menu-bar icon changes state, the Dock shows a dot badge and the window title displays REC and elapsed time. Recording remains visible when the window is hidden or minimized. These indicators return to normal after stopping or an error.

2.5Update policy

Use About → Check for Updates. Avoid last-minute app, macOS or interface-driver upgrades on a production day. Update during preparation, then repeat tests with the actual devices, storage and channel count.

3.114-day trial

First launch enables a local 14-day trial with full recording capability. After the trial or a monthly/annual license expires, recording channel selection is limited to two tracks; other features remain available. A perpetual license has no subscription expiry.

3.2Activate with your DADAO account

1. Open Online Activation from the main menu.
2. Choose the default Email Sign-in and enter the DADAO account email and password associated with your Record Safer license.
3. Sign in and wait for online verification. On success, the device's license card shows the plan and expiry.

3.3Use a license key

If your purchase email or support team supplied a key, choose Use License Key in the same window. Paste it to avoid transcription errors. Account sign-in and license keys are different entry points to the same cloud verification and device binding.

3.4Restore and deactivate

• If local license files are missing but macOS Keychain retains device credentials or a key, use Restore License.
• After reinstalling the OS, sign in with your DADAO account instead of manually copying old files.
• Activation, restoration and deactivation require a network connection. An incorrect system clock can also prevent verification.
• Each license permits one user-initiated deactivation every 183 days. Deactivation is for device migration, not a routine switch.
• After deactivation, the local app returns to trial state. You can then sign in or use the key on another device.

3.5License checks before production

Do not leave activation until minutes before the event. At least a day ahead, confirm sign-in, plan, expiry and unrestricted target channel count, then make a short recording. If temporarily offline, avoid repeatedly submitting credentials. Check the network and system time, then follow the interface's retry guidance.

4.1File format and bit depth

The wizard no longer asks separately for bit depth. Save the default in System Settings first. MCP session preparation may specify it explicitly; otherwise it uses 24-bit.

4.2Safe Mode and Studio Mode

Missing live meters or monitoring in Safe Mode is intentional. Select Studio Mode beforehand if needed; do not change modes during recording merely to see meters.

4.3Meter response

• Peak：Observe instantaneous peaks to avoid overload.
• PPM：Faster than VU, suitable for broadcast and general level observation.
• VU：Slower response, closer to traditional average-level metering.
• Loudness：Observe weighted perceived-loudness trends; does not replace post-production loudness compliance measurement.

Version 4.4.0 aligns backend meter response, peak hold and UI decay. Let a meter-type change finish saving before leaving settings, so no unapplied state remains before recording.

4.4Monitor layout and output mapping

Input channels, monitor layout and physical outputs are separate. After choosing Stereo, Quad, 5.1, 7.1, 5.1.4, 7.1.4, 22.2 or a custom layout, verify which physical output carries each monitor channel. Binaural headphones help check positioning on location; final decisions should return to the target monitoring system.

4.5Developer program

You can disable the developer program in System Settings. Diagnostics help investigate compatibility and stability and should not include recorded audio, account passwords, activation codes or license keys. Check this setting against your team's privacy requirements before production.

5.1Prepare a session with the wizard

1. Choose the input device: Verify device name, channel count and connection status.
2. Choose the sample rate: 48 kHz is a practical default for most video, podcast and professional work. Use higher rates only when the project requires them and the entire path has been tested.
3. Set the buffer: Adjust as needed for Studio Mode, live metering or monitoring. Smaller buffers reduce latency but increase system load.
4. Select and name channels: Select all, deselect all or use signal detection to assist selection. Always verify against the actual channel list.
5. Choose the output folder: Prefer an external SSD with ample space, stable speed and good cooling.
6. Complete health checks: Resolve blocking issues with disk space, writing, devices, sample rate and buffers.

5.2Ten-second pre-record buffer

In the recording console, the app keeps up to the most recent ten seconds of input in memory. When you click Start Recording, the available pre-record audio is added to the start of the file to preserve a first beat, opening words or cue before the click.

5.3Channel count and storage

During a valid trial or paid license, licensing imposes no additional channel restriction. After trial or subscription expiry, selection is limited to two tracks. High channel counts, sample rates and 32-bit Float all increase memory, CPU and disk demand.

Actual files include metadata and overhead. Reserve at least twice the estimated capacity and prepare a second tested backup disk for long sessions.

5.4Immediate and scheduled recording

After health checks pass, start immediately or schedule a start or stop. Scheduled recording shows a countdown and hourglass. Keep the Mac powered, the app running and both device and output disk connected.

6.1Watch these indicators first

• Recording state in the title bar, Dock and menu bar.
• Increasing elapsed time and reasonable free space on the output disk.
• New buffer, device, sample-rate or power alerts.
• In Studio Mode, stable levels on critical channels and monitor outputs matching physical speakers.

6.2Monitor mixing does not alter original recordings

Studio Mode allows monitor level, pan, Solo, Mute, polarity inversion and spatial positioning within enabled layouts. These affect monitoring only and are not written into the original audio. Safe Mode locks these operations while recording.

6.3Markers

Add a short marker for retakes, noise, disconnections, battery changes, scene changes or important sections. Use clear labels such as Presenter section 3 retake, Second half begins or Input 12 brief noise. Markers enter reports and supported file metadata with the session.

6.4Channel changes

Set the channel list before starting. The current interface does not offer adding tracks during recording as a standard operation. If a version or controller permits stopping individual tracks, add a marker and record the reason first. Do not rearrange inputs, change sample rate or move the output folder during important recording.

6.5Stop recording

Use Stop Recording in the console and wait for file finalization and report loading. Version 4.4.0 does not use Cmd/Ctrl+Q as a recording-stop shortcut. Do not quit the app instead of stopping. Keep the audio device and output disk connected during finalization.

7.1Common faults

7.2When to continue and when to stop

A single power warning, brief monitor disconnect or recoverable device event need not require an immediate stop. A full disk, persistent buffer overflow, write failure or unrecoverable engine fault is a serious risk. First confirm whether the file is still being written, then whether the fault persists, and finally decide to continue, switch to backup or stop.

7.3Do not rush to rerecord after a fault

1. Wait for finalization and check whether the completion page confirms safe writing or gives a warning.
2. Record the error time, device name and actions taken on site.
3. Copy recordings, reports and segments before overwriting or renaming originals.
4. Listen before and after the fault before deciding on a retake.

8.1The completion page leads with the result

After stopping, the page shows whether the session was written, its path, size, channel count and duration. On wide screens, Track Vault is on the left and health overview on the right. Expand metadata and timeline when needed. Multisegment sessions clearly show segment count and relevant notices.

8.2Track Vault

Track Vault creates a record for each track actually written. Browse track names, recorded channels and device inputs with the left/right controls, arrow keys, wheel or touch gestures. It verifies which tracks were recorded; it is not an audio editor.

8.3Clipping detection is manual

Version 4.4.0 does not automatically scan all audio after each stop. Start clipping detection on the completion page when needed. Offline analysis may take time for long or multichannel files and can be cancelled. Results are added to the report's health checks.

8.4Review before delivery

• Copy the save path and confirm that the file exists and its size is plausible.
• Check disk, buffer, sample-rate, device and power results in the health overview.
• Expand the timeline and listen around warnings, device disconnections, segment boundaries and manual markers.
• Run clipping detection if needed, then save or export the report.
• Close the session only after copying and listening checks are complete.

9.1Multichannel splitting

The splitting tool exports a multichannel WAV/CAF source into mono files for post-production. Choose the source and a new output folder. Read the source and write new files; do not manually overwrite original masters. After splitting, verify file count, channel order, names, lengths and sample rate.

9.2Disk formatting

Formatting erases every file on the target disk. Verify its name, capacity, connection and whether it contains other project material. Never format during recording, while the disk is writing or when its identity is uncertain. Eject as instructed afterward, reconnect and test writing.

9.3Pro Tools and REAPER

The completion page provides Convert to Pro Tools and Convert to REAPER to launch the bundled conversion workflow. Run only after recording has stopped, the report is available and file paths are valid. Open the resulting DAW project and verify track count, order, names, start positions and media links.

9.4ADM-BWF

ADM-BWF export is an offline operation after recording for immersive workflows such as Dolby Atmos. Current requirements:

• The source session must be 48 kHz.
• The bed is fixed at 7.1.2, with ten bed channels.
• Up to 118 objects and 128 total output channels.
• Direct export of a multisegment recording into one ADM-BWF is not supported. Use one multichannel segment.
• Verify channel and object mapping in Logic Pro, Dolby Atmos Renderer or the target system after export.

9.5Suggested archive structure

10.1Installation and verification

Record Safer Pro MCP requires Node.js 18 or later. The usual launch command is:

npx -y record_safer_pro_mcp@latest

Appearing idle when run directly is normally expected: a stdio MCP server waits for the AI client. Verify using these two commands:

npx -y record_safer_pro_mcp@latest --version
npx -y record_safer_pro_mcp@latest --doctor

10.2What MCP can do

• Open Record Safer Pro automatically and query current state, health and audio devices.
• Read a channel list or user requirements, preview and confirm recording settings, and prepare a session.
• Start, stop or schedule recording, cancel schedules, and add, view or rename markers.
• Read tracks and monitor mixes; adjust names, colors, volume, pan, Solo, Mute and polarity.
• Start Pro Tools or REAPER conversion when completion-page requirements are met.
• Search the built-in user manual and monitor-mixing guide.

10.3Preparing a session does not start recording

preview_record_mcp_setup previews, confirm_record_mcp_setup confirms, and start_record_mcp only prepares the session and opens the recording page. It does not start writing. Recording requires an explicit user instruction to start before executing the action. Do not continue high-impact operations from ambiguous instructions.

10.4Current boundaries

• MCP cannot currently select or switch immersive or multichannel monitor modes. Configure layout and output mapping in the app's System Settings first.
• MCP does not handle account activation, software updates, disk formatting, storage cleanup or macOS permission changes.
• When importing a channel list, AI should match each documented input number and name against actual device channel labels, rather than inferring from channel count.
• Every operation changing recording, channel or mix state should follow the current app state and clear user intent.

11.1Include these details when contacting support

• Record Safer Pro version, macOS version and Mac model.
• Audio interface model, connection type, driver version, sample rate and channel count.
• Output disk model, format, free space and error time.
• Screenshots, reports, segment information and logs safe to share.
• Do not send passwords, activation keys, license files or clients' original recordings unless official support has specified a secure transfer method.

12.1Project preparation

• Fix the versions of Record Safer Pro, macOS, interface drivers and firmware.
• Confirm account licensing, expiry and target-device binding.
• Make a test recording longer than one minute with the actual devices, channel count and output disk.
• Prepare the channel list, input labels, monitor-output diagram and spare cables.
• Estimate capacity and prepare at least twice the required space plus a tested backup disk.

12.2Thirty minutes before the event

• Connect stable power and close unnecessary apps, cloud-sync clients and system updates.
• Confirm audio devices, clock, sample rate, channel count and output disk.
• Verify bit depth, WAV/CAF, Safe/Studio Mode and monitor-output mapping.
• Enter the console and allow the ten-second pre-record buffer to fill.
• Make a test recording, listen at the start, middle and end, and inspect its report.

12.3Before the actual take

• Check each input, name and color against the channel list.
• Resolve all blocking issues and investigate important warnings before proceeding.
• Confirm system-level REC indicators, elapsed time and free disk space.
• Add an Official start marker and watch the first thirty seconds.

12.4Afterward

• Add an Official end marker, press Stop and wait for finalization.
• Verify path, size, channel count, duration, Track Vault and health overview.
• Run clipping detection as needed and listen around all alerts and segment boundaries.
• Copy original files, reports and location notes before splitting, DAW conversion or ADM-BWF export.
• Clear the location disk only after confirming at least two independent readable copies.