Octave

Octave is a containerised tool that syncs your Spotify playlists into a Jellyfin library, requests missing albums in Lidarr, and enriches album matching with…

  • Media Applications
  • Media Servers
  • Tools & Utilities
Octave is a containerised tool that syncs your Spotify playlists into a Jellyfin library, requests missing albums in Lidarr, and enriches album matching with ListenBrainz and Last.fm metadata. Browser-based setup means no config-file editing is needed. Aimed at homelab media stacks already running Jellyfin and optionally Lidarr.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

51/100 Fair

Maintained
77last commit 73 days ago
Popular
102 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
701 GB minimum RAM

Availability: platform listings confirmed today, links checked 19 days ago

GitHub stars
2
Open issues
1
Last commit
2026-09-09
Latest release
v3.3.5
License
MIT
Activity
stale

Checked 6 days ago - source: GitHub (johagan94/octave)

Resources & Compatibility

Minimum requirements: 1 GB RAM, 614 MB disk.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start Octave and get help Use octave --gui in a terminal (the text window where you type commands) to open the windowed app, or octave for a text-only prompt; type help command or doc when you need an explanation. This is how you begin using Octave and find answers without leaving the app. source
  • Tell Octave where your files live Use cd to move to the folder where your Octave files (.m, text files with code) live, and addpath if Octave should search another folder; without this, Octave cannot find your scripts or functions. source
  • Install and load extra packages Use pkg search and pkg install to add useful packages such as statistics or image, then pkg load to activate them; without loading, the extra commands won't be available. source

Fetched 47 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need to edit a config file to set up Octave?

No, you configure it in the web UI Settings after starting the container. You enter the Spotify Client ID and connect, then enter Jellyfin details and optional Lidarr details.

Does Octave require a Spotify client secret?

No, normal setup uses PKCE Spotify OAuth and only needs the Spotify Client ID. Octave still accepts a Client Secret for legacy setups.

Can Octave be protected if exposed to a browser?

Yes, it has optional HTTP Basic Auth for exposed deployments.

Can Octave request missing albums in Lidarr?

Yes, it can request missing albums in Lidarr and track those queued albums across runs. It performs up to four concurrent album lookups.

How do I schedule Octave syncs?

Scheduled syncs use the SYNC_SCHEDULE cron value, with the default at 2 AM UTC. You can also manually trigger a sync from the dashboard.

Does Octave remember matches and run history between restarts?

It keeps a persistent track cache and library index, and stores every run in SQLite history. That history survives restarts cleanly.

Answers sourced from github.com

Community

Collected 49 days ago - public community threads