KoreanFA
KoreanFA creates Praat TextGrid files from Korean or Japanese WAV audio and a matching UTF-8 transcript. It provides both a Python API and a command-line interface, with automatic Korean/Japanese model selection by default.
Features
- Align one WAV/TXT pair or an entire directory of pairs
- Select Korean or Japanese automatically, or choose a model explicitly
- Produce word and phone tiers in a Praat TextGrid
- Validate a corpus before alignment and record reproducible JSON run reports
- Export structured intervals as JSON, CSV, or word/phone CTM files
- Use a managed Kaldi-based engine; Docker and a web server are not required
Requirements
- Linux x86_64 with glibc 2.17 or later
- Officially supported and tested: Ubuntu 22.04 LTS and 24.04 LTS
- Older Ubuntu releases and other glibc-based Linux distributions may work, but are not currently covered by KoreanFA's official test matrix
- macOS 12 or later on Apple Silicon (arm64) or Intel (x86_64)
- Python 3.12 or 3.13
- WAV audio and UTF-8 text transcripts
Windows is not supported yet. KoreanFA automatically downloads the native engine matching a supported Linux or macOS system.
Installation
Install KoreanFA from PyPI, then install the native alignment engine matching the current system once:
python -m pip install koreanfa
koreanfa engine install
To use the latest development source from the default branch instead:
git clone --depth 1 https://github.com/hyung8758/Korean_FA.git
cd Korean_FA
python -m pip install .
koreanfa engine install
Check the engine status at any time:
koreanfa engine status
If the engine is missing, an alignment command explains how to install it.
Command line
Align one WAV/TXT pair:
koreanfa align recording.wav recording.txt
This creates recording.TextGrid beside the input audio by default.
Align every matching pair in a directory:
koreanfa align corpus
koreanfa align corpus -r -o aligned
Files are paired by their relative stem: for example, session_01.wav is matched with session_01.txt. Unmatched files are skipped by default and a warning identifies them.
Validate pairing, UTF-8 transcripts, language detection, complete WAV decoding, and engine readiness without running Kaldi:
koreanfa validate corpus -r --report validation.json
Validation collects all detected problems instead of stopping at the first file. It exits with status 2 for errors; add --strict to make warnings fail as well. --no-engine-check is available when checking data on a machine that will not perform alignment.
The CLI reports each file's preparation/decode stage, a directory progress bar, and a final total / success / failed / skipped summary. Successful files keep their TextGrids even if other files fail; the CLI then exits with status 2 and prints each rejected file's reason. Add --keep-workdir to retain logs/summary.tsv and per-file Kaldi logs for diagnosis.
Language selection
-l auto / --lang auto is the default. Hangul selects the Korean model, while Hiragana, Katakana, or Kanji selects the Japanese model. Choose a model explicitly for mixed-script transcripts. In a directory, a transcript that has neither script (for example, <laugh> or English-only text) is reported in batch.failures; other files continue to run.
koreanfa align recording.wav recording.txt -l kor
koreanfa align recording.wav recording.txt -l jap
Run koreanfa align --help for all options.
Alignment options
-nj N,--num-jobs N: align up toNfiles concurrently; the default is 4. In Python, usenum_jobs=N.-o DIR,--output-dir DIR: write TextGrids underDIR(output_dir=DIR).-kd DIR,--kaldi-dir DIR: use an external Kaldi runtime (kaldi_dir=DIR).-l {auto,kor,jap},--lang ...: choose a language adapter (lang=...).-r,--recursive: include subdirectories when aligning a directory (recursive=True).-iu,--ignore-unmatched [true|false]: skip WAV/TXT files without a same-stem counterpart and issue a warning; this is the default (ignore_unmatched=True). Set it tofalseto stop before alignment when an unmatched file is found.-nw,--no-word;-np,--no-phone: omit the corresponding TextGrid tier (word_tier=False/phone_tier=False).-kw,--keep-workdir: retain successful-run Kaldi logs and staged diagnostics (keep_workdir=True).--existing {overwrite,skip,error}: overwrite existing TextGrids (the compatible default), skip realignment for structurally valid TextGrids, or stop before alignment if a requested output already exists (existing=...). Requested JSON/CSV/CTM files are still generated from a valid skipped TextGrid; a damaged TextGrid is never treated as a successful skip.--export {json,csv,ctm}: write an additional machine-readable format; repeat the option for multiple formats (exports=("json", "csv", "ctm")). CTM export writes separate word and phone files, omits only empty gap intervals, and uses the corpus-relative stem as its recording ID. Whitespace, control characters, and%in CTM recording IDs or labels are UTF-8 percent-encoded to preserve the five-field format; JSON and CSV labels remain unchanged.--report PATH: atomically write a versioned JSON run report containing relative paths, options, outcomes, attempt counts, and engine metadata (report_path=PATH). Transcript contents are not copied into the report.
Use -h / --help for command help and -v / --version for the package version.
Python API
Install the engine once, then align a pair:
from koreanfa import align, install_engine
install_engine()
result = align("recording.wav", "recording.txt", lang="auto")
print(result.textgrid)
print(result.language) # "kor" or "jap"
for word in result.words:
print(word.start, word.end, word.label)
For a directory, use Aligner:
from koreanfa import Aligner
aligner = Aligner(lang="auto", num_jobs=4)
batch = aligner.align(
"corpus",
output_dir="aligned",
recursive=True,
existing="skip",
exports=("json", "csv", "ctm"),
report_path="aligned/run.json",
)
for result in batch.results:
print(result.textgrid, result.outputs["json"])
for skipped in batch.skipped:
print(f"unchanged: {skipped.textgrid}")
for failure in batch.failures:
print(f"rejected: {failure.audio} ({failure.reason})")
result.words and result.phones contain typed intervals in seconds, including named silence intervals. result.outputs identifies every emitted file. Directory alignment returns successes in batch.results, valid existing outputs in batch.skipped, and controlled per-file rejections in batch.failures; aggregate counts and elapsed time are available from batch.summary.
Library calls do not print progress by default; unmatched input files are reported through Python's warning system. Pass a progress callback when the host application wants structured progress events, and use keep_workdir=True when it needs to retain logs/summary.tsv.
The same preflight is available in Python as validate("corpus", recursive=True). Its ValidationReport contains every valid pair and every structured issue; pass check_engine=False when validating data only.
Input notes
- Each WAV file needs a matching UTF-8
.txttranscript. - One sentence per transcript is recommended.
- Audio is normalized to mono 16 kHz PCM WAV in a temporary workspace.
- Korean pronunciation conversion is provided by the package dependency
ko-speech-toolsand its Korean MeCab dictionary; no separate Korean G2P installation is required. - Japanese support includes the required MeCab and IPADIC resources in the managed engine.
Engine management
koreanfa engine install
koreanfa engine status
koreanfa engine install -f
koreanfa engine remove -y
Set KOREANFA_ENGINE_HOME to choose the engine cache location. Advanced users can set KOREANFA_KALDI_DIR or pass kaldi_dir= to use an externally managed Kaldi runtime instead.
If an engine download or checksum verification fails, see the engine installation troubleshooting guide. KoreanFA never installs an engine whose SHA-256 checksum does not match the published manifest.
Citation
If you use KoreanFA in academic work, please cite the specific version used in your research. Citation metadata is provided in CITATION.cff and through the Cite this repository menu on GitHub.
License
KoreanFA code and the Japanese acoustic model are licensed under Apache-2.0. The Korean acoustic model is proprietary to Mediazen and may be used for commercial or non-commercial purposes only as part of KoreanFA; modification or separate redistribution requires prior written permission. See the Korean model notice, the example-data notice, and the third-party notices for bundled source material and the separately downloaded engine.
Release files for koreanfa 2.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| koreanfa-2.3.0.tar.gz | 55.6 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| koreanfa-2.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 111.3 MB
Release files / koreanfa-2.3.0.tar.gz
| Download URL | koreanfa-2.3.0.tar.gz |
|---|---|
| Size | 55.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bd4d4074e61ccac20b99799a2755f480c02e6ffd721eecbcb70aabac38b974c1
|
|
BLAKE2b-256 checksum How to use checksums |
362d9d811ae24e407f41c0bf7821a1a6219a6ace7f4725db20557a85e5a67608
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 21, 2026.
Transparency logRelease files / koreanfa-2.3.0-py3-none-any.whl
| Download URL | koreanfa-2.3.0-py3-none-any.whl |
|---|---|
| Size | 55.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
01e3fb3d6bf15362006987bae0cac777cdc13aca4172d0271dc9b489ac5c7a21
|
|
BLAKE2b-256 checksum How to use checksums |
633cd4fdcdf6ae6fde2d5ab695b81815949f4ef4ab52b8714b6df3d0b0aca1b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 21, 2026.
Transparency log