You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Double-clicking the status bar on macOS zooms the window again, as
double-clicking a title bar does everywhere else on the Mac — the status bar
is this window's title bar, and it had answered nothing since 0.3.0. It obeys
the system's "double-click a window's title bar to" setting, so a Mac set to
minimise minimises and one set to do nothing does nothing, and it waits the
double-click interval that Mac was configured with. No control in the row
answers any later for it: what Flutter recognises there is still a single
click, and the pair is counted in the runner.
⚡ Changed
The iOS and Android home screen label is OAA, the wordmark the status bar
already draws. It was Open Audio Analyzer, which no tablet ever actually
showed: iOS fits an icon label to the width of one icon by tightening the
tracking before it truncates, and tracking is spent on the spaces between
words first — a 19-character name arrived on the home screen as OpenAudioAnal…, run together and cut short anyway. Apple's guidance is
twelve characters. The product's name is unchanged everywhere it fits: the
macOS, Windows and Linux applications, both permission prompts, and every
configuration directory — nothing a tablet has saved moves.
🐛 Fixed
The canvas no longer gets slower the longer a spectrogram is on screen. The
spectrogram redrew its whole history as run-length marks on every published
frame, and its cost was budgeted against smooth columns — real material
jitters a brightness step between most adjacent rows, so a large display was
re-recording and re-rasterising 150,000–230,000 marks about 47 times a
second, a cost that ramped for the half-minute the history took to fill after
a mount and then stayed. Every meter repaints from the same clock, so it
dragged the whole canvas — most visibly the analyser — and the remote display
paid the same price on weaker hardware, more of it at the 60 fps link rate.
The history is now kept as pixels and drawn as one image, a quarter of a
millisecond per published frame whatever the signal does; the numbers are in tool/bench_spectrogram.dart.
On a remote display, the tab control now sits beside the name of the machine
being watched instead of stranded in the middle of the link bar. The bar kept
room for the host's playhead whether or not the host had one, so on every host
with no DAW behind it — a desktop metering a device or a file, which is most
of them — 248 px of nothing stood between the name and the tabs. The slot
appears with the playhead and does not move again while the link lasts, so a
reading that goes stale does not shift the tabs out from under your finger.
🚧 Internal
tool/bench_spectrogram.dart is formatted the way the test job's dart format --set-exit-if-changed step demands. It was not, so that job
failed on every push after the benchmark landed while the analyzer, the
suites and the benchmark itself all stayed green. That step is now listed
with the other gates in README.md and CLAUDE.md, which is why it was
never run by hand.