What is nodecast-tv?

February 16, 2026 Β· View on GitHub

nodecast-tv

What is nodecast-tv?

nodecast-tv is a modern, web-based IPTV player featuring Live TV, EPG, Movies (VOD), and Series support. Built with performance and user experience in mind.

Features

  • πŸ“Ί Live TV: Fast channel zapping, category grouping, and search.
  • πŸ“… TV Guide (EPG): Interactive grid guide with 24h timeline, search, and dynamic resizing.
  • 🎬 VOD Support: Dedicated sections for Movies and TV Series with rich metadata, posters, and seasonal episode lists.
  • ❀️ Favorites System: Unified favorites for channels, movies, and series with instant synchronization.
  • πŸ” Authentication: User login system with admin and viewer roles (details).
  • πŸ†” OIDC SSO: Support for Single Sign-On via OIDC providers (Authentik, Keycloak, etc.).
  • ⚑ High Performance: Optimized for large playlists (7000+ channels) using virtual scrolling and batch rendering.
  • βš™οΈ Management:
    • Support for Xtream Codes and M3U playlists.
    • Manage hidden content categories.
    • Playback preferences (volume memory, auto-play).
  • πŸŽ›οΈ Hardware Transcoding: GPU-accelerated transcoding with NVIDIA NVENC, AMD AMF, Intel QuickSync, and VAAPI support.
  • πŸ”Š Smart Audio: Configurable 5.1β†’Stereo downmix presets (ITU, Night Mode, Cinematic) with automatic passthrough for compatible sources.
  • πŸ“¦ Stream Processing: Auto-detection of stream codecs with smart remux/transcode decisions.
  • 🐳 Docker Ready: Easy deployment containerization.

Screenshots

Dashboard Live TV TV Guide Movies Series Settings

Getting Started

Prerequisites

  • Node.js (v14 or higher)
  • npm

Installation

  1. Clone the repository:

    git clone https://github.com/technomancer702/nodecast-tv.git
    cd nodecast-tv
    
  2. Install dependencies:

    npm install
    
  3. Start the development server:

    npm run dev
    
  4. Open your browser at http://localhost:3000.

Docker Deployment

You can run nodecast-tv easily using Docker.

  1. Create a docker-compose.yml file (or copy the one from this repo):

    services:
      nodecast-tv:
        build: https://github.com/technomancer702/nodecast-tv.git#main
        container_name: nodecast-tv
        ports:
          - "3000:3000" # Host:Container
        volumes:
          - ./data:/app/data
        restart: unless-stopped
        environment:
          - NODE_ENV=production
          - PORT=3000 # Optional: Internal container port
    
  2. Run the container:

    docker-compose up -d
    

The application will be available at http://localhost:3000.

Hardware Acceleration Setup

To enable hardware transcoding (NVENC, QSV, VAAPI), you must expose your host's GPU to the container.

1. Intel (QSV) & AMD (VAAPI) Update your docker-compose.yml to map the DRI devices and add necessary groups (often required for permission):

    devices:
      - /dev/dri:/dev/dri # Required for VAAPI/QuickSync/AMF (Linux)
    # group_add:       # Optional: Needed mainly if you run as non-root
    #   - "video"      # Run on host: getent group video
    #   - "render"     # Run on host: getent group render

2. NVIDIA (NVENC) Ensure you have the NVIDIA Container Toolkit installed on your host, then update your docker-compose.yml:

    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia
              count: 1
              capabilities: [gpu, utility, video, compute]

Verify: After restarting the container, go to Settings -> Transcoding. The Hardware Detection status should list your GPU (e.g., "NVIDIA GPU Detected" or "VAAPI Available").

SSO / OIDC Setup

Enable Single Sign-On (SSO) with your preferred OIDC provider (Authentik, Keycloak, etc.) by configuring these variables in your .env file or Docker environment:

OIDC_ISSUER_URL=https://your-idp.com/application/o/nodecast/
OIDC_CLIENT_ID=your_client_id
OIDC_CLIENT_SECRET=your_client_secret
OIDC_CALLBACK_URL=http://localhost:3000/api/auth/oidc/callback # Adjust for your domain

Note: New users signing in via SSO are automatically assigned the Viewer role. You must manually promote them to Admin if desired.

Usage

  1. Go to Settings -> Content Sources.
  2. Add your IPTV provider details (Xtream Codes or M3U URL).
  3. Click "Refresh Sources".
  4. Navigate to Live TV, Movies, or Series to browse your content.

Browser Codec Support & Transcoding

