A DAW isn’t just about sound. It’s about memory. It’s about being able to stop, sleep, return, and pick up exactly where you left off.
That’s why we built a robust save/load system — not just to store data, but to preserve experience.
When you click save, Jiku Music captures everything:
- BPM, bars, snap settings
- Instrument tracks with waveform, volume, mute state, and notes
- Vocal tracks with metadata and audio blobs
- Active track focus
- Track IDs and color assignments
It even encodes your vocal recordings into base64 so they can be embedded directly into the .jiku file — no external assets, no broken links.
This isn’t just a snapshot. It’s a full state export.
When you load a file, the engine parses every field, reconstructs every track, decodes every vocal blob, and restores your session with precision.
It’s fast. It’s resilient. It even validates the file version and structure before proceeding — so you don’t crash your studio with a corrupted import.
And if something goes wrong? You get a clean error message. No silent failures. No mystery bugs.
When you’re ready to share your music, Jiku Music renders the entire mix into a WAV file using OfflineAudioContext.
It schedules every oscillator. It routes every vocal buffer. It applies gain envelopes and timing logic. It renders the final output at 44.1kHz with 16-bit depth — ready for mastering, uploading, or distribution.
This is where your browser becomes a mastering suite.
The save/load/export system isn’t flashy. But it’s foundational.
It’s what makes Jiku Music feel like a real DAW — not just a toy, not just a sketchpad, but a serious tool for serious creators.
And as we evolve, this engine will support:
- Versioned backups
- Cloud sync
- Session history
- FX rack presets
- Collaborative loading
Because memory isn’t just about storage. It’s about continuity. It’s about trust.
And Jiku Music remembers everything.
