a quest to organize my massive collection of samples
Go to file
2024-05-08 02:44:45 -07:00
.github Fix CD 2024-05-08 02:44:45 -07:00
cmd/keepr Fix CI and main app location 2024-05-08 02:40:56 -07:00
internal Fix: reduce log spam 2024-05-08 02:26:02 -07:00
.gitignore Fix CI and main app location 2024-05-08 02:40:56 -07:00
go.mod Fix CI and main app location 2024-05-08 02:40:56 -07:00
go.sum various improvements 2024-05-08 02:04:06 -07:00
README.md Update README.md 2024-05-08 02:10:18 -07:00


organize your audio samples.. but don't touch them.


  • too many audio samples
    • 250 gigs scattered about in different subdirectories
    • moving them would immediately cause chaos in past project files


  • create folder filled with subfolders that we populate with symlinks.
    • use file names, wav data, and parent directory names for hints
    • allows for easy browsing of audio samples from any standard DAW browser by:
      • key
      • tempo
      • percussion type
      • whatever we think of next

keepr is fast. really fast. on my system the bottleneck becomes I/O. When reading and writing to a single NVMe drive keepr averages around 700MBp/s disk read and spikes up to nearly 2GBp/s disk read.

will you ever finish it

do I ever finish anything? idk maybe. it works right now better than the old version (which was a shitty bash script that ran fdfind), so it's lookin good so far.

  • guess tempo by filename
  • separate wave files and midi files
  • validate wave files
  • guess key by filename
  • guess drum type by parent directory
  • create symlinks for all of the above\
  • be stupid dumb fast
  • verify various theories with wave/midi data
  • sort MIDI files
  • more taxonomy
  • unit tests
  • in-app documentation
  • more to-do items