Resources← Back to the neck

Resources / Theory / Turkish makam vs Arabic maqam

Turkish makam vs Arabic maqam

Related traditions, commonly conflated, materially different. An app that merges them produces a system that belongs to neither.

Summary of differences

TurkishArabic
Theoretical division53 commas24 quarter-tones (notational)
Building blocksçeşni (üçlü/dörtlü/beşli)ajnas
Melodic pathseyirsayr
Rhythm cyclesusûliqa'
Reference pitchrast conventionally written as Gvaries; often C or D
NotationAEU, 10 accidentalshalf-flat/half-sharp, 4 accidentals
TranspositionInstruments notated transposed (ahenk system)Generally at pitch
Institutional theoryCodified (Arel–Ezgi–Uzdilek, 20th c.)Less centrally codified

The pitch difference is audible

Established The clearest case is the neutral third in Rast.

A 35-cent gap between the two traditions is well above the threshold of perception — roughly a third of a semitone. Turkish Rast leans toward the Western major third; Egyptian Rast sits noticeably lower and flatter.

Practice Real performance in both traditions varies around these figures, and Arabic practice varies more, because Arabic notation is more explicitly an approximation.

Regional variation within Arabic practice

Established Egyptian, Syrian/Aleppine, Iraqi, and Turkish-influenced Ottoman Arabic practices differ in the tuning of the neutral degrees. Aleppo is generally described as preserving a more Ottoman-inflected intonation; Egyptian practice is often described as flatter in the neutral pitches.

Uncertain Precise measured figures per region — I have not verified specific cent values from measurement studies and should not invent them. This is a research task before the app can claim regional variants (see 07-research/open-questions.md).

The transposition trap

Established Turkish notation uses a transposing convention. The perde rast is written as G regardless of the instrument's actual sounding pitch, and the ahenk (pitch level) determines where that actually sounds. Different instruments and different ahenk names shift the sounding pitch substantially.

Consequence for the app: written pitch and sounding pitch must be separate fields. This already caused confusion in the tuning research — Turkish sources give the classical oud as Fa♯–Si–Mi–La–Re–Sol, which a tuner will read roughly a fourth lower. Both statements are correct; they're in different reference frames.

Shared repertoire, divergent readings

Roman/Romani and Balkan musicians move between these systems fluidly, and much of the Aegean and Thracian repertoire exists in both Turkish and Greek versions with different intonation. This is a feature of the music, not a problem to resolve — but it means "the correct tuning of this tune" is often not a well-formed question.

Design recommendation

Do not build a unified Makam record with one pitch set. Build:

Makam
  └── variants[]
        ├── turkish-aeu       (theory)
        ├── turkish-practice  (measured)
        ├── egyptian
        ├── syrian
        └── iraqi

Let the user A/B them. The difference between Turkish and Egyptian Rast, heard back to back on a drone, teaches more in ten seconds than a page of explanation.

Sources

Meshk uses privacy-respecting analytics (Google Analytics, proxied through this domain) to see which tunings, makams, and features people actually use. Read the privacy policy.