Atlas node · Tools · working study

frZone_core

Frequency-zone trigger instrument for turning sound analysis into visible thresholds and downstream MIDI or OSC events in performance and teaching contexts.

Repository →

Where sound becomes a switch

frZone listens for the moment when sound stops being atmosphere and starts becoming action. Bands, thresholds, and triggers make an event stream out of pressure in the air.

The work matters because analysis can disappear into the machine. frZone keeps the threshold visible, so a performer or learner can see how a sound becomes a message, a change, or a cue.

The architecture notes, MIDI map, OSC addresses, and quickstart material show the grammar of the tool. The next proof is a short capture where the input, threshold, and output move together in public.

The public claim should stay with legible trigger behavior. Classroom outcomes, scene reliability, and larger rig integration need direct evidence before they become stronger claims.

What it is

frZone is a frequency-analysis tool that divides audio into playable or teachable zones. It belongs in the Atlas as both a DSP study and a classroom-friendly way to make audio behavior legible.

What it lets people do

It lets people hear and see how bands, thresholds, and trigger logic turn sound into event streams instead of treating analysis as a hidden background process.

What is public now

Evidence status

Status: working study. Source documentation supports the architecture, but the public page still needs a short capture where audio input, threshold state, and MIDI or OSC output are all visible at once.

Next proof object: 30-second screen recording showing frequency analysis, threshold adjustment, and MIDI or OSC output changing in real time.

What remains unresolved

  • The current public page should not claim classroom outcomes or live-rig reliability yet.
  • A public-safe trigger log or CSV example would strengthen the teaching and testing story.
  • Integration with MOARkNOBS-42, SeedBox, or Horizon should stay modest until directly captured.

Methods surfaced

Proof objects

Source trail

  • Project repo — Implementation truth.
  • Last reviewed: 2026-05-15

The Atlas is the relationship layer. Use the repository for current project-specific truth, and use studio-notes when methods, decisions, or teaching material need to travel across the fleet.

Where to go next

  • Open MOARkNOBS-42 — See the control surface that can feed or accompany this analysis branch.
  • Open live-rig — See where this kind of trigger logic can leave the lab and enter a scene system.