u/MomSausageandPeppers

I Created A Local Music Player For Windows - Really Proud Of It
▲ 8 r/mp3players+5 crossposts

I Created A Local Music Player For Windows - Really Proud Of It

I am pretty proud of this project and wanted to share. I have a ton of mp3s from the past, flac from live shows, and blah blah blah. I have finally given up on Spotify and the like... and just didn't find any real players that felt inspiring. I know that Foobar is cool - but like I said... I am proud of this. Please check it out and give me some feed back.

Bullet Points About Project (AI Written):

  • Four UI shells — Retro (Bloomberg-density Winamp 2 homage), Modern (rounded, content-forward), Liquid Glass (translucent stacked panes with backdrop-filter), Concourse (operator-console split-cells)
  • Nine deck (compact-window) skins — Windowshade, Winamp Classic, Winamp Industrial, Record Player, Jukebox, Cassette Deck, Discman, Hotdog Deck, and Retro TV. Each declares its own native window size — no letterbox
  • 13 color skins — Classic, Ops, Midnight, Neon, Amber, Oxide, Steel, Walnut, Jukebox, Terminal, Ice, Miami, Mono. Plus full Winamp 2.x .wsz skin import
  • 0–100 decimal track scoring — Drag, scroll-wheel, keyboard-nudge, or double-click to type 88.3. Stars stay in sync for legacy sorts and smart rules
  • 0–200% volume with a red-zone past unity — VLC-style amp boost, full 0 dB / +6 dB tick labels, runs after the master limiter so it amplifies without clipping
  • Magazine-style Home — greeting hero with blurred album backdrop, Today's Pick (high-rated track you haven't played in 6+ weeks, with a reason chip), Your Highest Rated rail, NewAmp News editorial card, Listening Stats This Week, plus the classic Harmonic / Taste / Loved / Heavy Rotation / Fresh Imports rails
  • Living Library Discover mode — local-first crate-digging missions that turn ratings, plays, skips, fresh imports, deep album candidates, and underplayed corners into playable sessions with Deck / Full Vis / Save as Playlist actions
  • Bloomberg-density Now Playing with a tabbed side panel (On Air / Album / Lyrics), draggable spectrum-split, selectable spectrum styles, VU + waveform overview, LRCLIB-synced lyrics, optional karaoke mode, custom-lyrics editor, tempo trainer, practice A/B loop, track bookmarks
  • Milkdrop visualizer + Xbox-inspired fullscreen modes — Butterchurn presets, spectrum modes, aurora, plasma grid, and neon ribbon renderers built for 4K fullscreen use
  • Auto DJ + smart playlists — BPM/key-aware harmonic mixes, taste-learning from plays/loves/ratings/skips, smart rules with min-rating filters
  • Album art rescue + Metadata rescue — embedded art, folder art, Cover Art Archive, MusicBrainz lookup, and manual cleanup tools for rough local libraries
  • Artist facts and images — musician-first artist context and large artist images without confusing bands for species, cities, albums, or other same-name pages
  • Custom playlists — create named playlists, reorder tracks, export portable folders, and pick or drop playlist artwork for the playlist icon
  • Native guitar tab companion — cache local/Ultimate Guitar-style tabs and pop out a native tab window when a playable match exists
  • Audiophile chain — WASAPI output, ReplayGain (per-track + per-album), crossfade/gapless playback checks, software limiter, 10-band EQ, lossless WAV export of any track, output-device picker with test tone
  • CUE sheet playback — one-file albums split into playable, seekable tracks with performer/title/year/genre metadata
  • Last.fm — full scrobbling + now-playing + offline outbox queue
  • Local-first — SQLite library, sql.js, no account, no telemetry, no required network

Upvote1Downvote0Go to commentsShare

github.com
u/MomSausageandPeppers — 2 days ago
▲ 8 r/OpenaiCodex+5 crossposts

Audrey 1.0 is out: local-first memory guard for Claude Code / Codex-style agents

I posted Audrey here about a month ago when it was still rough. I kept grinding and turned it into a real 1.0 release.

What it does now:

  • local-first memory for agents, not another cloud memory service
  • pre-action checks before risky tool calls, with allow / warn / block verdicts
  • redacted tool-trace receipts so the system can learn from previous mistakes without leaking raw secrets
  • GuardBench artifacts so the claims are auditable instead of just vibes
  • Node package + Python client + MCP/server path

The point is simple: the model can propose, but the host has to decide. If the rule only lives in prompt text, it is advice. If it runs at the tool boundary with evidence, it becomes infrastructure.

GitHub: https://github.com/Evilander/Audrey

Paper / artifact preview: https://paper-site-r3jdakujn-evilanders-projects.vercel.app

arXiv is submitted but still on hold, so I am not pretending there is a public arXiv ID yet. I would rather be exact than hype fake status.

If you are building agent tooling, I would genuinely like hard feedback. Especially on the GuardBench scenarios and where pre-action memory should block vs warn.

u/MomSausageandPeppers — 7 days ago