The cymbal stem answers, and the first reading of it was on a broken clock

Watermelon In Easter Hay. Songsterr copy s6857183, head revision r8968524. Event-by-event audio check of the 101 colliding cymbal strokes, run 2026-09-08 against the isolated cymbal stem. The lane-level conclusion on this page was superseded later the same day by a rebuild on the Moises metronome stem; see the banner below.

101 strokes scored bleed control passed 4 pre-registered controls no note removed cymbal verdict superseded

SUPERSEDED 2026-09-08, later the same day. Everything below about the cymbal lane being unsupported was measured on the wrong clock. Rebuilding the alignment on the Moises metronome stem, with this same detector, this same stem and these same 1,573 notes, moves the cymbal lane from 19.3 percent confirm to 40.2 percent, from 1.46 to 3.17 times chance, and from 1.45 to 3.00 times separation. The verdict flips from weak to SEPARATES, and all five lanes now clear. The notes were always there. The ruler was wrong.

What was wrong, precisely. This page anchored its clock on 97 snare matches. Tested on the kick lane, which neither clock was fitted on, that alignment recovers 226 of 504 kicks, or 44.8 percent, across 59.3 to 506.1 seconds. The metronome clock recovers 286 of 504, or 56.7 percent, across 41.3 to 528.5 seconds. It wins by 60 kicks while covering 41 more seconds of the song, so it is not buying accuracy with a shorter span. A cymbal lane is the densest and least periodic thing on the kit, which is why a clock error punished it hardest and left snare, kick and tom looking fine.

Two things this does NOT overturn. The tom result stands and in fact moved the other way, 70.2 down to 60.1 percent confirm while still separating at 4.51 times, and that is stated here rather than buried. And the 101-collision comparison below has now been rerun on the new clock and its conclusion survives: the 101 confirm at 36.6 percent against 40.4 for the other 1,472, a gap of -3.7 points at z = -0.74, so the collision criterion still selects nothing. Both rates roughly doubled with the better clock. Full rebuild: watermelon-metronome-clock.

The short version. The 101 cymbal strokes flagged for colliding with a tom confirm against the cymbal stem at 19.8 percent. Every other cymbal note in the tab confirms at 19.3 percent. The collision criterion selected nothing. The claim that followed, that the whole 1,573-note cymbal lane runs at only 1.46 times chance on its own stem, is withdrawn: on the metronome clock the same notes reach 3.17 times. The lane scores in that session were snare 6.89, kick 5.21 and toms 7.71 through identical machinery, and the cymbal gap against them was the clock, not the notation.

Corrected 2026-09-08 by the leakage gate. The sentence above about the lane running at 1.46 times chance is a statement about the DETECTOR, never about the notation. On the 865 cleanest cymbals in the song, those with no other drum within 50 ms, this detector recovers only 14.9 percent against a 13.3 percent floor, which is 1.12 times. It cannot see this instrument in this recording. Nothing about whether the cymbal notation is correct follows from the 1.46 figure, and no cymbal note can be removed on it.

A second result cuts against the repair list. All 49 sub-sixteenth tom positions sit a median of 15.4 ms from a tom-stem onset and 81.8 ms from the sixteenth grid, measured in bars where the clock is independently accurate to about 16 ms. Snapping them to sixteenths would move 49 notes away from the audio.

The governing hierarchy

Stem event first, instrument identity second, score timing third, Guitar Pro lane last.

Every number below follows that order. No verdict on this page uses a hand-availability argument, and no verdict uses a chart lane to decide which drum was struck. The protocol was written to disk and hashed with none of the 101 yet scored, so the thresholds could not be tuned to the answer.

Pre-registration SHA-256 3c785296 7a669198 06a81dde 02212e50 76ad0737 98d74dbd 7ba43f12 51e63557

First, the clock had to be earned

The alignment in hand was fitted on the original tab. This pass runs on the copy tab carrying your ear edits, so reusing that clock needed proof rather than an assumption. Both files hold 105 bars, 472 quarter notes, one tempo automation at 56 bpm, zero meter disagreements, and a maximum bar-start difference of 0.0000 ms. The clock is the same object in both files.

The map itself is anchored on 97 snare matches. Cymbals play no part in building it, which is what keeps this pass from grading the cymbal lane against a ruler the cymbal lane helped carve. Scoring is restricted to the anchor span, 59.33 s to 506.08 s, which is 82 percent of the song. Anything outside is marked not scored and never counted as absent.

