StashVideoHasherNode 0.3.12

Distributed Stash videohasher worker with VAAPI/NVENC/VideoToolbox support.

📼 StashVideohasherNode (VAAPI)

Fork notice (important): This repository is a fork of the original project by @Darklyter.
Original repository: https://github.com/Darklyter/StashVideohasherNodeVAAPI

Got a big Stash library? This script takes the heavy lifting off your Stash server by spreading video processing across as many machines as you want. Each node grabs a batch of unprocessed scenes, does the work, and reports back — with full GPU acceleration to keep things fast.

What it does

For each unprocessed scene it finds, the script can generate:

• Perceptual hash (phash) — visual fingerprint for your video, used for matching with Stashboxes and finding duplicate videos across your library
• Cover image — extracted from the video if you don't have one
• Sprite sheet — 9×9 thumbnail grid with WebVTT for timeline scrubbing
• Preview video — 15-second highlight reel (15 × 1s clips)
• Marker media — MP4 clips, WebP animations, and JPG screenshots for each scene marker

Everything runs in parallel, one scene won't block another, and a failed scene gets tagged for later review rather than crashing the batch.

Note: This script uses OSHASH fingerprinting. If your Stash instance is set to MD5, make sure to switch it to OSHASH in Settings before running.

---

Requirements

• Python 3.8+
• uv
• FFmpeg (with VAAPI, NVENC, and/or h264_videotoolbox / hevc_videotoolbox support if you want GPU acceleration)

Install uv (if needed):

curl -LsSf https://astral.sh/uv/install.sh | sh

git clone https://github.com/pdbadger7/StashVideohasherNodeVAAPI.git
cd StashVideohasherNodeVAAPI
uv sync

Then copy and customize config:

mkdir -p "${XDG_CONFIG_HOME:-$HOME/.config}/stash-videohasher"
cp config.example.yml "${XDG_CONFIG_HOME:-$HOME/.config}/stash-videohasher/config.yml"

Phash generation uses the internal pure-Python implementation by default. If you prefer the original videohashes binary, see PHash Backend below.

Optional global install (CLI command)

If you want a globally available command:

uv tool install .
stash-videohasher --health-check

stash-videohasher loads YAML config from:

• $XDG_CONFIG_HOME/stash-videohasher/config.yml (if XDG_CONFIG_HOME is set), otherwise
• ~/.config/stash-videohasher/config.yml

Use --config /path/to/config.yml to override.

Environment variables with the STASH_VH_ prefix are also supported (for example STASH_VH_STASH_HOST, STASH_VH_PER_PAGE, STASH_VH_DRY_RUN). Precedence is: defaults < config.yml < STASH_VH_ env vars < CLI flags*.

After the package is published to PyPI, you can install/run it without cloning this repo:

uv tool install StashVideoHasherNode
uvx --from StashVideoHasherNode stash-videohasher --health-check

---

Docker (x86 + ARM64)

This repo now includes a Dockerfile that builds on both linux/amd64 and linux/arm64. Docker image repository names must be lowercase, so the published image uses stashvideohashernode.

Build

docker buildx build --platform linux/amd64 -t stashvideohashernode:amd64 .
docker buildx build --platform linux/arm64 -t stashvideohashernode:arm64 .

Run with VAAPI (Intel/AMD on Linux x86 host)

docker run --rm -it \
  --device /dev/dri:/dev/dri \
  -v "${XDG_CONFIG_HOME:-$HOME/.config}/stash-videohasher/config.yml:/config/config.yml:ro" \
  -v /mnt/stash:/mnt/stash \
  stashvideohashernode:amd64 --config /config/config.yml --health-check

Apple M-Series note

linux/arm64 images run correctly on Apple Silicon, but Docker Desktop containers do not expose macOS VideoToolbox into Linux containers.
For Apple M-Series hardware acceleration (h264_videotoolbox / hevc_videotoolbox), run the script natively on macOS instead of inside Docker.

---

Setup

1. Point it at your Stash server

Open your config.yml and fill in your connection details:

stash_scheme: http
stash_host: 127.0.0.1
stash_port: 9999
stash_api_key: null

To get your API key: Stash → Settings → Security → copy or generate the key.

2. Set your output paths

Tell the script where your Stash-generated files live:

sprite_path: /mnt/stash/generated/vtt
preview_path: /mnt/stash/generated/screenshots
marker_path: /mnt/stash/generated

3. Add your tag IDs

The script uses Stash tags to track which scenes are in-progress and which had errors. At startup it resolves these by tag name from Stash (creating only when missing), updates in-memory IDs, and persists the resolved IDs back to your config file.

hashing_tag: 0
hashing_error_tag: 0
cover_error_tag: 0

4. Path translation (multi-machine setups)

If this node and your Stash server see the same files at different paths, add translations. If translations is empty, startup tries a best-effort auto-detection from scene paths + your local generated-media mount roots:

translations: []

5. Run the health check

