# eventyay-interpretation: live captions for Eventyay streams > eventyay-interpretation is an Apache-2.0 Eventyay plugin that connects Eventyay organizers to a VoxBento live interpretation console. It targets event teams that need live captions and language selection for video streams, but its documented setup is development-oriented. **fossasia/eventyay-interpretation** — A plugin for live interpretation of video streams - Repository: https://github.com/fossasia/eventyay-interpretation - Stars: 1,551 · Forks: 12 - Language: HTML - License: Apache-2.0 - Published: 2026-10-16 · Updated: 2026-10-16 · Language: en - Canonical page: https://hysenlabs.com/projects/fossasia-eventyay-interpretation ## What eventyay-interpretation Adds to Eventyay eventyay-interpretation addresses a specific gap in event streaming: organizing live interpretation alongside a video event. The README describes a plugin for integrating the fossasia/voxbento live interpretation console with Eventyay. According to that description, the integration supports live interpretation of video streams, language selection, and live captions. The intended users are Eventyay organizers who already have an event and a VoxBento instance to connect to it. This is not a general-purpose streaming server, nor does the repository describe a separate operator console for event staff. Its scope is the connection between those two named systems. The project is organized as a Python package named eventyay-interpretation, with an interpretation package and a tests directory. Its package metadata includes requests>=2.31.0 and cryptography>=41.0.0 as runtime dependencies. The project also registers the interpretation application through the pretix.plugin entry-point group, which is the registration mechanism named in the configuration files. That registration matters for an Eventyay operator. The README does not describe a standalone command-line interface or an independent deployment target. Instead, the documented path is to install the application into an Eventyay development setup and enable it from the Eventyay settings plugins tab. ## The VoxBento Connection Boundary The available documentation defines the integration boundary but does not provide a detailed internal data-flow diagram. At the visible configuration level, the project exposes the interpretation application through [project.entry-points."pretix.plugin"], and its package data includes interpretation/language_map.yml. Those files indicate that the plugin has a language mapping resource and an Eventyay plugin registration path. The README names three user-facing capabilities: live interpretation of video streams, language selection, and live captions. It attributes the live interpretation console to fossasia/voxbento. The documentation does not state whether the video stream is pulled directly by this repository, sent by Eventyay to VoxBento, or handled through another intermediary. It also does not document authentication headers, callback URLs, stream formats, retry behavior, or the event lifecycle for caption sessions. This is a meaningful boundary for technical evaluation. A team can identify the intended systems and the plugin registration mechanism from the repository, but it cannot derive deployment topology or failure behavior from the README. The source layout suggests that language data is packaged with the application, while the external VoxBento relationship remains the central operational dependency. ## Installing the Plugin in Eventyay The README describes a development setup rather than a packaged installation for end users. First, the reader needs a working Eventyay development setup, as stated in the project documentation. The repository then needs to be cloned, for example into local/eventyay-interpretation, and the virtual environment used for Eventyay development must be activated. After that setup, register the application with the Eventyay plugin registry from the repository directory: ```bash uv pip install -e . ``` The README says this registers the application with the Eventyay plugin registry. Compile the translations next: ```bash make ``` The Makefile maps the default target to localecompile, which runs django-admin compilemessages. After the local Eventyay server is restarted, the plugin can be enabled for events in the 'plugins' tab in Eventyay settings. The documentation does not give a production installation command, a Docker deployment, or a release archive, so teams should not infer those options from the development instructions. ## Checking Code Quality and Translations The repository includes Ruff configuration for Python 3.11 style checks, formatting, and import ordering. The README documents installation of Ruff separately, followed by checks for rule violations: ```bash pip install ruff ``` That command installs the checker named in the documentation. The repository then defines these checks: ```bash ruff check . ruff format --check . ``` The README says the project uses CI to enforce code style rules and lists these commands for local checking. Automatic fixes are also documented: ```bash ruff check . --fix ruff format . ``` For pre-commit integration, the README names .install-hooks. It does not give the command for invoking the installed hook, so the exact execution sequence is left to the Eventyay development environment. Translation maintenance is separate from Ruff. The Makefile provides localegen, which runs django-admin makemessages and includes language directory arguments generated from interpretation/locale. The README only instructs developers to run make for compilation, not to regenerate translation catalogs. ## Operational Limits of the Documented Integration The clearest limitation is the lack of a documented production lifecycle. The repository has no GitHub releases, and the README describes cloning, editable installation, compilation, and local server restart. It does not document version pinning, production packaging, database migration procedure, rollback, VoxBento deployment, or credential management. The project also does not say how a failed VoxBento request is surfaced in Eventyay. Although requests and cryptography are declared dependencies, the supplied documentation does not identify which operations require cryptography, how secrets are supplied, or whether network errors are retried. As a result, an operator cannot use the README alone to define an incident response for a disconnected interpretation service. The lack of detail is not proof that these features are absent. It does mean they are not established by the repository documentation available for review. A team that needs a guaranteed caption uptime target, a documented recovery process, or a formal compatibility matrix must verify those points against the code and the surrounding Eventyay and VoxBento deployments before relying on the plugin. ## Comparing Plugin Installation with Direct VoxBento Use The repository names fossasia/voxbento as the live interpretation console. A direct VoxBento deployment would be an alternative integration approach in which an organization manages the interpretation console outside Eventyay. The repository documents the plugin route because it registers interpretation with Eventyay and exposes the requested live interpretation, language selection, and caption functions through that relationship. The difference is architectural rather than a claim about either project's feature set. Direct VoxBento use keeps the operator's work centered on the VoxBento instance and does not, by definition, install this Eventyay plugin. The plugin route adds an Eventyay-facing registration layer and requires the operator to maintain an Eventyay development or deployment environment. The README does not document the steps, APIs, or operator workflow for direct VoxBento use, so it cannot be used to compare configuration options or session behavior. It also does not claim that the plugin replaces VoxBento. Based on the stated integration, a team should choose this plugin when it wants the Eventyay connection, while treating VoxBento as the external service that provides the live interpretation console. ## Maintenance Signals and Upgrade Surface The repository is not archived, and its last push was on 2026-10-15. The repository has no GitHub releases. These facts describe the visible maintenance signals, but they do not establish a release cadence or a promise of compatibility with a particular Eventyay version. The main upgrade surface is the Eventyay plugin environment rather than a standalone application deployment. The project uses an editable install command, the Eventyay plugin registry, and a local server restart. Its dependencies are declared with minimum versions: requests>=2.31.0 and cryptography>=41.0.0. The repository also contains uv.lock, tests, CI configuration, translation tooling, and Ruff configuration, but the README does not explain an upgrade procedure for the surrounding Eventyay or VoxBento installations. The Apache-2.0 license permits use and modification under its terms, subject to the license text. This review does not interpret the license or provide legal advice. Copyright 2026 FOSSASIA is stated in the README. Organizations should preserve required notices and review the actual LICENSE file before redistribution. ## Conclusion Eventyay organizers should adopt this plugin when they already operate an Eventyay development environment and can supply a VoxBento instance. It is not a suitable standalone captioning service for teams without that infrastructure. Before adoption, verify the VoxBento connection, language configuration, translation build, and the absence of a documented rollback or production upgrade procedure; the project should not be selected for a deployment that requires a published release artifact or a documented release history. ## FAQ ### What does eventyay-interpretation do? It is an Eventyay plugin for integrating the fossasia/voxbento live interpretation console. The README lists live interpretation of video streams, language selection, and live captions as supported capabilities. ### How do I install eventyay-interpretation? The README requires a working Eventyay development setup and a virtual environment. It then instructs developers to clone the repository, run uv pip install -e ., run make to compile translations, and restart the local Eventyay server. ### How do I enable eventyay-interpretation in Eventyay? After the editable installation, translation compilation, and local Eventyay server restart, enable the plugin in the 'plugins' tab in Eventyay settings. The repository does not document a production enablement procedure. ## Sources - [fossasia/eventyay-interpretation on GitHub](https://github.com/fossasia/eventyay-interpretation) - [Issues](https://github.com/fossasia/eventyay-interpretation/issues) - [License: Apache-2.0](https://github.com/fossasia/eventyay-interpretation/blob/dev/LICENSE) - [README](https://github.com/fossasia/eventyay-interpretation/blob/dev/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/fossasia-eventyay-interpretation