Description: We are looking for an experienced streaming engineer (not a hobbyist) with proven knowledge in: Flussonic Media Server FFmpeg advanced pipeline design HLS / RTMP streaming workflows yt-dlp (dynamic HLS URL extraction) Linux server automation (systemd, shell scripting) We have several cameras streaming to YouTube Live, with embed restrictions enabled. The goal is to restream these feeds into Flussonic, bypassing embed limitations, ensure automatic reconnection, and generate daily time-lapse videos with timestamp + branding overlays. Requirements 1. YouTube → Flussonic Restream (Automatic + Persistent) Extract temporary HLS stream URLs from YouTube Live using yt-dlp. Convert and restream to Flussonic (local RTMP or direct HLS). Must automatically: Detect stream interruptions (e.g., camera offline for 12+ hours) Reconnect and resume streaming without manual action Restart properly after server reboot (systemd service required) This system must run fully unattended. 2. Frame Capture for Time-Lapse Capture one frame every 10 seconds per stream (configurable). Save frames into separate directories per camera. 3. Automated Daily Time-Lapse Generation Generate a 24h time-lapse video (compressed playback). 30 FPS output, 1920 width (or native higher). H.264 encoding with optimal CRF / preset. Automatically delete raw frames after the video is created. 4. Overlay Requirements On both frames and final video: Local timestamp (DD-MM-YYYY HH:MM). Camera name / location label. PNG watermark/logo (transparent background). Text must remain readable in daylight / night (outline/stroke required). 5. Storage & Cleanup Automatic retention policy (keep time-lapse files for 7–30 days). Automatic removal of old time-lapse files to control disk usage. Deliverables Working, fully automated pipeline. systemd services for: stream restreaming frame capture daily time-lapse generation Shell scripts + documentation. One-time setup + handover explanation. To Apply (Must Answer) Do not apply unless you can answer the following: Provide examples of real streaming systems you have deployed. Describe how you handle dynamic HLS URL token refresh from YouTube. Confirm experience with Flussonic ingest + stable HLS output. Confirm you can provide a reconnection strategy for streams that go down for 6–12+ hours. Initial Scale Number of streams: ___ (we will provide exact number) System must be expandable to more streams later. Only apply if: You have production-level FFmpeg scripting experience. You understand stream resilience and failover, not just basic commands. You can deliver a robust, fault-tolerant setup — not a one-liner hack. This is not a beginner job. We need a senior-level streaming engineer. If that’s you — let’s discuss.