Chabad Torah Leining — Research Report for a Lein-Practice Tool

Date: 2026-11-17 · Scope: Torah only, Chabad (Lubavitch) trop, practice tool (pick a parsha/aliyah, hear it leined correctly in Chabad trop, follow along, repeat) · Research only — no building.

How this was made: four parallel research passes (taamim system, Chabad melody, text data, existing tools + pedagogy) plus direct verification of the voice-technology fork. Every claim below is sourced; where documentation is thin or only exists as recordings, that is stated plainly. The Chabad melody deep-dive (full write-up, motif transcription, sources) lives at ~/workspace/research/chabad-trop-research.md.


0. Bottom line


1. The taamim system from first principles

1.1 What the marks are — three jobs at once

Hebrew ta'amei ha-mikra (טַעֲמֵי־הַמִּקְרָא), singular ta'am = "taste / sense / reason", Yiddish trop, English "accents / trope symbols". Fixed in Tiberias by the Masoretes, 8th–10th c. CE, culminating in Aaron ben Moses ben Asher; the Aleppo Codex (c. 920) is the model text. The marks are not in the Torah scroll — the reader learns them from a printed text (tikkun/Chumash) and chants from memory. Unicode: U+0591–U+05AF, plus sof pasuq U+05C3 and paseq U+05C0.

Every mark does three things at once:

Function What it does
Syntax / punctuation Divides a verse into clauses and phrases, like commas, semicolons, full stops. Can affect exegesis — e.g. Isa. 40:3, where zakef katan on qore discourages the KJV grouping "voice crying in the wilderness".
Phonetics / stress Most marks sit on the consonant of the stressed syllable, showing milra (final-syllable stress) vs mil'el (penultimate). This also shows where the main note of the motif goes. A few always go on the first/last letter, for musical reasons or to disambiguate identical shapes.
Music Each mark stands for a short melodic motif (niggun / neginot in Hebrew, trop in Yiddish). Strung together they make the verse's chant.

Mechon Mamre warns the syntax tree is not a pure syntax tree: virtually every verse is split by etnachta even when that falls mid-sentence (Gen. 1:1, between verb/subject and object). Do not assume the parse is a pure grammar tree.

Scope note: this is the 21-book prose system. The 3 poetic books — Psalms, Proverbs, Job (Sifrei Emet, אמ״ת) — use a different system with different functions for many of the same-looking signs. For a Torah-only tool this doesn't matter, but don't reuse the Torah melody table for Tehillim.

1.2 Disjunctives vs conjunctives

Rule: in general each word has one mark. Exceptions: a maqqef-hyphenated group counts as one word (one mark for the group); a long word may carry two (a disjunctive on the stressed syllable plus the related conjunctive two syllables before, in place of meteg).

Disjunctives by level

