PureRecorder Documentation

PureRecorder is a high-efficiency background engine designed for seamless, 24/7 Chaturbate stream archiving. It eliminates the need for manual monitoring, providing a "set-and-forget" environment that captures your favorite content the moment it goes live. Built for stability and precision, the software handles the entire lifecycle of a broadcast—from detection to final storage—without requiring user intervention.

Quick Start

1. Run PureRecorder_Installer.exe
2. Launch PureRecorder.exe
3. Open http://localhost:9090/ in your browser
4. Paste your Chaturbate cookies in Settings
5. Add performers to begin monitoring
        

Installation

PureRecorder is distributed as a Windows installer. Run the installer to install the application.

PureRecorder_Installer.exe
        

After installation the main executable is:

PureRecorder.exe
        

Web Interface

PureRecorder uses a local web interface instead of a traditional desktop UI.

Once the program is running, open your browser and navigate to:

http://localhost:9090/
        

From the interface you can add performers, view active recordings, configure settings and monitor system activity.

Settings

The Settings page allows configuration of recording behaviour, storage directories and authentication cookies.

Authentication (Cookies)

PureRecorder requires authenticated browser cookies to access stream endpoints. Without valid cookies the recording engine cannot retrieve stream data.

1. Install the Cookie Extension

Install the extension Get cookies.txt LOCALLY by kairi.

2. Login to Chaturbate

Open Chaturbate in your browser and log in normally.

3. Copy Cookies

1. Click the extension icon
2. Press "Copy"
3. Cookies will be copied to your clipboard
        

4. Paste into PureRecorder

1. Open http://localhost:9090/
2. Go to Settings
3. Paste cookies into the Cookies field
4. Save the configuration
        

Logs

PureRecorder writes logs to the logs directory inside the application folder. The main system log is logs/system.log. Each performer can also have a dedicated log file.

Logs use a structured format:

[date time] [LEVEL] [CODE] message | key=value key=value
[time] [LEVEL] [CODE] message
        

Log Prefix Reference

The following prefixes are used by the application exactly as written in the source code. They indicate the subsystem that generated each entry.

INFO

• INIT-001 — System boot
• INIT-100 — System ready
• WORK-001 — Worker started
• WORK-010 — Stopping paused stream
• REC-010 — Live stream detected
• REC-100 — --- NEW RECORDING STARTED ---
• REC-101 — File: <output filename>
• REC-200 — Recording finished.
• USER-001 — User action
• CFG-001 — Settings updated
• SYS-OFF — Shutdown requested
• SYS-100 — Server started

WARN

• PROC-021 — Force killing process
• LIC-002 — PRO license expired. Switching to FREE mode.
• ENC-001 — FFmpeg missing, cannot start recording
• NET-001 — Network check failed

ERROR

• DB-001 — Database connection failed
• DB-002 — Failed to create performers table
• DB-003 — Failed to create config table
• SYS-001 — Internal Template parse failed
• REC-PIPESTALL — yt-dlp stdout stalled
• PROC-002 — Failed to start ffmpeg process
• PROC-002 — Failed to start yt-dlp process
• PROC-000 — Command not initialized
• PROC-011 — Process execution error
• REC-STALL — Recording stalled detected
• USER-002 — Failed to add performer
• TPL-001 — Template execution failed
• CFG-002 — Failed to write cookie file
• PANIC-001 — Recovered panic
• PANIC-002 — Fatal panic

DEBUG

Debug logs are only written when Debug Mode is enabled in Settings.

• PROC-020 — Cancel signal sent
• PROC-001 — Starting piped process
• PROC-003 — Process started
• PROC-010 — Process exited
• ENG-STDERR — stderr output captured from yt-dlp
• ENG-VAL-START — Validating stream
• ENG-VAL-FAIL — Invalid engine path
• ENG-VAL-FAIL — Validation execution failed
• ENG-VAL-PARSE — JSON parse failed
• ENG-VAL-RESULT — Validation result

STATS

Telemetry entries are written with the [STATS] tag and are used for live recording progress.

• Uptime
• File size
• Bitrate

Per-performer logs are stored at:

logs/<performer_name>.log
        

These logs are rotated automatically when they reach the size limit, and the previous file is moved to .old.