The machinery works, proven on three other lanes

Same detector, same clock, same tolerance, same one-to-one matching for every row. Chance is measured by drawing 20,000 random timestamps inside the span and running them through the identical procedure.

Notated laneScored againstNotesStem onsets ConfirmChanceRatioReading
Tomtoms stem1688670.7020.091 7.71×positive control, strong
Snaresnare stem3426590.4770.069 6.89×positive control, strong
Kickkick stem5048600.4480.086 5.21×positive control, independent band
Snarecymbals stem34212860.2720.133 2.05×cross-lane leakage, expected
Cymbalcymbals stem15731286 0.1930.1331.46× (superseded: 3.17×) its own stem, barely above chance
Cymbalsnare stem15736590.0910.069 1.31×near null
Cymbalbass stem157322160.2030.219 0.93×negative control, correctly null

Superseded: the cymbal figure in this paragraph is 3.17 on the metronome clock.

Three lanes clear five times chance on their own stems. The cymbal lane sits at 1.46 on its own stem and 0.93 on an unrelated one. This replicates the earlier two-way page through a stricter method, since one-to-one matching stops a single loud crash from confirming a run of written notes.

It is not an alignment artifact

If the clock were smearing cymbal hits, widening the window would recover them. It does not. The ratio peaks at the pre-registered 25 ms and decays in both directions, which is the shape of a lane that has no signal to find rather than a lane that is merely mistimed.

ToleranceConfirmChanceRatio
10 ms0.0650.0581.13×
15 ms0.1210.0861.40×
25 ms0.1930.1331.46×
40 ms0.2600.1831.42×
60 ms0.3110.2381.31×
80 ms0.3530.2981.18×
120 ms0.4410.4171.06×

The wrong-recording control, run after the spec demanded it

The clock was inherited and proved identical across both score files, and that says nothing about whether it maps onto this recording. The spec requires a deliberately incorrect recording that preserves nuisance structure and breaks the correspondence. Watermelon's notated events were scored, through the Watermelon clock, against Keep It Greasey, a different Zappa performance run through the same Moises separator, 501.84 s against 545.27 s.

Notated lanenRight recordingWrong recordingSeparationVerdict
Tom1687.71×1.36×5.67×separates
Snare3426.89×0.78×8.86×separates
Kick5045.21×0.70×7.49×separates
Cymbal15731.46×1.00× 1.45× superseded: 3.00×weak
now SEPARATES

The clock is doing real work. Three lanes collapse to 1.36, 0.78 and 0.70 against the wrong performance, from 7.71, 6.89 and 5.21 against the right one. An alignment that matched anything rhythmic would not behave that way, so the map is specific to this recording.

Superseded. The paragraph that follows reasons from the 1.45× separation, which the metronome clock replaces with 3.00×. Its conclusion that the lane cannot promote an individual edit no longer follows from the number it cites.

This sharpens the cymbal reading rather than killing it. The wrong recording returns the cymbal lane at exactly 1.00×, a clean null, and its own recording returns 1.46×. Some cymbal notation is genuinely supported by this stem. The separation of 1.45× sits under the 1.5× floor, so the lane characterises well and still cannot promote an individual edit. Written into data/wrong_recording.json.

The bleed control, which decides whether any of this counts

The 101 are tom-coincident by construction. If a tom transient leaks into the cymbal stem, every one of them confirms for the wrong reason and the pass is worthless. So the control measures notated tom onsets that carry no notated cymbal within the tolerance, scored against the cymbal stem by the same procedure.

65
toms with no cymbal written
9.2%
confirm rate
0.69×
versus chance, below it
2.15×
separation from the 101

A lone tom hit produces a cymbal-stem confirmation less often than a random timestamp does. The separation is clean and the source separator earned its keep. The pass is measuring cymbals.

The 101, and why they turned out not to be a group

101
colliding strokes, exact match
20
confirmed
80
absent
1
ambiguous

Reproduction first. Applying the audit's own rule to the baseline file returns 24 measures and 106 colliding slots. Dropping the three measures whose cymbal voice does not fill the bar removes exactly 5 slots and leaves 21 measures and 101 collisions, with the sub-sixteenth tom count landing on 41 independently. The set is the same set.

