A browser notebook for 303 ideas, built around the real work of editing tiny musical decisions.

What problem 303box is trying to solve

Step sequencers are powerful precisely because they reduce music to small decisions. That can also make them slow to edit. On hardware, a single idea may require moving between pitch entry, octave switches, accent, slide, gate length, pattern pages and MIDI settings. 303box puts those decisions on one screen so a phrase can be read as a whole before it is transferred to a machine.

The goal is not to replace the instrument. Hardware still matters for sound design, performance, tactile control and saving the final pattern. The browser is used as a planning surface: a place to compare alternatives, hear a rough audition and keep a readable reference beside the device.

What the generator does — and what it does not do

The pattern generator is rule-based. It uses constrained pitch choices, rhythmic masks, repeated motifs, controlled mutations and limited accent/slide placement to create a starting point. It does not call a generative-AI composition service and it does not claim authorship of the music. A generated result is intentionally editable and disposable.

This distinction matters to the design of the site. A useful sketch should expose its decisions. You should be able to see that step 4 is a rest, step 7 is accented, step 10 moves up an octave or step 14 slides into a target note. Hidden musical decisions are less useful when the destination is hardware that must be programmed or performed deliberately.

Why the site includes long-form guides

The sequencer alone can show controls, but controls do not explain judgment. The editorial pages document why a rest can be more useful than another note, why slide needs a meaningful destination, why MIDI channel matching matters, how browser output differs from hardware output, and how to troubleshoot a connection without randomly changing every setting.

These articles are written specifically around the behavior and workflow of 303box. They are not copied manufacturer manuals and they are not generic summaries assembled to create search traffic. When a hardware-specific statement may vary by firmware or device configuration, the guide says so and points the reader back to the device's own settings or manual.

Hardware support is compatibility, not affiliation

303box currently focuses its hardware workflow on the Roland T-8 and Behringer TD-3 families because they represent two practical acid workflows: a compact rhythm-and-bass device and a dedicated 303-style bass synthesizer. Product and company names are used only to describe compatibility and user workflow. 303box is an independent project and is not endorsed by, sponsored by or affiliated with Roland or Behringer.

MIDI is also configuration-dependent. A device can be physically connected and still be silent because the selected browser output, MIDI channel, transport setting or device-side receive setting does not match. For that reason, the hardware guide treats connection status and musical playback as separate checkpoints instead of treating “USB connected” as proof that the whole signal path is correct.

Editorial and quality standards

Each guide should answer a real task a user can perform in the site or on connected hardware. Pages are reviewed for factual consistency with the current interface, and examples are written for 303box rather than reproduced from other sites. If the interface changes, the documentation is expected to change with it.

• Originality: examples, explanations and troubleshooting steps are written for this project.
• Clarity: articles separate facts, recommendations and device-dependent settings.
• Practical value: a reader should leave with a repeatable workflow, not only background information.
• Limitations: the site avoids claiming that browser emulation exactly reproduces the analog behavior of a particular instrument.
• Maintenance: pages carry stable canonical URLs and are included in the sitemap so updates remain discoverable.

Privacy and local browser state

The pattern editor uses browser features such as Web Audio, Web MIDI and local storage to provide interactive behavior. MIDI access is requested by the browser and remains subject to the browser's permission model. The site does not need a user account to create a pattern. Some preferences and MIDI router choices may be stored locally so the workspace can reopen in a familiar state.

Advertising and analytics consent are handled separately from the core sequencer. More detail is available on the privacy page. The practical principle is that using the sequencer should remain possible without pretending that an advertising click is part of the musical workflow.

Who 303box is for

The primary audience is producers, live performers and curious beginners who want to understand a 303-style sequence at step level. Some users will build a pattern in the browser and enter it manually on hardware. Others will use Web MIDI for immediate audition. Others may never connect a device and simply use the grid to learn how pitch, gate, accent, slide and octave interact.

Those are different workflows, but they share one requirement: the pattern must remain understandable. The interface and the articles are therefore designed around readable decisions rather than around hiding complexity behind a single “make music” button.

Where to continue

If you are new to acid sequencing, start with the 303 pattern programming guide. If you already understand the grid and want concrete phrases to study, use the annotated pattern examples. For external instruments, read the MIDI and hardware workflow guide. The learning library groups the articles by goal.