cent-offset tuning card · index card with a stamped header

Compare Measured Pitch Ratios in Cents Against a Stated Reference Shift

Hertz differences do not describe equal pitch steps across a range. Use the frequency ratio, keep its signed cents difference, and compare it with your stated reference shift without a musical-quality verdict.

1 · Tone code | reference frequency Hz | observed frequency Hz

FIRST-LOAD

HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.

Data note: This cent-offset tuning card calculates in the tab from Tone code | reference frequency Hz | observed frequency Hz. No input-collection endpoint, AI request or file upload is built into it. Drafts may be saved locally; explicit input-state links and optional external formatting can disclose the records. Use non-sensitive codes and clear the draft when finished.

Perspective: Before: raw hertz differences looked like comparable tuning errors. After: signed frequency-ratio cents and the intentional reference shift have separate, explicit roles.

2 · Read the cent-offset tuning card

Supplied-frequency arithmetic only: no audio analysis, device calibration, performance judgment or universal tuning prescription. Confirm harmonic/reference conventions and any consequential adjustment with an appropriate music teacher or tuner technician.

Paid layer: cent-offset tuning card filing layer

one-time step · the free reading above stays complete

hidden patterns detected after your first run

Free tier

one full, unwatermarked cent-offset tuning card App execution
three invented readings and unlimited calculations in the paired article demo
copy the complete working and boundary; voluntarily share non-sensitive input state

What $4 one-time adds

subsequent cent-offset tuning card App calculations through a browser-local convenience signal
boundary-preserving print and row-and-summary CSV of this cent-offset tuning card; conditional retyping budget uses only your entered minutes
five local headline/count/time summaries, separately deletable; full-input draft is separate and not a backup

HYPOTHESIS / PROTOTYPE: the proposed $4 one-time price concerns filing this cent-offset tuning card, not obtaining its answer. No checkout is available. An optional manual-retyping baseline computes a conditional one-export retyping budget; preparation, review, measured savings and buyer demand are not implied.

Local history (this device)

No saved runs yet — your first run files here.

Filing prototype — checkout unavailable

Checkout is unavailable. Browser-local, profile-scoped convenience gating is best-effort, not server-verified access. A URL or browser flag is not proof of payment. Clearing browser data removes local state; no account or cross-device recovery is provided.

Optional filing controls are a local prototype.

Checkout is unavailable. The reading above is complete; print, CSV and five local summaries are optional enhancements, not hidden answers.

Before using the cent-offset tuning card

Use non-sensitive tone codes and positive finite reference/observed frequencies from the same intended tone and measurement convention. This card has no microphone access, audio upload or pitch tracker; it accepts numbers supplied by you. Cents define a logarithmic ratio scale with 1,200 cents per octave, not a mandate that every performance use equal temperament. The target shift is a deliberate reference offset in cents, applied to every row. It does not alter the measurements. Instrument, style, temperament, harmonic selection and device accuracy matter, so do not convert a precise-looking mismatch into a compulsory adjustment or a judgment of a musician.

Boundary and sources

Declared local method: Calculate signed difference as 1,200 times log base two of observed divided by reference. Subtract the shared target shift to obtain signed mismatch. The headline is the largest absolute mismatch, while each row retains its sign, measured ratio and reference convention. Do not add row cents as though they were durations or ordinary frequency changes. The calculation does not wrap octaves or label the largest mismatch as a performance failure.
Every sample code, measurement, date, price, fingerprint and scenario is invented. Artifact checks do not verify reader data, policies, actual files, tickets, votes or health/accessibility outcomes.
Google’s official Gemini pricing page, fetched 2026-10-01, lists AI Studio access in its Free section, limited model access and free input/output tokens. Free-tier content may be used to improve products. Optional external formatting may require an account; limits/access can change. Manual local entry needs none. Do not send sensitive records.

Mechanism: competence-autonomy-loop

Optional AI formatting, never the calculation

Manual entry completes this cent-offset tuning card for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.

Format only these fictional or non-sensitive notes for a cent-offset tuning card. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string"]}], "setting": "string"}. The columns are Tone code | reference frequency Hz | observed frequency Hz; the setting is Target shift from the reference (cents). Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.

An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.