The comparison that decides it. The 101 confirm at 19.8 percent. The other 1,472 cymbal notes confirm at 19.3 percent. A difference of half a percentage point on 101 events is nothing. Colliding with a tom does not predict whether the cymbal stem carries the stroke, so the collision list was never a list of suspect notes. The list sampled an evenly weak lane.

Index 56, display bar 57, the one you flagged first

Eleven toms with eleven coincident cymbal strokes, checked one event against one audio event.

SlotCymbal writtenStem timeVerdictTom at that slot
4Ride (middle)310.825ABSENTHigh Tom (48)
8Ride (middle)311.908ABSENTHigh Tom (48)
9Ride (middle)312.179CONFIRMEDHigh Tom (48)
10Ride (middle)312.450ABSENTHigh Tom (48)
11Ride (middle)312.721CONFIRMEDHigh Tom (48)
12Ride (middle)312.992ABSENTHigh Tom (48)
13Ride (middle)313.263ABSENTHigh Tom (48)
14Ride (middle)313.534ABSENTHigh Tom (48)
15Ride (middle)313.805ABSENTHigh Tom (48)
16Ride (middle)314.076CONFIRMEDHigh Tom (48)
19Ride (middle)314.889ABSENTVery Low Tom (43)

Three of eleven confirm, which is 27 percent against a 13.3 percent floor on a sample of eleven. That is one or two events above chance and it settles nothing on its own. The bar is worth opening for the tom reason below, and the cymbal verdicts here stay in the queue.

Why these are candidates and not commands

With confirmation at 19.3 percent against a 13.3 percent floor, roughly a third of any single CONFIRMED is signal and the rest is coincidence. That is enough to characterise a lane of 1,573 notes and it is not enough to license deleting one note. Per-event cymbal verdicts on this song are investigation queue entries. The same machinery on toms, snare and kick clears five times chance, so per-event verdicts there would carry real weight.

What the page therefore refuses to do. No cymbal note is removed. No cymbal note is added. The 101 verdicts are published as a queue with their timestamps so any one of them can be opened against the audio. The earlier framing said a hand has to leave the cymbal, and that argument is retired here because the cymbal stem can answer the question directly and did.

The sub-sixteenth toms, which the audio defends

The repair list proposed pulling 41 fractional tom positions onto the sixteenth grid. The tom stem scores 7.71 times chance, so it has the standing to arbitrate. All 49 fractional tom notes in the file were scored.

49 / 49
closer to the written fractional position
0 / 49
closer to the sixteenth grid
15.4 ms
median distance to fractional
81.8 ms
median distance to grid

Closing the circularity

Those fractional positions were generated from raw stem onsets, so matching them back to stem onsets proves provenance and cannot by itself prove the drummer played off the grid. The control that breaks it is the tom notes written on the grid, which were never derived that way.

PopulationnMedian distance to nearest tom onsetWithin 25 ms
Tom notes written ON the sixteenth grid11916.4 ms65%
Tom notes written OFF the grid4915.4 ms84%
Snare in the 17 bars holding off-grid toms6116.9 ms64%
Snare in every other bar28111.6 ms63%

The clock lands within about 16 ms in exactly the bars under suspicion, measured two independent ways. The grid sits a median 68.1 ms from the fractional position, which is four times the clock's own error. Snapping those 49 notes to sixteenths would move each one roughly four clock-errors away from the onset the tom stem records. The regrid is contraindicated and the item belongs in the queue as a per-fill question about tuplets and odd meters.

Relative tom height, measured ahead of any MIDI name

Post-transient resonance peak between 60 and 400 Hz on the isolated tom stem, 20 ms after the attack over a 120 ms window. FFT bin resolution is 5.38 Hz, so differences under about two bins carry no weight. Ordering is the claim. Absolute drum identity is not.

Display bar 25 confirms the ear edit

SlotWrittenMIDIResonance peakCentroidRMS
12High Tom48129.2 Hz153.10.0166
13High Tom48129.2 Hz158.40.0143
14High Tom48129.2 Hz161.00.0167
15Mid Tom4796.9 Hz144.20.0127
16Mid Tom47102.3 Hz150.30.0148
17Mid Tom4786.1 Hz122.10.0146
18Mid Tom4786.1 Hz132.70.0129
19Low Floor Tom4180.7 Hz127.00.0116

