Skip to content

DAWWW-CORE Desktop — Public Showcase Launch

Latest
Latest

Choose a tag to compare

View all tags
@charli-dev420 charli-dev420 released this 17 Aug 02:42
· 17 commits to main since this release
1
3a3e181
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

DAWWW-CORE Desktop is now presented publicly through this repository.

Desktop today

The Desktop version runs directly in the browser and is available without a payment flow. It is built around a local-first project model: creative sessions remain primarily on the user's device and can be exported as portable .dw projects.

Production surface

The current studio brings together the core modules of a DAW in one project environment:

  • Sequencer with detailed per-step controls
  • Piano roll for note-level editing
  • Arranger / song timeline
  • Mixer, routing and master path
  • Automation
  • Master and stem-oriented export workflows
  • Local save / restore and .dw import / export

Built-in sound palette

DAWWW-CORE currently includes 51 built-in instruments across drums, basses, electronic synths, pads, keys, bells, guitars, orchestral instruments and sampler-based workflows.

The built-in processing set contains 16 effects, including EQ, compressor, reverb, delay, modulation, distortion, filter, gate, limiter, saturator, bitcrusher and utility processing.

Desktop ↔ Android

DAWWW-CORE uses one project model across platforms. The upcoming Android version will be offered by subscription and is designed as a complete cross-device continuation of Desktop: the same .dw project moves between Desktop and Android without a separate mobile project format or conversion step.

Local-first

Cloud project storage is not required for a project to exist. Browser-local persistence is used for active Desktop sessions, while .dw provides the portable project copy used for transfer, backup and recovery.

Current practical limits

Session capacity depends on the local device: CPU, memory, browser storage quota, audio-device behaviour and the complexity of instruments/effects/routing in use. DAWWW-CORE therefore does not publish arbitrary universal limits for track count, polyphony or project size.

Links

This repository is the public product showcase. The production application and audio-engine source remain private.

Assets 2
Loading