
What components are you using? (building a database for my new component)
Hey everyone,
I just released my second foobar2000 component: Component Update Checker, a small 64-bit component that checks your installed third-party components against their GitHub Releases and tells you when an update is available. It doesn't auto-download or auto-install anything — it just points you to the release page so you can decide for yourself.
What it does:
- Detects your installed components automatically
- Checks GitHub Releases for updates (manual check, or automatic on startup)
- Shows results in a popup window with a clickable link to the release page
- Has a shared, community-maintained database so a lot of components can be checked without you having to register anything yourself
Right now it only supports GitHub Releases, but I'm planning to add support for other sites down the line too.
Requirements: foobar2000 (64-bit)
GitHub (source): https://github.com/p2ashiura/foo_component_update_checker
Full disclosure: I have zero programming background. All I did was come up with the feature ideas and describe what I wanted — Claude (Anthropic's AI) wrote every line of the actual code, same as with Album Train. Wanted to be upfront about that since it's very much a collaborative build rather than something I coded myself.
It's MIT licensed and open source.
This is where I'd love your help: the shared database (https://github.com/p2ashiura/foo_component_update_checker-registry) is still pretty small — just what I could personally verify. If there's a foo_ component or DSP you use and would like update notifications for, let me know! 64-bit is ideal, but even if it's 32-bit-only, tell me anyway, it's worth having on record. Just the name is enough — a download page URL helps too if you happen to have one handy, but isn't required.
Feel free to just comment here with what you're using, or if you want, there's also a "Suggest for Shared Registry..." button inside the component itself that opens a pre-filled GitHub pull request for you.
Thanks for reading!