DOCSEARCHbyAlgolia
Submit Docs

SmartStrm Documentation

website·Indexed 29 days ago

https://smartstrm.github.io

A high-efficiency STRM file generation and management system for private media servers. It enables NAS and home cinema users to integrate cloud drives (such as Quark, Tianyi, 115, 123, and others) with media libraries like Emby, Jellyfin, and Plex. Key features include 302 proxying to reduce NAS server load, Webhook triggers for instant library updates, TMDB-based movie and TV show recognition, and support for various cloud storage drivers.

Tokens
21.8K
Snippets
33
Records
177
Agent score
74%

What's inside SmartStrm

  1. Overview of SmartStrm

    SmartStrm is a media library STRM file generation tool that enables cloud drive resources to be integrated into media servers (such as Emby, Jellyfin, and NAS-specific media centers like Green Union or ZSpace). It allows for 'instant play' by generating .strm files that point to cloud resources, bypassing local bandwidth bottlenecks via 302 direct link playback (Pro version). Key features include automatic .strm/symlink generation, remote deletion synchronization, Emby API library refreshing, and automatic organization of subtitles, posters, and NFO metadata.

  2. Overview of SmartStrm 302 Direct Link Playback

    SmartStrm allows Emby media libraries to play files from Quark Drive via 302 redirection. Instead of streaming data through the local server, SmartStrm scans the cloud drive, generates .strm files, and redirects the playback request directly to the Quark Drive resource link. This removes local upload bandwidth bottlenecks.

  3. Overview of SmartStrm and its automation workflow

    SmartStrm is a tool designed to generate STRM files for streaming media from cloud drives. It is built to integrate with other tools like Quark Auto Save (QAS) and CloudSaver (CS) to create a fully automated workflow: Search → Save to Cloud → Generate STRM → Emby Library Import → Playback. The tool provides basic STRM generation for free and includes plugin integration and Webhook functionality for developers to implement custom generation and API calls.

  4. Overview of SmartStrm for Emby Cloud Playback

    SmartStrm allows Emby media libraries to play files from Quark Drive and Alist/OpenList using 302 redirects. Instead of the server streaming the file, SmartStrm generates .strm files that redirect the player to the cloud drive's direct download link. This minimizes server upload bandwidth and CPU load, as the data flows directly from the cloud provider to the playback device.

  5. Overview of Quark-auto-save and SmartStrm automation

    This setup allows users to automate the process of tracking TV shows and variety shows from Quark cloud drive. The workflow consists of: automatically searching for resources, batch processing/renaming files, scheduled saving to the cloud drive, generating .strm files (shortcuts to cloud videos), and finally scraping and importing them into a media library (e.g., Emby, Jellyfin, Plex). Using .strm files saves local disk space and reduces home upload bandwidth by utilizing 302 redirects to stream directly from the cloud.

  6. Overview of SmartStrm for Cloud Media Libraries

    SmartStrm is a tool that generates STRM files (network shortcuts) for media libraries. Instead of storing large media files locally, it creates small pointer files that tell media players (like Ugreen Movie Center, Emby, Jellyfin, or Kodi) to stream the content directly from a cloud provider. This allows for extremely fast library scanning and avoids 'risk control' (account bans/restrictions) from cloud providers by reducing unnecessary file access during scanning.

  7. Overview of SmartStrm for Cloud Media Integration

    SmartStrm is a system that generates and manages .strm files, allowing users to integrate cloud drives (such as Quark, Tianyi, Mobile, 115, 123, Xunlei, and Guangya) into private media servers like Emby, Jellyfin, Plex, and FN-OS (飞牛影视).

    Key benefits include:

    • Zero Disk Pressure: Maps TBs of cloud resources to small .strm files, removing the need for expensive local storage expansion.
    • Fast Library Integration: Supports incremental generation so new cloud-saved movies/series are quickly added to the media library.
    • Direct Playback (302 Redirect): Uses 302 redirection technology so the playback client requests the video stream directly from the cloud drive, bypassing the NAS to avoid bandwidth bottlenecks.
    • Automation: Can be paired with tools like Quark-Auto-Save and CloudSaver to automate the flow from "Save to Cloud" $\rightarrow$ "Import to Library" $\rightarrow$ "Playback".

  8. Overview of STRM files and SmartStrm for FNOS

    STRM files are plain text files containing direct URLs to media files (e.g., from a cloud drive). They act as placeholders that the FNOS Movie player (v0.9.1+) can use to stream remote content as if it were a local file.

    SmartStrm is a tool that automates the conversion of cloud drive directory structures into local .strm files. Compared to mounting a cloud drive via FUSE/WebDAV, SmartStrm offers:

    • Higher Playback Efficiency: Direct streaming of remote links without intermediate caching/proxying.
    • Faster Scraping: The media player only scans small text files rather than querying the cloud API for large file metadata, avoiding API rate limits.
    • Trade-off: Because the player only sees the .strm file and not the actual video stream during the scraping phase, it cannot generate internal video thumbnails (frame extraction).

  9. Overview of CloudSaver + SmartSTRM + Jellyfin zero-local-storage architecture

    This architecture allows users to play high-quality media in Jellyfin without storing actual video files locally. It consists of three components:

    1. CloudSaver: Handles resource searching and one-click transfers to various cloud drives, with the ability to trigger actions upon completion.
    2. SmartSTRM: Maps cloud drive resources to local .strm files, providing a local media structure for Jellyfin, Emby, or Plex.
    3. Jellyfin: Acts as the media server, playing the cloud resources referenced by the .strm files.

  10. Manage task scheduling and concurrency

    SmartStrm employs a task management system where each task is executed by a single thread. If a task is triggered multiple times, it is placed in a sequential queue to prevent exceptions caused by concurrent execution. Users can stop running tasks via the stop button provided in the log modal on the frontend.

  11. Configure 123 Cloud Drive and generate .strm files in SmartStrm

    To use 123 Cloud Drive, you must have a developer rights package to obtain the client_id and client_secret. To enable direct link access (302 proxy), a SmartStrm Pro license is required, which is entered in System Settings → About.

    Steps to generate files:

    1. Create storage in SmartStrm using the 123 Open Platform driver.
    2. Enter the client_id and client_secret.
    3. Enable the '302 Proxy' feature for direct link access.
    4. Go to 'Storage Browser' → 'Add Task' and enter the cloud drive path to scan and generate .strm files.

  12. STRM generation and remote file synchronization

    SmartStrm is a media library STRM file generation tool designed to work with Emby. Key capabilities include:

    • 302 direct link playback.
    • Synchronized deletion of remote files when media is removed from Emby.
    • Configurable file extensions, size thresholds, and copy extensions.
    • Handling of duplicate filenames by renaming copies to filename.(media_ext).copy_ext to prevent NFO mismatch.