Before your first real run, make sure everything is wired up correctly:

uv run stash-videohasher --health-check

This validates your Stash connection, checks that the configured phash backend is ready, confirms output paths are writable, and does a real test encode on whichever GPU encoder you have configured. All green? You're ready to go.

---

PHash Backend

Phash generation supports two backends, controlled by phash_backend in config.yml:

Internal (default)

phash_backend: internal

Pure-Python implementation — no binary needed. Requires numpy and scipy:

uv add numpy scipy

Implements the same algorithm as goimagehash (the library Stash uses internally), validated against a library of stored hashes. VAAPI hardware decode is used for frame extraction when available.

Videohashes binary

phash_backend: binary

Uses Peolic's videohashes binary. Download the right executable for your OS into the bin/ directory. No additional Python dependencies required.

---

GPU Acceleration

The script auto-detects VAAPI at startup and picks the best encoder automatically. You can also override it from the CLI or lock it in via config.

VAAPI (Intel / AMD)

vaapi: true

uv run stash-videohasher --vaapi    # force on
uv run stash-videohasher --novaapi  # force off

NVENC (NVIDIA)

nvenc: true

uv run stash-videohasher --nvenc

VideoToolbox (Apple Silicon / macOS)

videotoolbox: true
videotoolbox_codec: h264

uv run stash-videohasher --videotoolbox
uv run stash-videohasher --novideotoolbox
uv run stash-videohasher --videotoolbox-codec hevc

VideoToolbox support is macOS-only and requires FFmpeg built with h264_videotoolbox (for H.264) and/or hevc_videotoolbox (for H.265/HEVC). It is currently used only for MP4 preview encoding (scene previews and marker MP4 clips). Sprites, WebP, JPG/screenshot extraction, cover extraction, and phash generation stay on their existing paths.

When both are available

hw_priority: vaapi

uv run stash-videohasher --hw-priority nvenc

Encoder resolution order: VAAPI → NVENC → VideoToolbox → libx264

Performance comparison

When benchmarked on a batch of 25 comparable scenes VAAPI came out ~35% faster than NVENC. Results will vary depending on your GPU generation, driver version, and video characteristics — but GPU acceleration over software is always worth enabling if you have it.

---

Usage

The basics

Phash is always generated — it's the core job and runs unconditionally whenever a scene is processed. You don't need a flag for it.

Sprite and preview generation follow the generate_sprite and generate_preview settings in config.yml (both default to True). Marker generation can be enabled in config or via --generate-markers. CLI flags force these on regardless of config.

# Default run — phash + cover + whatever is enabled in config.yml, loops until done
uv run stash-videohasher

# Force all generation on, regardless of config
uv run stash-videohasher --generate-sprite --generate-preview --generate-markers

# Run one batch and exit (good for cron)
uv run stash-videohasher --once --batch-size 25

# Test on a small sample first
uv run stash-videohasher --once --batch-size 5 --verbose

# Filter to specific files
uv run stash-videohasher --filemask "JoonMali*" --generate-sprite --generate-preview --once

Generate missing media in bulk

The integrated flags (--generate-sprite, --generate-preview, --generate-markers) only run during scene processing — they won't touch scenes that already have a phash. If you want to backfill sprites, previews, or marker media for scenes that were already hashed, use the standalone modes instead. These search for scenes missing specific media regardless of phash status:

# Generate missing sprites (50 at a time)
uv run stash-videohasher --standalone-sprites --sprite-batch-size 50 --verbose

# Generate missing previews (25 at a time)
uv run stash-videohasher --standalone-previews --preview-batch-size 25 --verbose

# Generate missing marker media (100 at a time)
uv run stash-videohasher --standalone-markers --marker-batch-size 100 --verbose

# Run all three at once
uv run stash-videohasher --standalone-sprites --standalone-previews --standalone-markers

You can also generate only specific types of marker media:

uv run stash-videohasher --standalone-markers --marker-preview-only     # MP4 clips only
uv run stash-videohasher --standalone-markers --marker-thumbnail-only   # WebP animations only
uv run stash-videohasher --standalone-markers --marker-screenshot-only  # JPG screenshots only

Error recovery

# Retry scenes that previously failed
uv run stash-videohasher --retry-errors

# Clear all error tags to start completely fresh
uv run stash-videohasher --clear-error-tags

See what it would do

uv run stash-videohasher --dry-run --verbose --once
uv run stash-videohasher --standalone-markers --dry-run --verbose

---

Marker Generation

Turn marker generation on in config.yml or with the --generate-markers flag:

generate_markers: true

marker_preview_enabled: true
marker_thumbnail_enabled: true
marker_screenshot_enabled: true

marker_preview_duration: 20
marker_thumbnail_duration: 5
marker_thumbnail_fps: 12
marker_batch_size: 50

Marker files are saved alongside your other generated media:

