🚀🎬 Video Streaming (Local DASH Pipeline)

A local video processing and playback app built with Next.js.
It accepts uploaded videos, transcodes them into DASH format with FFmpeg in a background worker, and plays ready streams in the browser via Media Source Extensions (MSE).

Purpose

This project provides an end-to-end local streaming workflow:

• upload a source video from the UI
• process it asynchronously into DASH segments + manifest
• track processing status (pending, processing, ready, failed)
• play the final stream from local filesystem-backed endpoints

It is designed for local development and feature iteration (no cloud storage or database yet).

Tech Stack

• Framework: Next.js 14 (App Router)
• Language: TypeScript + React 18
• Data Fetching: TanStack Query
• UI: Radix UI primitives + shadcn-style component patterns
• Processing: FFmpeg (DASH generation)
• Background Scheduling: cron npm package (worker loop)
• Storage: Local filesystem under videos/

Work Schema (Processing Flow)

1. User uploads a video through /api/videos/upload.
2. A video record is created with pending status.
3. Background worker scans for jobs every ~15 seconds.
4. FFmpeg converts input into DASH output (manifest.mpd + segments).
5. Status is updated to:

• ready on success
• failed on processing error

6. Client polls list/status APIs and plays ready media through MSE.

Status Lifecycle

pending -> processing -> ready | failed

Local Storage Schema

All runtime assets are stored on disk:

• videos/uploads/<videoId>/<original-file>
• videos/dash/<videoId>/manifest.mpd (+ segment files)
• videos/records/<videoId>.json
• videos/locks/<videoId>.lock

Prerequisites

• Node.js 18+ (recommended modern LTS)
• npm
• FFmpeg available in your system PATH

Check FFmpeg:

ffmpeg -version

Required Commands

Install dependencies:

npm install

Run development server:

npm run dev

Create production build:

npm run build

Start production server (after build):

npm run start

If Next.js build cache gets corrupted with route resolution issues:

rm -rf .next && npm run build

Notes

• Worker initialization is triggered by server init imports in API routes.
• The app currently has no authentication/authorization layer.
• This is a filesystem-first implementation (no DB/S3 integration yet).