Pitch, scales, and harmony

Pythagorean Tuning Calculator

Generate Pythagorean interval frequencies and cents from a selected tonic.

PrivacyRuns in your browser
OutputTuning generator
CostFree to use
Tuning generator

Enter pitch and harmony values

Keep reference pitch, spelling, key, and octave conventions attached to the entries.

Root note for the generated scale.

Frequency assigned to the tonic.

Generate by ascending fifths or descending fourths.

Ready to calculate

The pitch or harmony result will appear here with supporting details.

What this calculator answers

Generate Pythagorean interval frequencies and cents from a selected tonic.

Pythagorean Tuning Calculator addresses one defined pitch or harmony relationship. Generate octave-reduced 3:2 ratios and frequencies. Identify the sounding note, written spelling, key, chord, or tuning system represented by the inputs before comparing alternatives within a reproducible pythagorean tuning workflow.

For this pythagorean tuning case, keep the reference and the musical noun visible. Hertz, cents, semitones, scale degrees, chord symbols, and interval names describe different layers and cannot be exchanged merely because two displayed numbers match before accepting the pythagorean tuning output.

Inputs and notation conventions

The input record runs from Tonic through Circle direction. Capture those values from one score, tuning session, analysis, or arrangement version as part of the saved pythagorean tuning record.

  • Tonic: Root note for the generated scale.
  • Tonic frequency: Frequency assigned to the tonic.
  • Circle direction: Generate by ascending fifths or descending fourths.

Read the fields together. A valid Tonic paired with Circle direction from another case can yield flawless arithmetic for the wrong note or harmony.

A reproducible example

The default case begins with Tonic = C, Tonic frequency = 261.6256, Circle direction = fifths. Calculate it unchanged and record the pythagorean scale. Then adjust one field and explain the difference before changing a second input when checking pythagorean tuning.

This sample demonstrates the calculation path, not a preferred tuning, key, chord, or notation choice within a reproducible pythagorean tuning workflow. Substitute the values from the real musical source before carrying the output into a score, session, or arrangement before accepting the pythagorean tuning output.

From entries to pitch result

Generate octave-reduced 3:2 ratios and frequencies. The result panel retains supporting values so the headline can be inspected instead of accepted without context as part of the saved pythagorean tuning record.

Generate Pythagorean interval frequencies and cents from a selected tonic.

Carry frequency and ratio calculations at full precision, then round the display when checking pythagorean tuning. Preserve written accidentals and key context through notation calculations; respelling every pitch with sharps can erase the interval or chord function being analyzed within a reproducible pythagorean tuning workflow.

When octaves or inversions appear, distinguish pitch class from register before accepting the pythagorean tuning output. C4 and C5 share a pitch class but differ by an octave, while C–E–G and E–G–C contain the same triad with a different bass in a documented pythagorean tuning test.

Interpreting the displayed notes

The primary output is pythagorean scale. Read it beside Tonic, Circle direction, and the named tuning or key convention. A pitch can be numerically accurate while its enharmonic spelling is unsuitable for the harmonic context as part of the saved pythagorean tuning record.

Compare the component values as well as the headline when checking pythagorean tuning. If a changed Circle direction produces an unexpected pitch direction, scale degree, or chord function, restore the default and check sign, octave, ratio order, and key selection.

Independent verification

Compare octave endpoints first. An EDO table should double frequency after its full number of steps; octave-reduced rational tuning should keep every displayed pitch within one octave of the tonic.

  • Verify the tuning reference or tonic before examining small differences within a reproducible pythagorean tuning workflow.
  • Keep interval direction and ratio order explicit.
  • Distinguish a sounding pitch class from its written spelling before accepting the pythagorean tuning output.
  • Check octave placement separately from chord or scale identity as part of the saved pythagorean tuning record.

A neighboring calculation is available in the Just Intonation Interval Calculator. It answers a related question but should not be expected to return the same output noun when checking pythagorean tuning.