{marker_path}/markers/{oshash}/{seconds}.mp4
{marker_path}/markers/{oshash}/{seconds}.webp
{marker_path}/markers/{oshash}/{seconds}.jpg

---

CLI Reference

Core options:
  --batch-size N        Scenes per batch (default: 25)
  --max-workers N       Parallel worker threads (default: 4)
  --once                Process one batch and exit
  --verbose             Progress bars and detailed output
  --debug               FFmpeg commands and timing breakdowns
  --dry-run             Simulate without making changes
  --filemask PATTERN    Filter scenes by filename (e.g. 'JoonMali*')
  --windows             Use Windows paths and binaries

Integrated scene processing (only runs on scenes missing a phash):
  --generate-sprite     Force sprite generation on during scene processing
  --generate-preview    Force preview generation on during scene processing
  --generate-markers    Force marker generation on during scene processing

Standalone modes (runs regardless of phash status — use to backfill existing scenes):
  --standalone-sprites          Generate missing sprites only
  --sprite-batch-size N         Batch size (default: 25)
  --standalone-previews         Generate missing previews only
  --preview-batch-size N        Batch size (default: 25)
  --standalone-markers          Generate missing marker media only
  --marker-batch-size N         Batch size (default: 50)
  --marker-preview-only         MP4 clips only
  --marker-thumbnail-only       WebP animations only
  --marker-screenshot-only      JPG screenshots only

Hardware acceleration:
  --vaapi                       Force VAAPI on
  --novaapi                     Force VAAPI off
  --nvenc                       Enable NVIDIA NVENC
  --videotoolbox                Enable Apple VideoToolbox encoder (macOS only; scene/marker MP4 previews)
  --novideotoolbox              Disable VideoToolbox
  --videotoolbox-codec {h264,hevc,h265}
                                VideoToolbox codec for MP4 previews
  --hw-priority {vaapi,nvenc}   Which encoder wins when both are available

Utilities:
  --health-check        Validate config and exit
  --retry-errors        Process scenes with error tags
  --clear-error-tags    Remove all error tags and exit
  --no-auto-setup       Disable startup autofill for missing tag IDs/translations

---

Running on multiple machines

This is where it really shines. Each node claims a batch of scenes via Stash tags, processes them, and releases the claims when done. Other nodes skip anything that's already claimed.

1. Node A claims scenes 1–25 (adds "In Process" tag)
2. Node B sees those as claimed, picks scenes 26–50
3. When Node A finishes a scene, it removes the tag
4. That scene is only eligible again if it still needs work

There's a small race window during random page selection, but the claiming system covers it almost entirely in practice.

---

Error Handling

One failure won't take down the batch. Each scene processes independently. If something goes wrong:

• Phash failures get tagged with hashing_error_tag
• Cover failures get tagged with cover_error_tag
• The failure is logged to error_log.txt with a timestamp
• The scene is skipped in future runs until you explicitly retry it

Every scene also has a 10-minute timeout. If a video is hanging for some reason, it gets tagged and the batch continues.

---

Troubleshooting

VAAPI not working — Run --health-check. Make sure you have Intel/AMD GPU drivers installed, FFmpeg compiled with VAAPI support, and read/write access to /dev/dri/renderD128 (or whichever device you have).

Setting up VAAPI on Ubuntu:

• Intel (Broadwell and newer): Install intel-media-va-driver (or intel-media-va-driver-non-free for additional codec support), then verify with vainfo. See the intel/media-driver repo for supported hardware.

  sudo apt install intel-media-va-driver vainfo
  

• Intel (older / Haswell and below): Use i965-va-driver instead.

  sudo apt install i965-va-driver vainfo
  

• AMD: VAAPI support is included in Mesa — install mesa-va-drivers and the AMDGPU firmware.

  sudo apt install mesa-va-drivers vainfo
  

• FFmpeg VAAPI guide: trac.ffmpeg.org/wiki/Hardware/VAAPI — covers filter graphs, encode/decode support, and troubleshooting FFmpeg-specific issues.
• Ubuntu community wiki: help.ubuntu.com/community/HardwareVideoAcceleration — broader overview of VA-API, VDPAU, and NVENC setup on Ubuntu.

Leftover temp directories — All temp files go in .tmp/ and are cleaned automatically at the start and end of each run. If something was interrupted, just run the script again and it'll clean up.

Error tags piling up — Check error_log.txt to see what failed, fix any config issues, then:

uv run stash-videohasher --clear-error-tags
uv run stash-videohasher --retry-errors

Process hangs — The 10-minute timeout per scene should prevent this. If you're still seeing hangs, check error_log.txt for details on which scenes are timing out.

---

License

MIT — see LICENSE

Credits

• Stash — the media organizer this was built for
• goimagehash — the perceptual hash algorithm this implements
• Peolic's videohashes — alternative binary backend
• Everyone who filed bugs and tested fixes

---

Pro tip: Run this on a few machines simultaneously, set --batch-size 50, schedule it with cron, and let it work through your backlog overnight.