19 of 19 pairwise orderings agree. The written descent matches the measured descent at every comparison, running 129.2 Hz down to 80.7 Hz. Your predicted figures were 129 to 133 Hz for the first event and 85 to 102 Hz for the second group, and the stem returns 129.2 and 86.1 to 102.3. The hand correction holds on audio evidence, with the direction certain and the exact drum names still open.

Display bar 57: unresolved, and below the resolution floor

SlotWrittenMIDIResonance peakRMSReading
4High Tom4891.5 Hz0.0180one drum
8High Tom4886.1 Hz0.0166one drum
9High Tom4891.5 Hz0.0182one drum
10High Tom4891.5 Hz0.0163one drum
11High Tom4886.1 Hz0.0126decaying
12High Tom4886.1 Hz0.0089decaying
13High Tom4886.1 Hz0.0079decaying
14High Tom4886.1 Hz0.0070decaying
15High Tom4886.1 Hz0.0073decaying
16High Tom4886.1 Hz0.0067decaying
19Very Low Tom43113.0 Hz0.0174 higher, and a fresh stroke

WITHDRAWN 2026-09-08, same day. This bar is UNRESOLVED, and neither side of it is a finding.

The measurement is withdrawn on its own terms. I first read 0 of 10 order agreement and called the fill backwards, on a measured 113.0 Hz final stroke against 86 to 91 Hz for the ten before it. That claim does not survive its own instrument. The repeated 86.1 Hz across six consecutive strokes is a one-bin reading at 5.38 Hz resolution, which is the signature of a tracker locking onto a single resonance, and a separated tom stem makes that worse. A single-F0 read cannot support a direction claim under those conditions, and it certainly cannot resolve a stroke that may be more than one drum.

The chart cannot settle it either, and saying so is the point. I cropped chart bar 48 and read a shape there. That read is not reported as a finding. This scan measures 5.0 px per staff space against a 15 px floor for notehead work, already recorded as q-2026-09-06-c45c11, which marked Watermelon lane counts blocked on resolution and asked for a scan at roughly three times this one. A notehead count taken below that floor is exactly what the floor exists to reject, and my own crop does not get an exemption for being mine.

What actually survives on this bar. Ten strokes hold a flat resonance near 86 to 91 Hz with a clean rms decay from 0.0180 to 0.0067, which reads as one drum through a decrescendo. That is a loudness contour, and loudness does not depend on the F0 estimate that failed. The eleventh stroke is unresolved.

Standing state: bar 57 waits on a higher-resolution scan. No edit is proposed for it, no drum is named, and no notehead is counted from this page image.

The snare discrepancy, reconciled

Two runs reported 154 chart heads against 193 tab snares, and 124 chart heads against 340 tab events. Both are correct and they count different things on both sides.

SideNumberWhat it actually counts
Tab193Plain, non-ghost snare instances. Identical in both revisions.
Tab342All snare instances in r8968524, which is 193 plain plus 149 restored ghosts. The quoted 340 sits two off this.
Tab193Total in the pre-sweep original, which carries zero ghosts, so the two definitions collapse there.
Chart154Snare-lane heads from the erosion reader with the ink cut at 180 or above.
Chart83 / 136 / 137Three earlier reader passes held on this disk, same page images.
Chart124A parallel session's reader pass. Not present on this disk, so it cannot be re-derived here.

Neither side holds the same quantity across the two comparisons. Until a comparison names its revision, its ghost rule, its bar range and its reader pass, the gap between chart and tab carries no information about what the drummer played. One chart image supports four different head counts on this machine alone, which is a reason to distrust the reader in dense passages and to re-read from the stem.

Applying the Perfect Stem Read spec, which found one more defect

The governing spec arrived after this pass and is now installed as /perfect-stem-read. It requires a snare count to declare its revision, measure range, voices, ghost policy, grace policy, tie and duplicate handling, event definition and reader version before the number supports any claim. Declaring those fields surfaced something the earlier reconciliation missed.

FieldPRESWEEP r7715683BASELINE r8968524
Artifact SHA-256, first 16687445e3371131fd4376b4a39dd1a466
Track8, Vinnie Colaiuta8, Vinnie Colaiuta
Measure rangeall 105 barsall 105 bars
Voices[0][0, 1]
Event definitionnote instance, never a Note definition id
MIDI counted4040
Total instances193342
Plain / ghost193 / 0193 / 149
Grace notes00
Distinct sixteenth positions193293
Positions carrying two notes049