Level Hebrew English Function
1 — Emperors סוֹף פָּסוּק sof pasuq; the accent on the last word is סִלּוּק silluq "end of verse" / "taking leave" Last word of every verse. Silluq is the accent; sof pasuq (׃) is the punctuation mark after it. Do not conflate them.
1 אֶתְנַחְתָּא etnachta / atnach "rest / pause" Divides verse into two halves (cola). At most once per verse; a very short verse may have none.
2 — Kings זָקֵף קָטָן zakef katan "small upright" Usual 2nd-level disjunctive; roughly comma/semicolon.
2 זָקֵף גָּדוֹל zakef gadol "great upright" Replaces zakef katan when it constitutes a phrase on its own; longer tune, stronger separation.
2 טִפְחָא tifcha (Seph. tarcha) "hand-breadth" Replaces zakef katan in the immediate neighbourhood of sof pasuk or etnachta — the "near companion" of the emperors.
2 סֶגוֹל segol / segolta "bunch of grapes" Stronger 2nd-level disjunctive, used in very long verses; only in first half of verse.
2 שַׁלְשֶׁלֶת shalshelet "chain" Replaces segol when it constitutes a phrase on its own. Only 4× in the Torah: Gen. 19:16, 24:12, 39:8; Lev. 8:23, always at verse beginning.
3 — Dukes רְבִיעַ revia / revi'i "fourth" Usual 3rd-level disjunctive.
3 זַרְקָא zarka "scatterer" Replaces revia in vicinity of segol; only ever before segol.
3 פַּשְׁטָא pashta "stretching out" Replaces revia in vicinity of zakef; precedes zakef katan. Same glyph as kadma (U+0599) — distinguished by placement: pashta on last letter (doubled if word is mil'el), kadma on stressed syllable. 5,429× in Torah.
3 יְתִיב yetiv "sitting" Replaces pashta/kadma when it constitutes a phrase on its own; always on first letter of word.
3 תְּבִיר tevir "broken / downward tumble" Replaces revia in vicinity of tifcha; precedes tifcha. Frequently paired with darga.
4 — Counts פָּזֵר pazer "lavish / strewn" Cluster near beginning of a long half-verse; elaborate realisation.
4 גֵּרֵשׁ geresh / azla-geresh "expulsion" See kadma v'azla below. Doubled unless on a non-finally-stressed word or following kadma.
4 גֵּרְשַׁיִם gershayim "double geresh" Replaces geresh when not preceded by azla AND word is stressed on last syllable.
4 תְּלִישָׁא גְדוֹלָה telisha gedola "great detached" Detached — never linked to following note as one musical phrase.
4 מֻנַּח לְגַרְמֵהּ munach legarmeh (+ paseq ׀) "munach by itself" Munach + paseq becomes a disjunctive, mainly before revia, occasionally before pazer.
4 קַרְנֵי פָרָה qarne farah "horns of a cow" Once in the Torah: Num. 35:5, preceded by yerach ben yomo.

Conjunctives ("servants", meshartim)

The general conjunctive is munach; which one appears depends on the following disjunctive:

Hebrew English Precedes (usual)
מֻנַּח munach "resting" General/default; before etnachta, zakef, segol, revia etc. Can repeat many times in a row.
מֵרְכָא mercha / ma'arikh "lengthener" Before sof pasuk and tifcha (occasionally tevir and other disjunctives). Note: misleadingly translated "comma" in modern usage — it is conjunctive; a comma marks a break.
מַהְפָּךְ mahpach "turning round" Before pashta. Cannot appear without a pashta (but pashta can appear without it).
דַּרְגָּא darga "stairstep" Before tevir. Before revia, the penultimate munach is always a darga.
קַדְמָא kadma "precede" Before geresh and some conjunctives; first member of kadma v'azla. Same glyph as pashta.
תְּלִישָׁא קְטַנָּה telisha ketana "small detached" Before some conjunctives; 3rd conjunctive before pashta in the pashta chain.
מֵרְכָא כְּפוּלָה mercha kefula "doubled mercha" Occasionally preceded by darga; function similar to tevir. Only 5× in Torah: Gen. 27:25, Ex. 5:15, Lev. 10:1, Num. 14:3, Num. 32:42. Disputed whether conjunctive or occasional replacement for tevir.
יֶרַח בֶּן יוֹמוֹ yerach ben yomo "day-old moon" Before qarne farah (once in Torah).

Count disagreement — flag: sources count differently. Iancu (2025) says the Ashkenazi system has 27 marks: 19 disjunctives + 8 servants. Wikipedia's table lists ~27 prose rows plus poetic-only rows. Any implementation should count codepoints, not "names", and treat pashta/kadma, geresh/azla, mahpach/yetiv as glyph collisions resolved by position/context, not by codepoint alone.

1.3 Hierarchy, domains, parsing a pasuk

The ruler model (Mechon Mamre — most formal source). Classes carry ruler titles: qeysar (emperor) terminates a whole verse and "reigns" it; a melekh (king) divides an emperor's realm; a mishne (duke) divides a king's realm; a shalish (officer) divides a duke's realm; lowest is mesharet (servant), a conjunctive. Exception: in the 21 books the first division is by an emperor, etnachta, dividing another emperor's realm (sof pasuk) — treat each half-verse (ending in sof pasuk or etnachta) as the top level, remembering sof pasuk divides stronger than etnachta.

Continuous dichotomy — how the tree is built. Start with a half-verse ending in an emperor → split by a king → each half split by a duke → each quarter split by an officer, etc. Key rules:

The companion table (Wikipedia "Sequences") — the last subdivision in a phrase must be a disjunctive one level down, chosen to fit the governing disjunctive (its "near companion"); other subdivisions are the "remote companion". A disjunctive constituting a phrase on its own may be substituted by a stronger disjunctive of the same level (the "equivalent isolated disjunctive").

Main disjunctive Preceding conjunctive(s) Near companion Remote companion Equivalent isolated
Sof pasuk Mercha Tifcha Zaqef katan —
Etnachta Munach Tifcha Zaqef katan —
Segol Munach Zarka Revia Shalshelet
Zaqef katan Munach Pashta Revia Zaqef gadol
Tifcha Mercha; Darga; Mercha-kefulah Tevir Revia —
Revia Munach; Darga Munach Munach legarmeh Geresh, Telisha gedola, Pazer —
Pashta Mahpach; Qadma Mahpach Geresh/Azla/Gershayim Telisha gedola, Pazer Yetiv
Tevir Mercha or Darga Geresh/Azla/Gershayim Telisha gedola, Pazer —
Geresh/Azla Qadma; Telisha qetannah — Gershayim —
Telisha gedola Munach — — —
Pazer Munach — — —
Qarne farah Yerach ben yomo — — —

1.4 How a pasuk's melody is built

Not fixed pitch notation. The marks are ideographic / neume-like: each stands for a short melodic motif / group of notes, not individual notes. Haïk-Vantoura's reconstruction treating signs as individual scale degrees is explicitly rejected by musicologists as at odds with all existing traditions.

Implementation consequence: model as syntax_tree (from marks) → phrase segmentation → motif lookup (mark, mode, phrase-length, final/non-final, isolated?) → note sequence, with the motif table supplied per tradition/mode from audio/transcription. The text alone does not encode pitches.

1.5 Formal rules that matter for implementation

  1. One mark per word (§1.2); maqqef chains share one; long words can carry two.
  2. Near/remote companion + isolated-substitute rules — §1.3 table. A validator can check: a disjunctive may only be preceded (ignoring conjunctives) by a same/higher-level disjunctive or its near companion.
  3. Rank-step rule (Mechon Mamre): successive distinctive marks may drop arbitrarily but rise at most one rank. Cheap sequence validator.
  4. Once-per-verse: sof pasuk (by definition), etnachta (≤1), segol (≤1 as first of its rank), shalshelet (≤1), qarne farah + yerach ben yomo (1× in Torah).
  5. Common phrase groups (use as test vectors): (Mercha) Tifcha (Mercha) Sof-Pasuk — end of every verse; (Mercha) Tifcha (Munach) Etnachta — ≤1×/verse; (Mahpach) Pashta (Munach) Zaqef-qaton — most common; Zakef-gadol standalone; [Munach] Zarka [Munach] Segol — zarka only before segol; Munach (Paseq) [Munach] Revia; Darga Tevir; Mercha-kefula usually alone.
  6. Yetiv / Pashta pair: pashta precedes zakef katan; replaced by revia when a stronger stop is needed or when >3 in a row — but the last stop before the zakef can never turn into revia. Mahpach must be followed by pashta, but yetiv may be followed by pashta or even by mahpach pashta. Mahpach vs yetiv are distinguished by placement/context, and are confusable when the first accented syllable has cholam/shuruk not beneath the word.
  7. Kadma v'Azla: the pair kadma (conjunctive) + azla/geresh (4th-level disjunctive) — "go forward and depart". May precede a mahpach, a revia group, or a tevir group. Yacavone: treat as one accent. Wikipedia: technically qadma/azla before gerish is a different sign from qadma before other disjunctives, though they look identical; Sephardim reserve azla for the former. Do not merge them in a parser without a flag.
  8. Pazer / Telisha cluster: 4th-level marks cluster, usually in order pazer → telisha gedola → geresh/gershayim, near the beginning of a long half-verse.
  9. Placement / glyph collisions (critical for tokenisation): - Pashta vs kadma: same glyph U+0599; pashta on last letter (doubled on mil'el words), kadma on stressed syllable. - Geresh vs azla: same glyph U+059C; geresh doubled unless mil'el or after kadma. - Mahpach vs yetiv: similar shape; mahpach under first letter of accented syllable, yetiv under first letter of word (always first letter). - Munach vs silluq/meteg: silluq looks like meteg (U+05BD); meteg is not a cantillation mark. - Zarka vs tsinnorit Unicode swap: encode zarqa/tsinnor as U+05AE "HEBREW ACCENT ZINOR", and tsinnorit as U+0598 "HEBREW ACCENT ZARQA" (Unicode Technical Note #27). A naïve name→codepoint map will be wrong. - Paseq (׀, U+05C0) can make an otherwise conjunctive mark distinctive (munach legarmeh), or mark an independent division. - Placement: pashta, zarka, segol, telisha always on leftmost letter; yetiv and telisha gedola always on rightmost letter (modern texts often duplicate/add a related accent on the stressed syllable to aid pronunciation).
  10. Exceptions are numerous: Mechon Mamre: "for each of these rules there are numerous places in the Hebrew Bible where they are violated." A validator should warn, not reject, on violations.
  11. Corpus sanity checks: Etnachta 5,483× in Torah; Pashta 5,429× in Torah (Price concordance, via Wikipedia).

Implementation sketch (derived, not a source claim): 1. Tokenise by Unicode codepoint (U+0591–U+05AF, U+05BD, U+05C0, U+05C3), resolving glyph collisions by position in word + following mark (pashta/kadma, geresh/azla, mahpach/yetiv), with the zarqa/tsinnorit swap hard-coded. 2. Parse the disjunctive sequence per half-verse into a tree using ranks (emperor 0, king 1, duke 2, officer 3, servant 4) + the rank-step and near/remote-companion rules; validate once-per-verse marks. 3. Segment into phrases = [conjunctives…] + disjunctive; each phrase is one musical unit. 4. Render via a per-mode motif table keyed by (mark, mode, phrase-length class, final/non-final, isolated?) — not by a single global pitch map.


2. The Chabad trop melody specifically

2.1 Bottom line

2.2 How the system works

2.3 Chabad vs. other traditions — how big are the differences?

2.4 The Torah mode in numbers (Eastern Ashkenazi, cross-checked)

Tonic = C in the Schmidt chart (C major, no sharps/flats except one marked B♭ in the segol melisma). Scale degrees below are relative to C (1=C5, 2=D5, 3=E5, 4=F5, 5=G5, 6=A5, 7=B5; below the tonic 7=B4, 6=A4, 5=G4, 4=F4). Range of the whole chart: F4–A5. Reciting tones are 1 (C5) and 2 (D5); the final is 1. (Malin's Kalib/Portnoy examples are notated in F major with one flat — same relative degrees, different absolute pitch. Absolute pitch is a free choice; readers chant at any comfortable level.)

2.5 Motif inventory

Transcribed from Stephen Schmidt, "Torah Trope" (5 pp., treble clef, C major), https://www.agudatachim.com/wp-content/uploads/2026/05/torahsheet.pdf — every notehead measured programmatically from the PDF (staff-line geometry → diatonic pitch) and verified visually staff by staff, including beams, rests, the B♭/♮ signs in the segol staff, and the open-headed half-note final of sof k'ria. Cross-checks against Malin 2016 noted per row.

Confidence key: A = notated in the chart and corroborated by Malin/Kalib/Portnoy · B = notated in the chart only · C = known only from recordings/forum, not notated anywhere found.

Ta'am Motif as notated (C major; phrase context in brackets) Degrees Conf.
Sof pasuk (siluk) [merkha–tipcha–merkha–] D5 D5 E5 C5 2 2 3 1 A
Etnachta [merkha–tipcha–munach–] C5 C5 D5 1 1 2 A (but see Slavin variation below)
Zakef katan [mahpach–pashta–munach–] G5 G5 E5 D5 5 5 3 2 A
Zakef gadol C5 C5 E5 G5 E5 D5 1 1 3 5 3 2 B
Tipcha D5 E5 (before etnachta/sof pasuk); D5 G5 E5 at end of reading 2–3; 2–5–3 A
Revia [munach–munach–] E5 E5 D5 C5 B4 A4 3 3 2 1 7 6 A
Tevir D5 C5 B4 C5 D5; preceded by darga G5 G5 F5 E5 D5 (long) or merkha D5 D5 (short) 2 1 7 1 2 A
Pashta [mahpach–] C5 G5 1–5 A
Yetiv G5 G5, then munach E5 E5 D5 + katon G5 G5 E5 D5 5 5 B
Segol [munach C5 C5, zarka C5 C5, melisma B♭4 A4 G4 A4 G4 F4, munach F4 C5,] C5 D5 C5 1 2 1 (melisma ♭7…4) B
Zarka C5 C5 reciting + descending melisma B♭4–A4–G4–A4–G4–F4 (only chromatic note in the chart) 1 1, then ♭7…4 B
Munach E5 C5 (before etnachta); E5 E5 D5 (before katon/yetiv); C5 C5 (before zarka/telisha/segol) varies A
Kadma C5 C5 (reciting on 1), shown only inside kadma-v'azla 1 1 B
Mahpach G5 G5 C5 (before pashta) 5 5 1 A
Merkha B4 D5 B4 (before tipcha); D5 D5 (before tevir / sof k'ria); E5 C5 (before sof pasuk) 7–2–7; 2–2; 3–1 A
Darga G5 G5 F5 E5 D5 5 5 4 3 2 B
Telisha gedola Recite C5 ×8, close E5 D5 E5 1… 3 2 3 B
Telisha ketana Recite C5 ×8, close E5 D5 C5 (differs from gedola only in last note) 1… 3 2 1 B
Geresh G5 G5 D5 5 5 2 B
Gershayim C5 D5 E5 D5 C5 D5 E5 1 2 3 2 1 2 3 B
Kadma-v'azla Kadma C5 C5; azla C5 E5 G5 E5 A5 G5 1 1 / 1 3 5 3 6 5 B
Pazer C5 C5 D5 D5 E5 A5 G5 E5 D5 1 1 2 2 3 6 5 3 2 B
Sof k'ria (end-of-reading coda) Merkha D5 D5, tipcha D5 G5 E5, merkha E5 C5, D5 E5 D5 A4 (final ah = half note) 2 2 / 2 5 3 / 3 1 / 2 3 2 6 A
Shalshelet Not in chart; forum: "The Chabad Shalshelet is basically 2 Pazers." 4× in Torah. — C
Karnei parah Not in chart; forum: "a combination of the Mercha Kefulah and Telisha Gedola." 1× in Torah. — C
Mercha kefula Not in chart; 1× in Torah. — C
Yerach ben yomo Not in chart; 1× in Torah. — C
Munach legarmeh Not in chart as such (munach + paseq); use contextual munach figure. — C

Notes on the table: - The chart notates phrases, not isolated marks — that is the correct unit. A ta'am's realisation depends on its neighbours and on position (mid-verse vs. end of verse vs. end of reading). - The chart lists phrase variants (e.g. etnachta 1A–1D, katon 3A–3F, telisha 9A–9D) but notates only the fullest form of each. - Two published variants differ from the chart at one point: Portnoy & Wolff's sof pasuk ends 1–5 where Kalib (and the chart) end 3–1 (Malin, Ex. 10a vs 10b). Treat the sof-pasuk ending as a known variation point. - The chart's home is Agudath Achim Synagogue, Altoona PA (Conservative; Dr. Stephen Schmidt, a member). It labels no tradition. It is used here as the Eastern Ashkenazi working model, not as a Chabad document. - Etnachta variation: Slavin's near-monotone rendering (Chabad.org forum, described as his personal style) differs from the chart's C5–C5–D5 — flag as a validation point, not a contradiction to resolve here. - Pronunciation: Chabad uses Ashkenazi pronunciation (e.g. tav, sav). A TTS/voice must use Ashkenazi, not Israeli/Sephardi, vowels.

2.6 What is text-reproducible vs. recordings-only

Layer Status
Grammar (phrase hierarchy, conjunctive/disjunctive rules, recursive dichotomy) Fully documented in text; machine-readable
Eastern Ashkenazi Torah mode (scale, resting pitches, cadences) Precisely documented in text + notation (Malin, Kalib, Portnoy & Wolff, Schmidt chart)
The Chabad melody specifically Not in staff notation in any public source found. Exists as TropeTrainer's Chabad system (sheet music behind demo/subscription) and as Slavin/Schusterman recordings. Reproducing it faithfully needs the TropeTrainer Chabad data or transcription of Slavin by ear/pitch analysis, diffed against the §2.5 chart
Rare marks (shalshelet, karnei parah, mercha kefula, yerach ben yomo) Recordings/forum only
Intra-Chabad variation Real: Slavin's flattened etnachta vs. older two-note etnachta — the tool must name its reference reader

2.7 Sources for the Chabad melody


3. Text data: Chumash with taamim as open data

3.1 Recommended stack

3.2 Sefaria — yes, taamim included

Docs: https://developers.sefaria.org/reference/getting-started — "all of our currently documented endpoints can be accessed without API keys, tokens, or authorization."

Endpoint (v3, current): GET https://www.sefaria.org/api/v3/texts/{Ref} — docs at https://developers.sefaria.org/reference-link/get-v3-texts

Version selection (verified from the docs page): the version param takes language or language|versionTitle. version=hebrew|Tanach with Ta'amei Hamikra returns only that version; no version param defaults to version=primary. There is also an older v2 endpoint https://www.sefaria.org/api/texts/{Ref}.

Verified live call (fetched 2026-11-17):

https://www.sefaria.org/api/v3/texts/Genesis.1.1?version=hebrew|Tanach%20with%20Ta'amei%20Hamikra

Returned (abridged — the versions[0] object only):

{"versions": [{"status": "locked", "priority": 1.0, "license": "Public Domain",
  "versionTitle": "Tanach with Ta'amei Hamikra",
  "versionTitleInHebrew": "תנ״ך מלווה בטעמי מקרא",
  "versionSource": "http://www.tanach.us/Tanach.xml",
  "language": "he", "isSource": true, "isPrimary": true, "direction": "rtl",
  "text": "בְּרֵאשִׁ֖ית בָּרָ֣א אֱלֹהִ֑ים אֵ֥ת הַשָּׁמַ֖יִם וְאֵ֥ת הָאָֽרֶץ׃"}],
 "available_versions": [ ... ]}

So Gen 1:1 with taamim is exactly: בְּרֵאשִׁ֖ית בָּרָ֣א אֱלֹהִ֑ים אֵ֥ת הַשָּׁמַ֖יִם וְאֵ֥ת הָאָֽרֶץ׃ — tipcha ֖ (U+0596) on בְּרֵאשִׁית, merkha ֣ (U+05A5) on בָּרָא, etnahta ֑ (U+0591) on אֱלֹהִים, merkha on אֵת, tipcha on הַשָּׁמַיִם, merkha on וְאֵת, siluk + sof pasuq ׃ (U+05C3) on הָאָרֶץ.

Notes: - The v2 call https://www.sefaria.org/api/texts/Genesis.1.1 also returned Hebrew with taamim in its he array — but it returned the whole chapter (31 verses) for a verse ref, and mixes in English versions. Use v3 with the pinned version. - return_format=text_only strips HTML/footnotes; default returns text as stored. (From the v3 docs page.) - Two Hebrew versions matter, and they differ: - "Tanach with Ta'amei Hamikra" — Public Domain, sourced from tanach.us/Tanach.xml (WLC). This is the one to use. - "Miqra according to the Masorah" (MAM) — CC-BY-SA, based on the Aleppo Codex; it is the primary Hebrew version, and it adds editorial accents (e.g. an extra pashta/zarqa/segol/telisha when an accent falls on an unstressed syllable; legarmeh/paseq visibly distinguished; qamatz qatan marked). For leining practice this is a real difference — pick one base text and stick to it. - A small pointing difference between editions was observed in live fetches: Gen 1:2 Sefaria/MAM has וְהָאָ֗רֶץ הָיְתָ֥ה while Mechon Mamre has וְהָאָ֗רֶץ הָֽיְתָ֥ה. Editions are not byte-identical. - Licensing: per-version license field in the API response. The Ta'amei Hamikra version is Public Domain; other Sefaria texts vary (CC-BY, CC-BY-NC, copyrighted). Sefaria's links dataset is CC-BY. Sefaria name/logo are trademarked. Source: https://developers.sefaria.org/docs/usage-of-our-name-and-logo - Bulk download (best for offline): https://github.com/Sefaria/Sefaria-Export — the repo is only an index (~25 MB); the actual data (~26 GB, ~85K files) lives in a public GCS bucket, no auth needed. Paths like gs://sefaria-export/json/Tanakh/Torah/Genesis/Hebrew/Tanach with Ta'amei Hamikra.json, .../txt/.../*.txt; books.json in the repo indexes everything with json_url/txt_url. (The exact Hebrew version filename should be confirmed from books.json before hardcoding it.) - Prior art: orelzion/2mikra builds a per-aliyah reader on exactly this API (3 parallel calls per aliyah, target versions "Miqra according to the Masorah" or "Tanach with Ta'amei Hamikra") — https://github.com/orelzion/2mikra/blob/HEAD/.agents/skills/sefaria-api/SKILL.md - Not verified: Sefaria API rate limits / fair-use thresholds. The old API wiki says "If you want to run your own database, please don't use this API to grab our data; instead download a complete dump" — for a shipped app, bulk-download once rather than scraping the API.

3.3 Mechon Mamre — full Tanakh with taamim, HTML only, restrictive licence

3.4 Other open sources

tanach.us — Unicode/XML Leningrad Codex (UXLC) ⭐ best offline source

Open Scriptures Hebrew Bible (OSHB / morphhb)

BHSA / ETCBC (Biblia Hebraica Stuttgartensia Amstelodamensis)

Others (verified as existing, lighter verification)

3.5 How taamim are encoded in Unicode

3.6 Aliyot — how divisions are represented

Hebcal @hebcal/leyning (best source — verified in full)

Vezot Habracha (verified in the file)

Entry "Vezot Haberakhah": {"num":54, "book":5, … "fullkriyah": {"1":["33:1","33:7"], … "7":["34:1","34:12"]}}. It is read on Simchat Torah (not Shabbat). Notable: unlike every other parsha in the file, it has no "M" (maftir) key — the maftir on Simchat Torah is a repeat of the 7th aliyah (Deut 34:1–12), but that halachic detail was not verified against a source in this pass, so treat the missing M as a data quirk to handle, not as a claim about the reading.

Special cases to handle

3.7 What is NOT available as open data

3.8 Suggested data architecture (one paragraph)

Ship the text offline: bulk-download Sefaria-Export's Tanach with Ta'amei Hamikra (PD) or the UXLC Tanach.xml.zip, store verses as received (no NFC), index by book/chapter/verse. Drive the practice flow from Hebcal @hebcal/leyning (aliyot.json + holiday-readings.json, or the REST API for date-aware readings incl. Israel/Diaspora). Derive per-word trope labels by parsing the Unicode accents in each word (handle stacks, maqaf-joined words, paseq/legarmeh). For audio, plan on recording your own reference leining per aliyah (or licensing Wieder/YU Torah streams) and aligning it yourself — that alignment layer is the genuinely missing open data, and it's the thing this tool would have to create.


4. What already exists — and the gaps

4.1 Chabad.org Torah Trainer (+ Megillah Trainer) — the only Chabad-native tool

4.2 TropeTrainer (HazzanSolutions, successor to Kinnor Software)

4.3 Pocket Torah (+ PocketTorah Trope) — Russel Neiss

4.4 Trope on the Go (Studio HaMikra, cantor-built, launched ~Sept 2026)

4.5 LearnTrope.com

4.6 TorahTrope.com

4.7 IvritSuite — Trope Tutor + Torah Trainer (free web)

4.8 Torah Morah (Adam Bellows)

4.9 Pink Trope (Danielius Studio, new Oct–Nov 2026)

4.10 Also noted (not deep-dived)

4.11 Comparison table

Tool Platform Price Voice Chabad trop? Follow-along highlight Slow playback Repeat a pasuk/word Record yourself Pitch feedback Quizzes/drills
Chabad Torah Trainer Web Free Recorded human (Alevsky / Kaplan / Slavin) Yes — native Yes, word-by-word 0.5×–2× Tap word/phrase No No No
TropeTrainer Web (+old iOS) $13/mo, $130/yr 12 "voice styles" — recorded vs. synth unverified for web version Yes, 1 of 79 systems Yes 0.25×–2× By word/verse/aliyah Yes (record, playback, download) No Tutor lessons only
Pocket Torah iOS/Android/web Free Recorded human (multiple cantors) No Yes No Tap verse/word No No No (Trope app has tutorials/exercises)
Trope on the Go Web + iOS Free tier; $11.99/mo, $119.99/yr Recorded cantor, not synthesized No (Ashkenazi only) Yes Yes Word/phrase repeat Yes, record & compare Yes, real-time pitch trail Yes — flashcards (spaced repetition) + games
LearnTrope Web Free Recorded MP3s No No No Line-by-line audio No No Guided practice only
TorahTrope.com Web Free Recorded, Ashkenazi No Tap word → trope name Half speed Custom verse ranges No No No
IvritSuite Trope Tutor Web Free PocketTorah recordings (Reform) No No No Clip replay in drills No No Yes — 3 quiz modes, mastery tracking
Torah Morah iPhone Free download (rest unverified) Recorded Not advertised Not verified Not verified Not verified Yes (sing-along) Yes, note-by-note Yes — quizzes/games
Pink Trope iOS Free Male voice in demos No Not verified Not verified Not verified Yes (it listens) Yes — Words % + Melody % scores No (archive/scores only)

4.12 Gaps a new Chabad lein-practice tool could fill

  1. A Chabad-trop tutor, not just a player. Chabad.org's trainer is a playback tool; TropeTrainer offers Chabad as 1 of 79 systems with no Chabad-first pedagogy. Nobody teaches the Chabad system clause-by-clause (families, frequency order, lookalike drills for kadma/pashta and yetiv/mahpach in the Chabad melody).
  2. Record-yourself + pitch feedback in the Chabad melody. Trope on the Go, Torah Morah, and Pink Trope all do pitch/score feedback — but only in Ashkenazi (non-Chabad) melodies. A Chabad-melody version of this does not exist.
  3. A male voice, by default. PocketTorah Trope's female voice draws kol-isha complaints from Orthodox users; a Chabad tool with a male baal koreh voice (e.g. in the style of Alevsky/Kaplan/Slavin) removes that objection entirely.
  4. Phrase-level practice loop for an aliyah. Tap-to-repeat a word exists in Chabad's trainer, but nobody offers phrase looping, sub-0.5× slow playback, "loop my hard spots," or a structured daily session (15–20 min) built around one aliyah.
  5. Lookalike-pair drills in Chabad trop. The known confusion pairs are a proven drill format (IvritSuite, Brainscape) — none exists for the Chabad melody, where the pairs sound different than in Avery/Binder.
  6. Chabad-specific content coverage. Weekday (Mon/Thu) readings, Rosh Chodesh, fast days, holidays, and Megillah in Chabad trop, plus the aliyah blessings — Chabad's trainer has the texts, but no practice structure around them; TropeTrainer has the structure, but Chabad is an afterthought.
  7. Progress tracking + teacher sharing. TropeTrainer lets you download a recording to send a tutor; nothing offers per-pasuk mastery tracking, spaced-repetition review of weak phrases, or a tutor dashboard for a Chabad cheder/shul.
  8. Free, offline-capable, Hebrew-first. The free tools (Pocket Torah, TorahTrope, IvritSuite) are Ashkenazi/Reform and buggy or stale (Pocket Torah's sync/pause bugs, 2021 last major update); the good pedagogy tools cost $12–13/month. A free, maintained, offline-capable Chabad tool would be the first in its lane.
  9. Trust/accuracy gap. Pocket Torah has documented wrong-text/wrong-audio mismatches and missing special haftarahs; a Chabad tool that is verified against the Chabad text (and clearly states its source) would be a differentiator.

Bottom line: the field splits into (a) free recording players with the wrong melody and real bugs, (b) one excellent but expensive generalist (TropeTrainer) that includes Chabad as an option, (c) one excellent new pedagogy app (Trope on the Go) that is Ashkenazi-only, and (d) Chabad.org's own trainer, which is free, authentic, and Chabad — but only a player. The open space is exactly a Chabad-first teacher: Chabad melody, male voice, clause-by-clause lessons, phrase looping, lookalike drills, record + pitch feedback, tikkun-to-STaM progression, and progress tracking.


5. How people actually learn to lein (pedagogy)

5.1 The traditional method

5.2 A good practice loop

The TorahTrope guide's six-step method, corroborated by the Torah Reading Guide:

  1. Read the words first, without chanting — get Hebrew fluent as plain reading; decoding letters and holding a melody at once means neither sticks.
  2. Find the phrase boundaries first — etnachta (mid-verse) and sof pasuk (verse end) divide each verse into halves/quarters; chanting is easier when you know where you're heading.
  3. Learn one phrase at a time, not one verse — chant the words up to the next separating mark until automatic, then add the next group. Verses are too long to hold at once.
  4. Loop the hard parts — the 2–3 spots that keep going wrong deserve most of the time; re-reading a whole aliyah to fix four words wastes the other three minutes.
  5. Practice out loud, at full volume, standing up — quiet mental practice builds a different skill than chanting in front of people.
  6. Drop the training wheels early — once solid, practise from consonants only (STaM/tikkun Torah side), leaving enough weeks to do it without panic. Progression: vowels+trope → two-column tikkun → STaM only.

Supporting habits: short frequent sessions beat long rare ones (15–20 min several times a week); record yourself and compare; use a teacher to correct errors before they fossilize.

5.3 How long it takes

5.4 Common stumbling blocks

5.5 What makes a practice tool effective vs. just a recording player

From the guides and from what the best tools do: (1) teach the system (clause families, in frequency order) rather than only playing your portion; (2) phrase-level looping and slow playback, not just whole-aliyah play; (3) visible phrase boundaries (color-coding, stacking by phrase); (4) a tikkun progression toward STaM; (5) active recall — quizzes, flashcards with spaced repetition, and lookalike-pair drills; (6) record-and-compare, ideally with pitch feedback, so errors get caught between lessons; (7) the right tradition's melody, with a male voice for Orthodox users; (8) short-session structure and progress tracking so daily practice actually happens.


6. The technical fork: how the voice gets made

The question that started this research: for producing the voice, compare (a) a tiny TTS with rule-based trop rendering from the marks, and (b) a recorded baal koreh voice. What's actually feasible for each, what data each needs, and what the hard parts are.

6.1 First: no TTS sings taamim today

Nothing found in this pass — no open model, no commercial product, no paper — produces chanted Torah with cantillation from text. Hebrew TTS exists, but for spoken Modern Hebrew, not chanted Biblical Hebrew. The melody layer is missing everywhere. This is the central fact of the fork: whichever path is chosen, the trop melody has to be supplied by the project, not by an off-the-shelf model.

The one precedent for machine-made leining is TropeTrainer, which Wikipedia lists under "Mechanical Cantillation (computer speech synthesis)" — it synthesizes chant with older (pre-neural) speech technology, in multiple melody systems. So synthesized leining is a proven product shape; it just hasn't been done with a tiny neural TTS.

6.2 What exists that each approach can build on

Hebrew TTS (spoken, modern) — the voice half of approach (a): - Phonikud (Interspeech 2026, https://phonikud.github.io, paper https://arxiv.org/abs/2506.12311): open-source Hebrew grapheme-to-phoneme producing fully-specified IPA, driving small real-time TTS like Piper (32M parameters, VITS) trained on 20 hours of synthetic Hebrew audio (via Gemini 2.5 Pro). Fine-tunes TTS with as little as 2 hours of data; runs on edge devices (Raspberry Pi); open models, code, and data (ILSpeech corpus). This is the Hebrew analogue of the tiny-voca recipe: synthetic data + small model. - BlueTTS (MIT, https://github.com/maxmelichov/BlueTTS, https://bluetts.com): multilingual TTS including Hebrew, ONNX, CPU-first, Hebrew G2P via renikud, runs in the browser on WebGPU with a CPU fallback. - HebTTS (Hebrew University, https://github.com/slp-rl/HebTTS, paper https://arxiv.org/pdf/2407.12206): open-source Hebrew TTS from ~5,000 hours of in-the-wild recordings; diacritic-free operation. - Key nuance for Torah text: the input is already vocalized — nikud is the pronunciation, so the G2P problem that Phonikud solves for unvocalized Modern Hebrew is mostly solved by the text itself. What remains is (i) pronunciation tradition: open Hebrew TTS is Modern Israeli pronunciation; Chabad leining needs Ashkenazi pronunciation (different vowels: e.g. tav as "s", kamatz as "aw", cholam as "oy" in some positions), which no open model provides — a voice would need training/fine-tuning on Ashkenazi speech; and (ii) the melody, which no TTS provides at all.

The pitch-control mechanism — the melody half of approach (a): - tiny-voca voice tuner (Nov 16, 2026, https://muninn.austegard.com/blog/tiny-voca-voice-tuner.html) — verified from the page: tiny-voca accepts per-phoneme duration and per-frame pitch overrides. "Two inputs override the model's own predictions: how many frames each phoneme lasts and the pitch of each frame. Lyrics are written in syllables (A-maz-ing grace) and notes as D4/1, or B4/.5~G4/.5 for a syllable held across two notes. Consonants keep roughly their spoken length and vowels fill the rest of each note." Result: "Told each phoneme's length and pitch the speech model sings within two cents of the notes" — median note error 0.7 to 1.4 cents, every note within 50 cents of the score (Praat pitch tracker). The model is 6.3 MB, runs in the browser, speaks ~27× real time on an iPhone. - This is the exact control interface a trop renderer needs: syllables + note sequence in, chanted voice out. It proves the architecture class (small neural vocoder with explicit duration + pitch inputs) can sing accurately — it does not prove a Hebrew model can, but the mechanism is language-independent; the phoneme inventory and the voice are what would change. - Related: Samuel (https://vvolhejn.com/blog/2026-08-17-samuel) — a speech model built on Pink Trombone (a vocal-tract simulator) where changing the pitch contour makes the voice sing a given melody. Speech-to-speech, not TTS, but shows the same principle: pitch is an external, controllable input. - Research-grade singing synthesis (YingMusic-Singer, Interspeech 2026, https://www.isca-archive.org/interspeech_2026/hao26_interspeech.pdf) does melody-controllable singing with diffusion models — but these are large research models, not tiny on-device ones, and they need a melody-providing reference clip.

Recorded audio — approach (b): - The reference recordings already exist: Slavin (all 54 portions + haftarot, Chabad.org), Schusterman (Beverly Hills Chabad), Wieder/YU Torah (full Torah/Haftarah/Megillot MP3s, free individual downloads). What does not exist is word-aligned audio — per-word timings for any of these. That alignment layer would have to be built (forced alignment of the recording against the known text, or manual segmentation per aliyah). - The whole Torah is finite: 54 parshiyot, ~5,846 verses. A single reader can record the entire Torah once; every aliyah is then covered forever.

6.3 Approach (a): tiny TTS + rule-based trop rendering

Aspect Assessment
What it is A small Hebrew TTS voice (Ashkenazi pronunciation) driven by a trop renderer: parse text → phrases → motif table → per-syllable note + duration sequence → pitch/duration overrides into the TTS. The melody is code; the voice is a model.
What it needs (1) A validated Chabad motif table (§2.5, validated against Slavin — the missing piece); (2) a phrase parser (§1.5); (3) a Hebrew TTS voice with Ashkenazi pronunciation — none exists open; needs fine-tuning on Ashkenazi speech (Phonikud's "as little as 2 hours of data" is the encouraging datapoint, but the 2 hours must be Ashkenazi, and ideally chanted, not spoken); (4) a duration model (how long each syllable/note lasts — trop has no fixed meter, so this is a design choice, not a fact to look up); (5) the text + aliyah data (§3).
Hard parts The motif table validation (Chabad melody is recordings-only — §2.6); the Ashkenazi voice (no open source; recording/fine-tuning a voice is a real project); the duration/rhythm model (free chant — what sounds right is a judgment call, needs a cantor's ear to validate); quality risk — a slightly-wrong synthetic chant teaches wrong melody, which is worse than no chant for a learner.
Strengths Infinite coverage: any verse, any aliyah, any custom range, any speed, any pitch/key, on demand, offline, tiny (MBs). One voice, every reading. Follows the tiny-voca spirit: own the voice outright, no recordings of a real person needed (though a real voice is still the best fine-tuning data). Can render the rare tropes (shalshelet etc.) the moment the motif table has them.
Feasibility verdict Plausible, but the hardest path. The pitch-control mechanism is proven (tiny-voca sings within cents); the Hebrew small-TTS recipe is proven (Phonikud); what is unproven is the combination (Hebrew + Ashkenazi + chanted) and the motif table it depends on. Estimate: real R&D, not a weekend.

6.4 Approach (b): recorded baal koreh voice

Aspect Assessment
What it is A real reader (e.g. in the style of Slavin) records the Torah — per aliyah, or per verse — and the tool plays it back with word-level highlighting, phrase looping, and speed control. The melody is in the audio; the tool's job is alignment + pedagogy.
What it needs (1) A reader and recording sessions (or a licence to existing recordings — Slavin's are on Chabad.org, Wieder's at YU Torah; licensing terms unverified); (2) word/phrase-level alignment of audio to text (forced alignment, or manual segmentation — the missing open-data layer, §3.7); (3) the text + aliyah data (§3); (4) the phrase parser (§1.5) for looping/drills (the parser is needed either way).
Hard parts Alignment: getting per-word timings right across ~5,846 verses is the bulk of the work (forced alignment on Hebrew chant is not an off-the-shelf solved problem; manual segmentation is laborious but tractable per aliyah). Recording quality/consistency across sessions. Speed control: time-stretching audio below ~0.5× degrades; a practice tool wants very slow playback. Fixed voice: one reader, one style — but for Chabad practice that is a feature (one canonical reader).
Strengths Authentic from day one — the melody is exactly right, including the rare tropes, the coda, the phrasing, the breathing. No ML risk, no "slightly wrong melody teaches wrong" failure mode. Proven by every existing tool (Chabad.org trainer, Pocket Torah, Trope on the Go all use recordings).
Feasibility verdict The safe, fast path. The work is recording + alignment + app, all well-understood. The main cost is the recording sessions and the alignment effort, not research.

6.5 A third option worth naming: hybrid

Record the reference voice and use it to bootstrap the synthetic one: the recordings give (i) the ground-truth motif table (pitch-track Slavin, diff against the §2.5 chart — §7 step 1), (ii) the fine-tuning data for an Ashkenazi chanted voice (a few hours of Slavin-style chant is exactly the "2 hours of data" Phonikud-style fine-tuning wants), and (iii) the MVP's audio while the synthetic voice is being built. The recorded path ships first; the synthetic path replaces/augments it later (e.g. for arbitrary verse ranges, speed/key changes, and offline size). This is the recommended sequencing — see §7.

6.6 What would have to be built either way

Both approaches need: the phrase parser (§1.5), the text + aliyah pipeline (§3), the motif table or the alignment layer, and the practice loop (§5). The voice is the only fork. Everything else is shared infrastructure — so the fork can be decided late, after the shared pieces exist.


7. Recommended path

Stage 0 — Validate the melody (the one thing everything depends on). 1. Open the TropeTrainer free demo, select the Chabad voicing system, inspect its sheet music — if its note data is accessible, that becomes the canonical motif table. 2. In parallel, take the §2.5 chart as the working hypothesis. 3. Validate against Slavin's Chabad.org recordings: transcribe by ear/pitch-tracking the first verses of Bereishit (which contain merkha-tipcha-munach-etnachta, katon, sof pasuk) and diff against §2.5. Pay special attention to: etnachta (Slavin reportedly flattens it), the sof-pasuk ending (3–1 vs 1–5), and the shalshelet (2 pazers?). 4. Name the reference reader in the tool (Slavin) and record the decision — intra-Chabad variation is real.

Stage 1 — Shared infrastructure (no voice decision needed). 5. Text pipeline: bulk-download Sefaria-Export's Tanach with Ta'amei Hamikra (PD) or UXLC Tanach.xml.zip; store as received (no NFC); index by book/chapter/verse. 6. Aliyot: Hebcal @hebcal/leyning (aliyot.json + holiday-readings.json). 7. Phrase parser: tokenise by codepoint (handle the §1.5 collisions), parse per half-verse into the rank tree, segment into phrases. Validate against the common phrase groups (§1.5.5) as test vectors. 8. Practice-loop design (from §5): phrase-level looping, slow playback, tikkun progression (vowels+trope → two-column → STaM only), lookalike-pair drills, 15–20-minute sessions, per-pasuk mastery tracking.

Stage 2 — Ship with a recorded voice (fast, authentic). 9. Record a reference reader (or licence existing recordings — terms unverified) per aliyah; build the word-level alignment layer (forced alignment, hand-checked per aliyah). 10. MVP: pick a parsha → pick an aliyah → hear it leined in Chabad trop with word highlighting, phrase looping, slow playback, tikkun view. This is the tool the user asked for, and it works with zero ML risk.

Stage 3 — Prototype the synthetic voice (in parallel, no deadline). 11. Fine-tune a small Hebrew TTS (Phonikud/Piper-style) on Ashkenazi chanted speech; drive it with the validated motif table via per-phoneme duration + per-frame pitch overrides (the tiny-voca mechanism). 12. A/B the synthetic voice against the recorded reference with a cantor's ear. Ship it only when it is indistinguishable-or-better on melody accuracy — a slightly-wrong synthetic chant is worse than a recording for a learner. 13. If it works, the synthetic voice adds: arbitrary verse ranges, any speed/key, tiny offline size, and the rare tropes for free.

What not to do: don't use Avery/Binder (Reform) or Wolff/Portnoy charts as the Chabad melody — different voicing systems for the same marks. Don't use Sephardi sources at all. Don't ship a synthetic voice before a cantor validates its melody. Don't NFC-normalize the text. Don't treat the §2.5 chart as "the Chabad melody" until Stage 0 step 3 is done.


8. Caveats and thin spots (say plainly)


9. Source list (all links verified 2026-11-17 unless noted)

Taamim system: Wikipedia "Hebrew cantillation" https://en.wikipedia.org/wiki/Hebrew_cantillation · Mechon Mamre / Helmut Richter, "Hebrew cantillation marks and their encoding" https://www.mechon-mamre.org/c/hr/intro.htm · code tables https://www.mechon-mamre.org/c/hr/tables.htm · J101 "Ta'amei HaMikra" https://practice.j101.net/taamei-ha-mikra · Yacavone "Cantillation Reference" (after James D. Price, The Syntax of Masoretic Accents) https://www.yacavone.net/accents/ · Wikipedia "Pashta" https://en.wikipedia.org/wiki/Pashta · Wikipedia "Etnachta" https://en.wikipedia.org/wiki/Etnachta · Iancu, "The Hebrew Cantillation System" (2025) https://musicologypapers.edituramediamusica.ro/images/issues/MP_2025-1_XL-1_04_Alexandra_Rebeca_Iancu.pdf · Malin, "Eastern Ashkenazi Biblical Cantillation" (Yuval 10, 2016) https://jewish-music.huji.ac.il/en/yuval/22542

Chabad melody: TropeTrainer https://www.tropetrainer.com/ · Schmidt "Torah Trope" chart https://www.agudatachim.com/wp-content/uploads/2026/05/torahsheet.pdf · Chabad.org Slavin recordings https://www.chabad.org/multimedia/audio_cdo/aid/983326/jewish/Torah-Reading-Recordings.htm · Chabad.org Interactive Torah Trainer https://www.chabad.org/library/howto/trainer_cdo/aid/2747444/jewish/Interactive-Torah-Trainer-Demo.htm · Chabad.org Torah Reading Trop + forum https://www.chabad.org/multimedia/music_cdo/aid/931078/jewish/Torah-Reading-Trop.htm · Beverly Hills Chabad Schusterman recordings https://www.beverlyhillschabad.com/torah-reading/TORAH-MENU.HTM · ChabadInfo Slavin MP3s http://chabadinfo.com/news/prepare-for-krias-hatorah-parshas-naso/ · Lipinski Bar Mitzvah Torah Trainer (SoundCloud) https://soundcloud.com/themitzvahclub/sets/barmitzvah-torah-trainer-torah-cantillations-taamei-hamikra · Chabad.org "Who Made Up the Way We Sing the Torah?" https://link.chabad.org/library/article_cdo/aid/817346/jewish/Who-Made-Up-the-Way-We-Sing-the-Torah.htm · Jacobson companion site https://www.chantingthehebrewbible.com

Text data: Sefaria developers https://developers.sefaria.org/reference/getting-started · Sefaria v3 texts API https://developers.sefaria.org/reference-link/get-v3-texts · Sefaria-Export https://github.com/Sefaria/Sefaria-Export · tanach.us https://www.tanach.us/ · OSHB/morphhb https://github.com/openscriptures/morphhb · BHSA https://github.com/ETCBC/bhsa · BHSA cantillation docs https://etcbc.github.io/bhsa/cantillation/ · STEPBible TAHOT https://github.com/STEPBible/STEPBible-Data · Mechon Mamre https://www.mechon-mamre.org/c/ct/c0.htm · Hebcal leyning https://github.com/hebcal/hebcal-leyning · Unicode Hebrew table http://www.i18nguy.com/unicode/hebrew.html · hebrew-text-in-practice https://github.com/ohavben/hebrew-text-in-practice · Vayavinu Bamikra https://en.wikisource.org/wiki/Vayavinu_Bamikra

Existing tools: Chabad.org Torah Trainer https://www.chabad.org/library/howto/trainer_cdo/aid/2747444/jewish/Interactive-Torah-Trainer-Demo.htm · TropeTrainer https://www.tropetrainer.com/ · Pocket Torah https://www.pockettorah.com/ (app) · Trope on the Go https://tropeonthego.com/splash · LearnTrope https://www.learntrope.com/ · TorahTrope https://torahtrope.com/pdf/how-to-practice-torah-trope.pdf · IvritSuite Trope Tutor https://ivritsuite.com/trope_tutor.html · Torah Morah https://torahmorah.org/ · Pink Trope https://www.pinkfame.art/ · Sefaria https://www.sefaria.org/texts · Navigating the Bible http://bible.ort.org/

Voice technology: tiny-voca https://huggingface.co/n4ze3m/tiny-voca · tiny-voca code https://github.com/n4ze3m/tiny-voca · tiny-voca demo https://tiny-voca.n4ze3m.com · tiny-voca voice tuner (pitch/duration control) https://muninn.austegard.com/blog/tiny-voca-voice-tuner.html · Phonikud https://phonikud.github.io (paper https://arxiv.org/abs/2506.12311) · BlueTTS https://github.com/maxmelichov/BlueTTS · HebTTS https://github.com/slp-rl/HebTTS (paper https://arxiv.org/pdf/2407.12206) · Samuel / Pink Trombone https://vvolhejn.com/blog/2026-08-17-samuel · YingMusic-Singer https://www.isca-archive.org/interspeech_2026/hao26_interspeech.pdf

Pedagogy: TorahTrope practice guide https://torahtrope.com/pdf/how-to-practice-torah-trope.pdf · Learn to Leyn (Kamionkowski) https://kamionkowski-bet-midrash.teachable.com/p/learn-to-leyn · Torah Reading Guide https://www.torahreadingguide.com/beginners


Full Chabad-melody deep-dive (the §2.5 transcription's method, cross-checks, and full source notes): ~/workspace/research/chabad-trop-research.md.