mpd, Syncthing, and ffmpeg: The Technical Showdown for Local Music Stat Sovereignty
The practical implementation centers on specialized, local toolchains. One suggested workflow involves using `yt-dlp` to pull YouTube content, piping it through `ffmpeg` for trimming, and logging statistics manually via `printf` for processing with `awk` or `sort/uniq`.
The community sharply divides over data ownership: some push for pure local control, citing tools like `mpd` with `mpdtrackr` or self-managed solutions like Maloja. Others are swayed by the perceived convenience of centralized services like Last.fm, while others favor specific desktop clients like Strawberry Music Player or Deadbeef. A highly technical approach using `mpd` is recommended for local stat tracking.
The strong consensus leans toward building robust, self-contained local systems. The fault line remains between the 'convenience of cloud services' and the 'absolute necessity of private, self-managed data streams.'
Key Points
Use `mpd` backend with `mpdtrackr` for local music statistics.
Multiple users cited `mpd` as the flexible, reliable core backend for local play tracking, notably mentioned by 'tal'.
Prioritize fully self-hosted, private data management over corporate tracking services.
The overarching theme is rejecting reliance on external services, emphasizing local control.
A complex, manual workflow exists for streaming video content.
User 'sin_free_for_00_days' detailed a workflow: `yt-dlp` -> `ffmpeg` -> `mpv` + manual stat logging.
Specific local applications are viable tracking alternatives.
Suggestions included Strawberry Music Player (for Last.fm sync) and Deadbeef (as a general Linux alternative).
Concrete, dedicated self-hosted trackers exist.
The tool Maloja was explicitly named as a self-contained, on-the-ground solution for tracking listening habits.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.