The 342 occupy 293 positions, and all 49 doubled positions share one pattern. Every one is a plain snare in voice 0 stacked with a ghost snare in voice 1 at the identical bar and sixteenth slot. The pattern is unanimous across all 49, with no other combination appearing.

A drummer cannot strike one snare loudly and quietly at the same instant. These are 49 notation collisions the ghost restore introduced, and they are a separate defect from anything the cymbal pass measured. Written into data/snare_duplicates.json and data/snare_scope_full.json. No edit is proposed here, since the restore's provenance decides this rather than audio.

The leakage gate, and the number that reframes the whole page

The spec requires more than one bleed control: target and competing transient energy, target and competing template similarity, and the detector's firing rate through known target-silent passages, all calibrated from confirmed events inside this recording. Running it changed what the cymbal figures mean.

Templates built from this recording only

An isolated event is one with no other drum notated within 50 ms. That gives 865 isolated cymbals and 59 isolated toms. The cymbal template is what the cymbal stem looks like on an isolated cymbal. The bleed template is what the same stem looks like when a tom sounds and no cymbal is written. The margin below is similarity to the cymbal template minus similarity to the bleed template.

PopulationnMargin medianCymbal-stem energyTom-stem energy
Isolated cymbal (target)400+0.0078168.10.2
Isolated tom (bleed signature)59−0.007187.6182.7
The 101, all together101−0.0038148.2154.4

A tom alone puts 87.6 of energy into the cymbal stem against 168.1 for a real isolated cymbal, so this separation leaks roughly half a cymbal's worth of energy on every tom hit. That is why the gate was necessary.

The two routes corroborate each other

Subset of the 101nMargin p25Medianp75Reads as
Onset CONFIRMED20−0.0051+0.0131+0.0148cymbal, above the isolated-cymbal median
Onset ABSENT80−0.0125−0.0058+0.0008near the tom-bleed median

Mann-Whitney, CONFIRMED above ABSENT, p = 0.0001. Onset detection and spectral shape are independent measurements and they agree. The 20 confirmed strokes are real cymbal, supported twice.

The recall number, which is the important one

865
cymbals with no other drum within 50 ms
14.9%
of those the detector confirms
1.12×
versus the 13.3% chance floor
85%
miss rate on known-good cymbals

The cleanest cymbals score WORSE than the tom-coincident ones. Isolated cymbals reach 1.12×, the whole lane 1.46×, the 101 1.49×. A detector that finds genuine cymbals barely above chance in the easiest possible conditions is not measuring the notation. It is failing to see a ride pattern inside its own resonant bed, which is the exact difficulty the spec names for broadband cymbal textures.

So ABSENT carries no information and never licenses a removal. Eighty-five percent of cymbals that are known good by isolation come back ABSENT. Applying that verdict as a repair instruction would delete most of a correctly notated lane. Every one of the 101 stays.

Detector rate through notation-silent passages

Only four stretches run 1.5 s or longer with no notated cymbal, totalling 19.4 s, because the notation is nearly continuous. The detector fires at 0.98/s inside them against 2.96/s elsewhere, a ratio of 0.33. Notation and stem agree at that coarse level, and the sample is four passages, so it carries little weight on its own.

Building a better detector, and proving why it hits a ceiling

The recall failure above could be a tuning failure, so it was worth attacking directly. Five onset functions were tried on the cymbal stem: plain spectral flux, SuperFlux (flux against a frequency-max-filtered lagged frame, which suppresses a ringing decay), adaptive bed subtraction, complex-domain deviation and its rectified form. Phase-aware methods were included because a fresh stick attack breaks phase continuity even while the cymbal keeps ringing. Parameters were tuned on 432 odd-indexed exemplars and reported on the 433 even-indexed holdout.

DetectorHoldout recallChanceRatio
Baseline, plain flux 4-16 kHz0.2630.2201.20×
SuperFlux on a bed-subtracted spectrum0.1990.1241.60×
Complex-domain deviation topped out at 1.72× on tune, SuperFlux alone at 1.65×, bed-residual energy at 0.80×.

A real 1.34× improvement on held-out data, and the 3× target is not met. Five independent onset functions across five frequency bands and every threshold all land between 1.2× and 1.7×. That flatness is the result, since a tuning problem does not resist five different methods equally.

