Piper is a fast, local neural text-to-speech engine that uses VITS models exported to ONNX for inference. The repository provides a comprehensive application stack: a Python package (`piper-tts`) with a clean API for voice synthesis, a CLI tool, an HTTP server with a web interface (including viseme animation), and a C/C++ shared library (`libpiper`) for embedding in other applications. It also includes a full training pipeline using PyTorch Lightning, allowing users to fine-tune or train new voices from scratch, with support for multi-speaker models, custom phonemes, and VAD silence trimming. The architecture is modular: phonemization is handled by language-specific backends (espeak-ng, Chinese pinyin/g2pW, Hebrew Nakdimon, Japanese OpenJTalk, Arabic tashkeel), and the core inference engine uses ONNX Runtime for efficient, cross-platform execution. The codebase is well-structured with clear separation of concerns, extensive testing, and CI/CD pipelines that build wheels for all major platforms. Although primarily an application, the training code (VITS model implementations, dataset caching, monotonic alignment Cython) exhibits data/research characteristics, making it a hybrid project. The repository is actively maintained, with a responsive issue tracker and regular updates, though the last commit date appears anomalous.
This repository is the full-stack implementation of Mega, a large-monorepo Git hosting and code collaboration platform with a Rust backend and a large React/Next.js frontend. The backend is split into several crates: mono provides the HTTP/SSH API server, ceres contains application services for Git operations, change lists (CLs), code review, build triggers, webhooks and notifications, jupiter handles persistence through SeaORM entities and storage services, jupiter-migrate manages a large sequence of database migrations, and orion/orion-server implement a Buck2-based distributed build orchestration system. The frontend in moon/apps/web is a feature-rich collaboration application with posts, notes, chat, notifications, project management, diff viewing, CL/merge-queue review, admin groups, OAuth integrations, and editor support. The core operational flow is: git push/import -> ceres transport and jupiter storage -> change list and merge-queue workflows -> build triggers sent to Orion -> build events/checks streamed back to the UI.