nodecast-tv is a web-based application. By default, video decoding is handled by your browser. However, the built-in smart transcoding system automatically converts incompatible media (e.g., HEVC video, Dolby audio) into browser-friendly formats using FFmpeg.

Codec Compatibility Table:

CodecChromeFirefoxSafariEdge
H.264 (AVC)βœ…βœ…βœ…βœ…
H.265 (HEVC)Auto-TranscodeAuto-Transcodeβœ…βš οΈ
AV1βœ…βœ…Auto-Transcodeβœ…
AAC Audioβœ…βœ…βœ…βœ…
AC3/EAC3 (Dolby)Auto-TranscodeAuto-Transcodeβœ…Auto-Transcode

⚠️ Note: Edge requires the HEVC Video Extensions from the Microsoft Store to play H.265 (HEVC) natively. ℹ️ Note: Safari plays AV1 natively on supported hardware (iPhone 15 Pro, M3 Macs). On older devices, Auto-Transcode handles it.

Supported Stream Types

nodecast-tv is optimized for HLS (HTTP Live Streaming).

  • βœ… HLS (.m3u8): Fully supported and recommended. Best for adaptive bitrate and network resilience.
  • βœ… MPEG-TS (.ts): Supported via Force Remux in settings.
  • ⚠️ High Latency/P2P: For sources like Acestream, prefer HLS output (.m3u8) over raw TS streams to avoid timeouts during buffering.
  • ❌ RTMP/RTSP: Not supported natively by browsers.

Transcoding Settings

All transcoding and stream processing settings are found in Settings β†’ Transcoding.

Hardware Encoder

SettingOptionsDescription
Hardware EncoderAuto, NVENC, AMF, QSV, VAAPI, SoftwareGPU-accelerated encoding. Auto detects best available.
Max Resolution4K, 1080p, 720p, 480pLimit output resolution (lower = faster).
Quality PresetHigh, Medium, LowEncoding quality/speed tradeoff.
Audio Mix PresetAuto, ITU, Night Mode, Cinematic, Passthrough5.1β†’Stereo downmix mode (see below).

Audio Mix Presets

PresetDescription
Auto (Smart)Copies stereo AAC as-is, uses ITU downmix for 5.1+
ITU-R BS.775Industry-standard balanced downmix
Night ModeBoosted dialogue, reduced bass for quiet viewing
CinematicWide soundstage, immersive surround feel
PassthroughNo processing (may cause errors on 5.1/Dolby sources)

Stream Processing

SettingWhat It DoesWhen to Enable
Auto Transcode (Smart)Probes streams and only transcodes/remuxes when neededRecommended for most users (default ON)
Force Audio TranscodeTranscodes audio to AAC (video passes through)When you have video but no audio (Dolby/AC3/EAC3)
Force Video TranscodeFull transcode of both audio and videoFor HEVC/VP9 sources on unsupported browsers
Force RemuxRemuxes MPEG-TS to MP4 (no re-encoding)For raw .ts streams from middleware
Stream Output FormatHLS or TS for Xtream API requestsTry TS if HLS causes buffering

Network

SettingWhat It DoesWhen to Enable
Force Backend ProxyRoutes streams through the server for CORS headersWhen streams fail with CORS errors, or using middleware

Troubleshooting

Video Won't Play (Black Screen or Loading Forever)

SymptomLikely CauseSolution
Black screen, Access-Control-Allow-Origin errorCORS blockedEnable "Force Backend Proxy" in Settings β†’ Transcoding
Black screen with MEDIA_ERR_DECODEUnsupported codec (HEVC/VP9)Ensure "Auto Transcode" is enabled
Loading forever (no error)Browser decoder stuckEnable "Force Video Transcode" (overrides Auto detection)

No Audio (Video Plays Fine)

SymptomLikely CauseSolution
No audio at allDolby/AC3/EAC3 audioEnable "Force Audio Transcode" (overrides Auto detection)
Audio out of syncStream encoding issueTry changing stream format to TS in Settings

Buffering Issues

SymptomLikely CauseSolution
Constant bufferingSlow network or weak GPU1. Lower Max Resolution (e.g. to 720p)
2. Try TS format instead of HLS

HTTPS / Reverse Proxy Issues

If you're running nodecast-tv behind a reverse proxy (Nginx, Caddy, Traefik) with HTTPS:

SymptomLikely CauseSolution
Streams fail with fragLoadErrorMixed content (HTTPS page loading HTTP streams)Enable "Force Backend Proxy" in Settings β†’ Transcoding
Streams work on HTTP but not HTTPSReverse proxy not passing headers correctlyEnsure X-Forwarded-Proto header is set (see examples below)

