Skip to content

ErsatzTV

ErsatzTV builds live TV channels from your media and streams them as IPTV (an M3U playlist and XMLTV guide) to apps like Plex, Jellyfin, Emby, or any IPTV player.

HMS-Docker uses the full ErsatzTV app (ghcr.io/ersatztv/legacy), which includes the web UI, library sources, and scheduling. The separate “ErsatzTV Next” project is not included.

Enable ersatztv in the Container Map and run the playbook. ErsatzTV is then available at ersatztv.<domain> through Traefik, or on port 8409 if ports are exposed.

ErsatzTV mounts the media share at /data, the same path Plex, Jellyfin, and Emby use. When you add a Plex, Jellyfin, or Emby source, ErsatzTV plays the files directly from disk using the paths the media server reports, so no Path Replacements are needed.

Use these server URLs when adding a source:

  • Plex: http://plex:32400
  • Jellyfin: http://jellyfin:8096
  • Emby: http://emby:8096

For a local library, use folders under /data/media_data/_library/ (replace media_data and _library if you changed hmsdocker_primary_mount_name or hmsdocker_library_folder_name).

ErsatzTV’s playlist and guide are at:

  • http://ersatztv:8409/iptv/channels.m3u
  • http://ersatztv:8409/iptv/xmltv.xml

Use these URLs when adding ErsatzTV as a Live TV / DVR source in a media server that runs in the same stack. For devices outside the stack, use https://ersatztv.<domain>/iptv/channels.m3u instead.

With hmsdocker_enable_intel_gpu: true, ErsatzTV gets /dev/dri and the group that owns /dev/dri/renderD128 (usually render), so it can use Intel QSV/VAAPI while running as the hmsdocker_container_uid user. If that device doesn’t exist, the playbook shows a warning and ErsatzTV runs without hardware transcoding. With hmsdocker_enable_nvidia_gpu: true, it uses the Nvidia runtime. Select the matching hardware acceleration in each ErsatzTV FFmpeg Profile.

Transcode files go to <hmsdocker_apps_path>/ersatztv/transcode, or to RAM if hmsdocker_transcode_tmpfs_enabled is set.