Post-Recording

Post-Recording is a lightweight Docker utility that watches a directory for .ts files created by Live TV recordings, converts them to a friendlier container…

  • Media Applications
  • Media Servers
  • Tools & Utilities
Post-Recording is a lightweight Docker utility that watches a directory for .ts files created by Live TV recordings, converts them to a friendlier container format, extracts subtitle (.srt) files, and adds or removes video chapters via comchap/comcut. Designed for homelab users running Emby or similar media servers who want automated post-processing of recorded TV content.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

30/100 Low

Maintained
0last commit 1774 days ago
Popular
2824 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
304 GB minimum RAM
Security check
85no serious findings, CI

Availability: platform listings confirmed today, links checked 43 days ago

GitHub stars
24
Open issues
14
Last commit
2022-01-12
Activity
stale

Checked 18 days ago - source: GitHub (chacawaca/docker-post-recording)

Resources & Compatibility

Minimum requirements: 4 GB RAM. ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Run the NVRAM setup script once After placing the LogoutHook folder, open a terminal and run the install command so the NVRAM (the saved settings area for your system) emulation scripts are registered. Skipping this can leave NVRAM-based settings not working. source
  • Set NVIDIA NVCAP if using NVIDIA If your graphics card is NVIDIA, use the calculated NVCAP (a code that tells macOS which GPU features to enable) in your setup. A wrong or missing NVCAP can break display features and GPU compatibility. source
  • Add AMD power management for Ryzen If you have an AMD Ryzen CPU, install the AMDRyzenCPUPowerManagement.kext (a small add-on that controls CPU power settings). Without it, macOS may not manage power correctly on Ryzen chips. source
  • NVIDIA GPU acceleration (Unraid) Install the Unraid NVIDIA plugin, add --runtime=nvidia to the container's Extra Parameters (advanced view), and set NVIDIA_VISIBLE_DEVICES to your GPU UUID for hardware-accelerated transcoding. source

Fetched 45 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I keep the original .ts recordings while testing?

Set DELETE_TS=1 to prevent deletion of the original .ts file after conversion. Values 0 and 2 delete the file or move it to the /backup directory.

How do I extract subtitles to .srt files?

Set SUBTITLES=0 to extract subtitles to .srt files. Set SUBTITLES=1 to disable extraction.

Can the container add or remove chapters?

Set POST_PROCESS=comchap to add chapters or POST_PROCESS=comcut to remove them. The default is comchap.

Do I need to configure a custom script?

Yes, /scripts/custom.sh needs to be configured by you. Example scripts are included to help, and /hooks and /comskip/comskip.ini can also be configured.

How do I enable hardware acceleration on Unraid?

For Intel GPUs, add modprobe i915 to your go file, reboot, then add --device=/dev/dri to extra parameters. For Nvidia GPUs, use the Unraid Nvidia Plugin, add --runtime=nvidia, and set NVIDIA_VISIBLE_DEVICES to your GPU UUID.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads