This release is a pre-release and may not be stable for production use.
travel-animator
Render videos for the Travel Animator app.
A companion to the Travel Animator service; it needs an account. See licence for the terms.
The Python import path is tada_render.
Install
pip install travel-animator
Requirements: Python 3.12+, an OpenGL implementation (a GPU driver in production, Mesa/llvmpipe for CPU-only use on Linux), and FFmpeg/PyAV's usual runtime libraries.
Linux, macOS, and Windows are all supported. On Windows the GL context comes from WGL, which needs an interactive desktop session: a service (session 0) cannot create one, and there is no software-render fallback as on Linux.
For the MCP server, install the mcp extra:
pip install "travel-animator[mcp]"
The extra keeps the MCP SDK out of the base install (and out of the GPU worker's dependency set — the renderer itself never imports it).
CLI
Console script: travel-animator.
travel-animator login # interactive magic-link login, or store a bearer token
travel-animator logout # remove locally stored credentials (local only; see below)
travel-animator render-bundle # render a prepared, offline bundle to MP4
travel-animator mcp # run the stdio MCP server (requires the `mcp` extra, below)
login authenticates against the same account system the Travel Animator
mobile app uses. With no argument on an interactive terminal it runs a
magic-link flow (email -> 6-digit code); with a token argument, -, or piped
stdin it stores a bearer token directly (for CI). Credentials are written to
~/.config/tada/credentials.json (or $XDG_CONFIG_HOME/tada/credentials.json)
with mode 0600 — the same XDG-style location on every platform; %APPDATA% is
not used. On Windows 0600 is a no-op beyond the read-only bit, so protection
comes from the ACLs your user profile already grants.
logout removes whatever is stored locally. There is currently no
server-side session revocation: a stolen credentials file remains valid at
the login service until it naturally expires. logout only stops this
machine from presenting it.
render-bundle renders a prepared bundle with no network access. Its --encoder
default is libx264, which runs anywhere; pass --encoder h264_nvenc for NVIDIA
hardware encoding. Run travel-animator render-bundle --help for the full flag
reference.
MCP server
The mcp extra adds travel-animator mcp, a stdio MCP server that lets an AI
assistant do the whole job for you: plan a route, tune how the animation looks,
and render the video. A typical MCP client configuration:
{
"mcpServers": {
"travel-animator-mcp": {
"command": "travel-animator",
"args": ["mcp"]
}
}
}
Run travel-animator login in a terminal first — tools that need a credential
fail with a clear message telling you to do so, and auth_status lets an
agent check before it builds a trip it cannot render.
Licence
travel-animator is published under a limited use licence, not an open-source
licence. In short: you may install and run it unmodified to prepare and
render Travel Animator content and to talk to Lascade's services. You may not
redistribute it, modify it, or build a competing service with it. The full
terms ship inside the package at tada_render/LICENSE.
The bundled fonts (SIL Open Font License 1.1) and flag artwork (MIT) are
third-party assets under their own licences, which that restriction does not
touch. Their notices and full licence texts are in
tada_render/THIRD-PARTY-NOTICES.md.
For redistribution or modification rights, contact Lascade.
Metadata
Release files for travel-animator 0.2.0a4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| travel_animator-0.2.0a4-py3-none-any.whl | Python 3 | none | any | Details for travel_animator-0.2.0a4-py3-none-any.whl |
Release files / travel_animator-0.2.0a4-py3-none-any.whl
| Download URL | travel_animator-0.2.0a4-py3-none-any.whl |
|---|---|
| Size | 10.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8474c8166d8eeee8b821cf320f04c696b1df182f36fbcf08de7d93b49d0adb18
|
|
BLAKE2b-256 checksum How to use checksums |
63239a509770bb500fe0d6c077f86c9623102aa53a72716ab5a4acd9ce632ec0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for travel-animator 0.2.0a4
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.