The offset sweep says the lane is unidentifiable, and the snare says the clock is fine

Global shiftCymbal ratioSnare ratio (control)
−100 ms0.73×3.07×
−50 ms0.99×4.85×
0 ms1.64×6.89×
+50 ms0.73×4.59×
+100 ms0.81×3.26×
+275 ms2.20× (its best)—

The snare peaks cleanly at zero and falls off symmetrically. That is what a correct alignment looks like, and it confirms the clock once more.

The cymbal lane has no peak at zero. Its best bump sits at +275 ms, which is 1.03 sixteenth notes at this tempo, with bumps of similar height at −250 and +300. 93.0 percent of written cymbal intervals fall within 10 percent of one sixteenth, median 271.2 ms against a 267.9 ms sixteenth.

A lane written on nearly every sixteenth matches itself one sixteenth over, so signal and null have the same shape and no offset is identifiable. Onset matching cannot validate a continuous sixteenth-note ride. That is a property of the method against this material, never a verdict on the notation, and it is why the snare works at 6.89× while the cymbal cannot be scored at all. Written into data/ridebed_final.json and data/ridebed3.json.

The approach that does work, and what it found

Per-event matching is unidentifiable on this lane, so the question changed. Ask whether the ride's periodicity matches the stem, over 6-second windows stepped by 2 seconds, with the same Keep It Greasey wrong recording as control.

RecordingMedian lag / notated spacingWindows within 15% of 1.0Median autocorrelation
Watermelon (right)1.97136 of 2160.217
Keep It Greasey (control)0.81415 of 2160.252

The stem's dominant pulse sits at almost exactly twice the notated ride spacing, which is 271.0 ms, so the envelope pulses at the eighth while the tab writes sixteenths. Separation against the wrong recording is 2.40×.

The obvious explanation fails its own test

If the drummer played eighths and the tab wrote sixteenths, the off-eighth notes would be inventions. Splitting purely on score position, with no reference to audio, refutes that.

PositionnConfirmedRecallRatio
On the eighth785211211/785 = 0.2692.17×
Off-eighth sixteenth736151151/736 = 0.2051.66×

Only 1.31× apart, Fisher p = 0.0021. Real and far too small for fabrication. The off-eighth sixteenths carry genuine support at 1.66×, so the drummer played the sixteenths.

What it actually is: an accent grid, and the original author wrote it down

A sixteenth ride with every other stroke accented pulses at the eighth in an envelope and still puts a real attack on every sixteenth. Both results then agree. The pre-sweep tab r7715683 encodes exactly that, marking 1,317 of its 1,778 ride notes with AntiAccent. Splitting on that flag alone, with no reference to audio:

Author's markingnConfirmedRecallRatio
PLAIN, the author's accents416122122/416 = 0.2932.37×
GHOSTED, the author's weak strokes1185240240/1185 = 0.2031.64×

1.45× apart, Fisher p = 0.00012. The notes the transcriber marked as accented are measurably louder in the isolated cymbal stem than the ones marked weak, on a split made from a notation flag with the audio never consulted.

Three independent splits, all significant, all in the same direction: envelope periodicity at 1.971, score position at 1.31× (p = 0.0021), author's flag at 1.45× (p = 0.00012). The modest effect sizes are what a detector with 14.9 percent recall can deliver, since poor recall caps how far any split can separate.

The consequence for the tab. Those 1,317 ride ghost flags encode an accent structure the audio independently supports, and the current copy tab r8968524 carries zero cymbal ghosts against the pre-sweep tab's 1,317. The accent grid has been lost from the working file. This is a provenance repair with audio backing, and it is the strongest actionable result on this page. Data: beat_periodicity.json, eighths_test.json, accent_grid.json, g44_flag_parity.json.

The queue this produces

  1. 101 cymbal strokes with timestamps and verdicts, opened individually, never removed in bulk.
  2. Display bar 57 is UNRESOLVED. The measurement failed on bin-lock and the chart sits below the 15 px notehead floor. It waits on a scan at roughly three times this resolution.
  3. 49 fractional tom positions examined per fill for tuplets and odd meters, with the regrid withdrawn.
  4. Restore the 1,317 ride ghost flags to the copy tab. The accent grid they encode is confirmed by the stem at p = 0.00012 and the working file carries zero cymbal ghosts.
  5. The chart reader, four head counts from one image, re-read from the stem ahead of grading anything.