Caddy example:

tv.domain.com {
    reverse_proxy nodecast:3000 {
        flush_interval -1
        header_up X-Forwarded-Proto {scheme}
    }
}

Nginx example:

location / {
    proxy_pass http://nodecast:3000;
    proxy_http_version 1.1;           # Required for chunked transfers and keep-alive
    proxy_buffering off;              # Don't buffer responses (required for streaming)
    proxy_request_buffering off;      # Don't buffer requests
    proxy_read_timeout 300s;          # VOD: 5 min timeout for large files
    proxy_connect_timeout 60s;        # VOD: Connection timeout
    client_max_body_size 0;           # No upload size limit
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;  # Required for HTTPS detection
    proxy_set_header Connection "";   # VOD: Enable keep-alive for Range requests
}

IPTV Middleware (m3u-editor, dispatcharr, Threadfin, xTeVe)

If you manage your streams with middleware tools, you may encounter CORS issues or raw MPEG-TS streams that browsers can't play directly.

Recommended Setup:

  1. Force Backend Proxy: Enable this in Settings β†’ Transcoding β†’ Network. This routes middleware streams through NodeCast TV, bypassing CORS restrictions.
  2. Auto Transcode: Keep this enabled (default). It will automatically detect if the middleware stream (e.g., MPEG-TS) needs to be remuxed or transcoded for the browser.

There is rarely a need to configure specific "Force Remux" settings manually anymore; the system detects stream types automatically.

TVHeadend

If you're using TVHeadend as your source, you may need to configure a few settings for streams to play correctly in nodecast-tv:

Option 1: Enable Force Backend Proxy (Easiest)

  • In nodecast-tv, go to Settings β†’ Transcoding β†’ Network
  • Enable "Force Backend Proxy"
  • This routes streams through the server, bypassing browser CORS restrictions

Option 2: Configure TVHeadend CORS

  • In TVHeadend, go to Configuration β†’ General β†’ Base β†’ HTTP Server Settings
  • Add your nodecast-tv URL to "CORS origin" (e.g., http://192.168.1.100:3000)
  • Note: You must include the protocol (http:// or https://)

Additional Tips:

  • Enable "digest+plain" authentication in TVHeadend if using username/password in the M3U URL
  • Try different stream profiles (?profile=pass or ?profile=matroska) if playback issues persist

Acestream / P2P Streaming

If you are using acestream-docker-home or similar tools, it is recommended to use the HLS output format to reduce server load, though NodeCast TV can remux raw streams if needed.

  • Recommended: http://proxy:6878/ace/manifest.m3u8?id=... (HLS Playlist - Direct Play)
  • Supported: http://proxy:6878/ace/getstream?id=... (MPEG-TS - Requires Server Remuxing)

Technology Stack

  • Backend: Node.js, Express
  • Frontend: Vanilla JavaScript (ES6+), CSS3
  • Database: SQLite (via better-sqlite3) for high-performance data storage
  • Streaming: HLS.js for stream playback
  • Transcoding: FFmpeg (integrated for hardware/software transcoding)

Project Structure

nodecast-tv/
β”œβ”€β”€ public/              # Frontend assets
β”‚   β”œβ”€β”€ css/             # Stylesheets
β”‚   β”œβ”€β”€ js/              # Client-side logic
β”‚   β”‚   β”œβ”€β”€ components/  # UI Components (ChannelList, EpgGuide, etc.)
β”‚   β”‚   β”œβ”€β”€ pages/       # Page Controllers (Movies, Series, etc.)
β”‚   β”‚   └── api.js       # API Client
β”‚   └── index.html       # Main entry point
β”œβ”€β”€ server/              # Backend server
β”‚   β”œβ”€β”€ routes/          # API Endpoints (proxy, transcode)
β”‚   β”œβ”€β”€ services/        # Playlist parsers, SyncService, etc.
β”‚   β”œβ”€β”€ db/              # Database Logic
β”‚   β”‚   β”œβ”€β”€ index.js     # Legacy DB Wrapper
β”‚   β”‚   └── sqlite.js    # SQLite Connection & Schema
β”‚   └── index.js         # Server Entry Point
└── data/                # Persistent storage (content.db, playlists)

License

This project is licensed under the GNU General Public License v3.0 (GPL-3.0).

You are free to:

  • Run the program for any purpose
  • Study how the program works and change it
  • Redistribute copies
  • Distribute copies of your modified versions

Under the condition that:

  • You typically must distinguish your modifications from the original work
  • You provide the source code to recipients
  • You license any derivative works under the same GPL-3.0 license

See the LICENSE file for details.