Temperament and tuning basis

Equal temperament, just intonation, and Pythagorean tuning distribute pitch differently. A result is meaningful only when its octave division, generating ratio, root frequency, and reference pitch remain attached.

For Pythagorean Tuning Calculator, name the invariant before changing Tonic or Circle direction. A comparison is meaningful only when the underlying pitch, function, or tuning basis remains defined within a reproducible pythagorean tuning workflow.

Build three controlled cases: the published default, a nearby musical value, and a boundary such as unison, octave, chromatic alteration, or range edge before accepting the pythagorean tuning output. Record the result unit and spelling for every case as part of the saved pythagorean tuning record.

Limits of the model

Pythagorean Tuning Calculator models only the entered relationship. It does not determine preferred voicing, stylistic intonation, readable engraving, performer comfort, or whether a theoretical substitution sounds appropriate in the arrangement when checking pythagorean tuning.

Use the output as transparent analysis. Audition important tuning and voicing choices, review written spellings in their key, and resolve material disagreements at the source rather than forcing the displayed answer to match an expectation within a reproducible pythagorean tuning workflow.

What the Pythagorean Tuning numbers describe

The central idea is that successive 3:2 generators are folded into one octave. That principle gives the displayed pythagorean scale its meaning and explains why a similar-looking number from another tuning, key, octave, or spelling system may answer a different question.

One dependable reference is this: Pythagorean thirds differ from pure 5-limit thirds. Enter that case before exploring unusual material and save the supporting values beside the headline before relying on this pythagorean tuning result. A failed reference case usually points to a sign, octave, root, ratio-order, or convention error rather than a subtle musical disagreement in the saved notes for pythagorean tuning.

Another important observation is that circle direction changes the spelling path. Change Tonic while holding Circle direction steady, then reverse the experiment. The two trials separate the influence of the source value from the influence of the selected frame of reference when reviewing pythagorean tuning.

Interpretation still matters because tonic frequency scales every generated pitch. This page reports a defined relationship, but the surrounding score, recording, instrument, or arrangement determines whether that relationship has been named and applied appropriately in a documented pythagorean tuning test.

Testing this result away from the default

Begin with the published defaults, then create one ordinary comparison and one edge case before relying on this pythagorean tuning result. Write down Tonic, Circle direction, pythagorean scale, and the direction of change. That record is easier to inspect than a screenshot of the headline alone in the saved notes for pythagorean tuning.

Listen to the result or read it back in notation after the arithmetic check when reviewing pythagorean tuning. In a pythagorean tuning task, consistent arithmetic can still be awkward when an accidental obscures function, an octave is unsuitable, or a voicing conflicts with a real part. Musical judgment should stay visible instead of being disguised as extra decimal precision in a documented pythagorean tuning test.

Reproducible work retains the source passage, tuning reference, key or tonic, and notation preference along with the inputs before relying on this pythagorean tuning result. Recalculate after the source changes. Manually editing an old pythagorean scale breaks the connection between the answer and the values that produced it.

Questions about the notation

What does Pythagorean Tuning Calculator return?

It returns pythagorean scale from the entered Tonic and Circle direction. Generate octave-reduced 3:2 ratios and frequencies.

How can I check the pythagorean scale?

Rebuild a simple unison or octave case when possible, then change only Circle direction. Confirm that the output moves in the direction predicted by that field before accepting the pythagorean tuning output.

Why can an enharmonic or tuning result look different elsewhere as part of the saved pythagorean tuning record.

Another source may prefer flats instead of sharps, use a different concert pitch, select another temperament, or label octaves differently when checking pythagorean tuning. Compare conventions before treating the values as contradictory within a reproducible pythagorean tuning workflow.

Should I save the inputs with the Pythagorean Tuning result?

Yes. Retain Tonic, Circle direction, the calculator name, and any key, octave, tuning, or spelling assumption needed to reproduce the result.