CUzeboxEX Audio Scope
Connecting…

Uzebox DAC source 15.7 kHz unsigned 8-bit stream

Move over the waveform to inspect a sample.
This view reads CUzeboxEX's existing audio ring. It adds no capture work to the emulation/audio path. Samples at 0x00 or 0xFF are marked as DAC rail hits.

Native Uzebox DAC writes OCR2A · cycle/PC/beam correlated

Arm DAC history to correlate native samples with AVR instructions.
SeqCycleRasterPCOCR2AFlags
This observes the final 8-bit PWM sample written by the emulated Uzebox kernel. It does not infer individual logical mixer channels. Clicking an event opens it in the main debugger at the exact AVR PC/beam position.

Host audio output post-resample/filter/reverb/volume

Output capture is off.
Performance: when output capture is OFF, SDL is connected directly to the original audio callback. There is no scope branch, ring write, or clip scan in the normal callback. Arming capture reopens the audio device with a wrapper that records the already-generated host samples; disarming restores the original callback.

Spectral / continuity analysis browser-side · no emulator capture path

Hann-windowed FFT; pitch is a normalized autocorrelation estimate and may be ambiguous for chords/noise.

Uzebox source

Host output

DC offset, large sample steps and constant runs are calculated from the displayed windows only. The host spectrum exists only while output capture is armed.

Native DAC cadence OCR2A cycle spacing

Cadence uses the cycle timestamps already stored in armed DAC history. It can expose late or missing DAC updates without adding another timing hook. Large cycle gaps are stronger underrun/discontinuity evidence than waveform shape alone.

Clipping attribution

Native DAC rail means OCR2A itself reached 0 or 255. Host rail means the final SDL output reached its device endpoint after resampling/filtering/monitor effects/reverb/master volume.

Attribution is by observed stage, not by logical Uzebox mixer channel. If host rails occur without native DAC rails in the armed evidence window, host-side processing is the likely added contributor. Repeated consecutive rail samples are stronger clipping evidence than a single endpoint sample.

Capture behavior

The source oscilloscope needs no explicit arming. Host-output capture is opt-in and is automatically disarmed when this page unloads on browsers that deliver the unload beacon.