gogul09/deep-drum

Purpose and Entry Point

This is a static, browser-based intelligent music demo. It generates continuous drum patterns from a seeded rhythm and arpeggios from input notes plus chord context, using Magenta DrumsRNN and ImprovRNN concepts. The application starts from index.html, with presentation styling in css/app.scss and compiled css/app.css.

Browser Runtime and UI Layer

The client runs entirely in the browser; no server, API, database, or deployment runtime is represented in the repository. Materialize provides UI styling/components, while Nexus appears to provide interactive music-control widgets.

• index.html

• externals/css/materialize.css

• externals/js/materialize.js

• js/nexus.js

Control and State Coordination

Control changes are centralized through an update layer, which likely propagates user selections—such as tempo, instruments, patterns, or musical settings—to the sequencing and playback modules. Multi-selection/tag behavior is separated from the main control updater.

• js/update_controls.js

• js/multiple_tag.js

• js/gpad.js

Generative Music Stages

The core generation pipeline is split by musical role. deepdrum.js is the drum-pattern generation integration corresponding to the README’s DrumsRNN behavior. arp_and_bass.js handles generated arpeggio/bass behavior associated with ImprovRNN-style chord-conditioned note generation. chord_finder.js supplies harmonic context to the arpeggiator.

• js/deepdrum.js

• js/arp_and_bass.js

• js/chord_finder.js

Musical Representation and Scheduling

Music-theory utilities, MIDI/note mapping, and timeline scheduling form the boundary between generated symbolic patterns and audible playback. Generated or user-entered notes must be mapped into playable pitches/instruments and placed on a time sequence.

• js/tonal.js

• js/reverse_midi_map.js

• js/timeline.js

Audio Engine and Local Media Boundary

Tone.js is the browser audio runtime. Playback depends on repository-hosted audio samples rather than an external streaming service: piano samples in Salamander, guitar samples, bass, and several named drum kits. The generation/control code ultimately drives this audio layer.

• js/tone.js

• sounds/salamander/C4.mp3

• sounds/acoustic_guitar/A3.wav

• sounds/drum-kits/analog/kick.mp3

Primary Flow

User interaction in the page and Nexus/Materialize controls updates application state. Seed rhythms feed the drum generator; notes and detected/selected chords feed the arpeggio generator. These symbolic outputs pass through tonal/MIDI mapping and the timeline, then Tone.js schedules local instrument samples for browser playback. The important boundary is between generative pattern logic (js/deepdrum.js, js/arp_and_bass.js) and deterministic sequencing/audio playback (js/timeline.js, js/tone.js).