Connect downstream media apps

Confirm a small target succeeded in 运行记录 (Run records), then find the output root under 设置 → 生成文件位置. STRM is a relay address, not a video. Generation alone does not establish downstream scanning or playback.

Choose the correct directory

Target	Generated structure
Short Drama	drama/{title}/tvshow.nfo and S01E01.strm…
VR Player	3dvr/{title}/{video}.strm
Audiobook	audiobook/{title}/001_{chapter}.strm…

Drama/audiobook numbering follows ascending filenames. Test a small folder to confirm ordering. Give downstream read-only access to its output type, not application state containing accounts/Cookies.

Docker /media is the Leelaa STRM container path, not automatically the path in VR/Drama/Audiobook containers. The maintainer must mount the same host output read-only downstream and use that container's path. fnOS likewise needs read permission for the downstream application.

Prepare identity before scanning

Ordinary relay URLs require a valid Leelaa STRM application session. fnOS system headers, another application's sign-in or an earlier browser management sign-in do not provide that session to a downstream server. Media probing may request the URL during scanning, before pressing play.

Independent services/players generally do not carry that session. Have the administrator configure the private-network channel under playback authorization, then select 确认并更新 STRM (Confirm and update STRM) for the target. Scan downstream after the dedicated addresses are written. Do not supply administrator passwords/Cookies to a player or disable authentication to remove a 401.

The software license must remain valid too; playback credentials do not bypass its gate. Each application has separate accounts and software licensing.

VR Player example

1. Complete a VR 播放器 target in Leelaa STRM, then confirm any required dedicated playback grant.
2. Ensure downstream can read output root/3dvr, and both the VR backend and real playback device can reach the dedicated IP/port.
3. As the VR application's own administrator, open 系统设置 → 储存库 → 添加来源 → STRM 目录. Enter the path VR can actually read, click 添加 (Add), then 运行任务 (Run task).
4. Check VR's indexed count and file-specific probe errors. Saving a source is not indexing it.
5. Open a video from VR's library and complete the checks below.

These are the current interfaces of the two applications. If an older package differs, consult each version's instructions; a documented procedure does not establish that an old package includes the capability.

Verify the playback chain

1. Check the target generated the expected STRM count, with correct downstream works, episodes/chapters/videos and ordering.
2. Start playback on the device you actually use. Check picture/sound, seeking and reopening.
3. Open again later. To check renewed direct links, retry after the one-hour cache period. One successful video does not establish every codec/device is compatible.

Playback requests this service first, receives a redirect to a 115 direct link, then reads media from the CDN. The NAS does not relay the media body and zero latency is not promised. Diagnose pre-redirect failures in Leelaa STRM; persistent stalls after the CDN redirect also require checking the player-to-upstream network.

If it does not work

• No downstream work: check the read-only mount, scan path and downstream scan errors.
• 401: ensure the files contain the dedicated authorized URL. Downstream may cache old ordinary URLs and need a rescan.
• Resource unavailable: check channel status, target grant and software license; handle revocation/address changes under playback authorization.
• Old cached address: after service or dedicated IP/port changes, resync/rotate the appropriate grant, then rescan downstream.

Older versions put VR files directly under 3dvr/; current output has a directory per target. Flat legacy files are not automatically cleaned. Back up and check downstream references, then have the maintainer handle genuinely unused files rather than deleting by a title prefix.