Repository navigation
Conversation
The CPU FULL guard read the meter at the moment of the pick, so picks made while stopped passed and left a Part that played over the line. Stopped, it now goes by the mean of the last four seconds the unit played, if that is more, and the box says WAS BUSY PLAYING. The base is not regenerated. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…he MKII Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
23f3f1b1of base4e9a87ea, 29 modules) the stopped unit read 70 %, four module effects were accepted, and playing then read 95 to 97 % with frames at 121 to 130 % until the DSP frames stopped (stall record 44). Measured with an encoder probe the same day, the panel is unchanged up to 83 %, and from 87 % a knob turn starts to wait for its redraw (0.1 to 0.2 s from 90 %).modwerk_status_cpu_load,cpu_note_playedinstatus.c). The box then reads "WAS BUSY PLAYING" in place of "UNIT IS BUSY" and shows that figure.machine_registry.casks the same figure for a machine pick.selection.c,dsp.candmanager.care untouched.test_status.c(kept only after eight readings in a row playing, a stop starts the count again, used only while stopped and only when higher, the refusal counted, stock and NONE pass, a lighter last play passes) and the registry host tests insdk/tests/test_machine_events.pyandtest_fract_public_registry.py. A build with the new rule broken fails the new checks.node scripts/docs.mjspasses.npm run pr:readywas not run.c6e655c7of this branch, started from the flashed base; Air Chorus, Tape Echo, Euclid, Mini Verb, POLY8 and FM Synth 0.1.2 installed): never played, stopped at 54 %, Mini Verb on T1 FX2 went through. After twelve seconds playing at 93 %, stopped at 66 to 68 %: Mini Verb on T1 FX2, Euclid on T1 FX1 and POLY8 on T2 SRC were each refused with "CPU FULL / CPU 93% / WAS BUSY PLAYING"; FILTER and NONE on T2 FX1 went through. With FM Synth removed and no play since, Mini Verb was still refused; after twelve seconds playing at 81 % and a stop, it went through.cpuentry after four refusals; whether that is intended was not looked at.docs/MODULE_PERFORMANCE.mdsaid the guard reads the moment of the pick; it now says how a stopped unit is judged and what the limits are.docs/verification/2026-11-13-cpu-guard-panel-lag.mdis the record of the day's runs: what the guard refused and let through, the lag by load, how it was measured, and what was not shown. The UI tick count and tick gap did not show the lag at any load; the record says so.Draft until: its turn at a base regeneration.
🤖 Generated with Claude Code