A central station for every sound you own.
Sample Squad Sound Station grows beyond media playback into a local, producer-centered system for discovering, understanding, auditioning, organizing, preparing, assigning, and remembering sounds.
- FILES
- remain the media authority
- SSSS
- becomes the relational authority
- SPACEAGE
- becomes the first production bridge
- LOCAL
- analysis stays private by default
“Sounds arrive, get understood, auditioned, organized, routed into kits and projects, and remain findable long after the session ends.”
The product is not merely a player, browser, database, or preset editor. Its advantage comes from connecting those functions into one continuous memory of a producer’s sound library.
Six modules, one connected memory
Each module solves a distinct problem, but the catalog and stable sound identities allow every decision to benefit the others.
Player
Everyday audio, MIDI, playlists, metadata inspection, EQ, conversion, and visualization.
Library
Recursive cataloging, watched roots, rich filters, saved searches, duplicates, and sonic similarity.
Sample Scout
Fast keyboard auditioning, fair level comparison, stars, rejects, ratings, notes, and candidates.
Kit Builder
Four banks of movable 16-pad workspaces for provisional kit construction and portable export.
SpaceAge Bridge
Open presets now; later send pads or whole kits directly to a chosen SpaceAge instance.
Usage Graph
Track where sounds were used, what they became, which projects depend on them, and how to find them again.
Organize around intent, not database chores
The user should feel a smooth creative workflow. Catalog maintenance happens quietly underneath.
Discover
Add library roots once. Search filenames, tags, folders, technical traits, acoustic character, history, and similarity.
QUESTION ANSWERED“Where are the short, dark kicks I have not used yet?”Evaluate
Move through results with Up/Down, replay with Space, compare at source, peak-matched, or perceived loudness.
QUESTION ANSWERED“Which candidate actually works when loudness is not fooling me?”Assemble
Drag keepers into movable pad cards. Rearrange, swap, bank, undo, and autosave without committing prematurely.
QUESTION ANSWERED“Can I shape this kit while I am still discovering it?”Use & recall
Export or send the kit, record its project relationships, and later reveal every preset and production using a sound.
QUESTION ANSWERED“Where did this snare end up, and can I safely move it?”The database knows more than tags ever could
Embedded metadata remains useful input, but SSSS-owned knowledge lives safely beside the files instead of being forced into incompatible containers.
What each record can know
- Path, filename, source pack, size, dates, format, duration, rate, depth, channels, and codec.
- Readable embedded metadata without requiring every format to support every field.
- SSSS tags, notes, ratings, stars, collections, custom fields, and project-specific decisions.
- Waveform, loudness, peak, dynamics, transient, decay, spectrum, stereo behavior, and signal health.
- Exact duplicates, likely variants, derivatives, availability, usage, kits, presets, and projects.
How identity survives change
CORE PRINCIPLE Files remain the media authority. SSSS becomes the organizational and relational authority.
Search what it is, how it sounds, and how you used it
The ultimate finder combines exact facts, human judgment, acoustic analysis, and production history.
Questions that keep answering themselves
A saved search such as “short, dark kicks unused in this project” updates as files arrive and usage changes.
Not just a mystery score
Find similar by punch, tonal color, low end, envelope, stereo character, or overall resemblance—and explain why each result matched.
Cluster overwhelming collections
Group thousands of related kicks, snares, impacts, or ambience files into manageable sonic families and expose representative choices.
Fast listening becomes structured judgment
Sample Scout is the keyboard-first decision layer between search results and production.
Short samples need a persistent, low-latency audio path, nearby prebuffering, automatic scrolling, and visible readiness. Source, peak, and perceived matching should report the exact applied dB so comparison remains trustworthy.
Decisions may be global or project-specific. Rejecting a kick for one production should not permanently condemn it across the entire library.
A provisional pad workbench on the right
When Scout mode is active, the underused right side becomes a simplified facsimile of SpaceAge Pads: four banks above a responsive 4×4 grid.
- Drop the current sample or drag from any result.
- Move freely; drop onto an occupied pad to swap.
- Send to an unassigned tray instead of deleting.
- Undo/redo placement, replacement, bank moves, and clears.
- Workspace positions remain provisional until save/export.
- Click a pad to audition; lock finalized choices.
- Autosave protects experimentation and crash recovery.
- Portable export copies or converts only when requested.
One kit model, two delivery paths
Define a versioned portable kit format first. Live sending later transmits the same model rather than creating a second incompatible integration.
Preset export
Reliable whether SpaceAge is open or not, portable between systems, and easy to validate.
Send to open instance
Choose a project and plugin instance, then load one pad, one bank, or the full kit immediately.
Contextual feedback
SpaceAge reports stable project, preset, pad, and sample identities back into the SSSS usage graph.
A sound should carry its production history home
The catalog becomes uniquely valuable when it remembers relationships that no audio file can store by itself.
Which projects use this sample?
Is this file safe to move?
Which presets would break if this drive disappeared?
Which sounds have never been used?
What alternate versions exist?
Which snares tend to appear with this kick?
Quiet automation, visible evidence, reversible decisions
A library manager earns trust by surviving real drives, real edits, and real interruptions.
| Concern | SSSS response |
|---|---|
| Changes while SSSS is open | Real-time watchers update selected library roots quickly. |
| Changes while closed or watcher overflow | Periodic reconciliation scans repair missed events. |
| Large initial libraries | Stage discovery, technical extraction, hashes, acoustic analysis, then expensive fingerprints. |
| Removable and offline drives | Preserve records and relationships; clearly mark availability rather than deleting knowledge. |
| Original media safety | Database tags by default; embedded writes are explicit, format-limited, backed up, and defensive. |
| Privacy | Local-first analysis with no required library upload. |
| Database failure | Atomic updates, automatic backups, export, rebuild, and an auditable change history. |
Grow the station without building everything at once
Each phase should deliver a complete useful loop and strengthen the foundation needed by the next.
- FOUNDATION · NOW
Dependable auditioning and identity
Finish the persistent audio path, visible level evidence, resilient catalog records, monitored roots, and staged scans.
- WORKFLOW · NEXT
Search → Scout → Kit
Unify library results with Sample Scout and add the four-bank movable pad workspace with autosave and undo.
- DELIVERY
Portable SpaceAge kits
Agree on the shared schema, package samples safely, verify dependencies, and open exported kits in SpaceAge Pads.
- INTELLIGENCE
Fingerprinting and explainable similarity
Recognize metadata-only changes, derivatives, transcodes, sonic families, and “like this, but…” searches.
- MEMORY
Projects and usage graph
Add direct SpaceAge communication, instance selection, project identities, dependency reports, and usage-aware discovery.
- ECOSYSTEM
An open sound station
Document a local API so other tools can search, send, report usage, and participate without weakening privacy.
Questions to settle before implementation hardens them
These are product decisions, not mere technical details.
Kit portability
Copy samples, reference originals, or offer both? When should automatic WAV conversion occur?
SpaceAge truth
Exact bank count, pad count, layering rules, parameters, and stable project/instance identifiers.
Identity confidence
How should exact, probable, and speculative derivative relationships be presented and corrected?
Global vs project judgment
Which stars, rejects, ratings, tags, and notes are universal—and which belong only to one production?
Monitoring boundaries
Which roots are always watched, scan-only, removable, excluded, or private?
Product surface
When does a capability belong in the main station, a focused module, SpaceAge, or a future extension?
Design tenets
Local firstNon-destructive by defaultFast before exhaustiveExplain automatic conclusionsPreserve offline knowledgeOne identity across workflowsCreativity before administrationNames for the parts
- Sound Station
- The complete product and connected system.
- Library
- The searchable catalog and monitored roots.
- Sample Scout
- The rapid audition and judgment workflow.
- Kit Builder
- The provisional four-bank pad workspace.
- SpaceAge Bridge
- Portable and live transfer into SpaceAge Pads.
- Usage Graph
- Relationships among samples, pads, kits, presets, instances, and projects.
- Fingerprint
- A stable audio-derived identity beyond filename and tags.
- Lineage
- Evidence that one sound is a moved, edited, converted, or derived version of another.