Your workflows. Your rules.

Trivox is a modular automation ecosystem for content creators, engineers, and small studios who live at the intersection of art, code, and publishing.

Today, Trivox is focused around Trivox Conductor – a content pipeline conductor that automates the boring glue between:

🎮 play / record → 🧹 organize → 🎬 edit → ☁️ export / publish

This GitHub organization is the home of Trivox’s open-source tooling — born not from theory, but from real-world pain points in content creation, creative tech, and modern workflows that blend games, storytelling, and automation.

Trivox isn’t a single plugin or script — it’s a growing suite of pipeline components designed to make content workflows more:

• reproducible
• automated
• less chaotic

Whether you're:

• Capturing gameplay with OBS + ReplayMod or other recorders,
• Organizing raw footage, renders, and thumbnails into clean session folders,
• Handing off media into editors like DaVinci or Premiere,
• Or wiring AI helpers for captions, summaries, or ideas…

Trivox is here to support you with developer-first, creator-friendly building blocks.

Trivox Conductor is the flagship project in this org.

It’s a modular desktop framework (Python + Qt) that:

• 🎮 Orchestrates capture sessions

  • Connects to tools like OBS and game capture setups.
  • Records session manifests so each run is reproducible.

• 🧹 Watches and organizes output

  • Listens to output folders (game renders, screenshots, exports).
  • Moves and renames assets into structured session folders.

• 🎬 Automates handoff

  • Prepares timelines / folders for editors (e.g., DaVinci Resolve, Premiere).
  • Can trigger scripts to open projects or pre-load media.

• 🔔 Notifies you when things happen

  • Desktop / in-app notifications.
  • Hooks for Discord / webhooks so you know when a render or upload is done.

Under the hood, Conductor uses:

• A plugin system (capture, watcher, handoff, notifications, AI, etc.).
• An event bus so modules can react to what’s happening in your pipeline.
• Profile-based configuration so you can define different workflows (e.g., Minecraft devlog, coding session, short-form clip recording).

This organization will host (and already is hosting) things like:

• Trivox Conductor (core app) – The main content pipeline conductor.
• Core Engine & Libraries – Shared Python packages, event bus, settings, logging.
• Modules & Integrations – Capture adapters, folder watchers, handoff logic, Discord/webhook integrations, and (later) AI helpers.
• CLI Tools – Command-line workflows for creators and coders who want automation without the GUI.
• Experimental Repos – Prototypes to test new creative patterns and pipelines.
• Docs & Templates – Guides, pipeline blueprints, and examples.
• Private / WIP Tools – Some experiments will remain internal until they’re ready.

Every piece of Trivox starts with a real, painful workflow problem — usually uncovered while:

• recording gameplay/devlogs,
• managing messy media folders,
• stitching together OBS, editors, cloud storage and social media,
• or building internal tools for creative teams.

We believe the best tools are:

• Easy to extend – plugin-based, event-driven, and scriptable.
• Dev-first, but creator-friendly – powerful under the hood, approachable in the UI.
• Modular, versioned, and local-friendly – runs on your machine; cloud is optional.
• Respectful of your process & privacy – you stay in control of your data and flow.

Trivox is in active development, with the first focus on:

• A usable MVP of Trivox Conductor for gameplay + coding session capture.
• Core modules: capture, watcher, handoff, and notifications.
• A clean foundation so other creators and devs can extend it.

Follow @alexsc6955 for updates, or ⭐️ the repos as they become public.

Trivox was created by Santiago Rincón, a senior Python developer focused on automation and creative tooling.

This ecosystem is shaped by:

• real-world experience in VFX/games/content pipelines,
• late-night experiments,
• and a stubborn drive to turn content chaos into something you can actually control.

We’re especially interested in:

• Creators who want to automate their content pipelines.
• Developers who enjoy building clean, extensible systems.
• Studios / indie teams who need “big studio” pipelines on a smaller scale.

Say hi via:

Each repo defines its own license.
Most public tools in this org will be available under the MIT License.