Marvis QT
Marvis_QT is a modular audio visualizer designed for players and multimedia applications. It offers runtime plugins (.vismod) for creative visualization modes (spectrum, particle, plasma, moiré, oscilloscope, etc.). Individual plugins are now independently loadable, configurable and localized to Czech (CZ)
What the project solves
Marvis_QT is a modular audio visualizer designed for players and multimedia applications. It offers runtime plugins (.vismod) for creative visualization modes (spectrum, particle, plasma, moiré, oscilloscope, etc.). Individual plugins are now independently loadable, configurable and localized to Czech (CZ)
How the application works and what it is for
Product overview
Marvis _ QT is a high-performance visualization engine designed for realtime transformation of sound waves into complex visual patterns. Application combines the benefits of built-in native modes with flexibility runtime .vismede of plugins.
Thanks to the support of profiles (Standalone, MaVi, ADB), Marvin can continuously adapt to the role of a music player or a separate VJ platform. The key element of version 0.2.5.x is Global-First Asset Lookupthat unifies visual style across the entire IPCS ecosystem.
UI workflow
Marvin uses the "Hybrid interface" - the rendering area is clean, while controls are available via RMB (Right Mouse Button) or keyboard shortcuts.
- Work with fashion: Menu Modes offers a list of built-in effects and detected plugins.
- Overlay panels: After induction (e.g. The Borders panel is displayed by the F1 button for Help), which can be moved by pulling the title bar.
- Real-time configuration: Plugin specifications (e.g. Sensitivity) can be changed when running without breaking the render.
Keyboard abbreviations
| Instant mode switch on the given index. | |
| Toggle Fullscreen. | |
| Display the main menu under the mouse. | |
| Close the top overlay panel. | |
| Change in global opacity (transparency). | |
| Safe Quit (saving status and ending). |
Screenplay and workflow
Workflow: Professional VJ setup
- Run with Profile on the second monitor.
- Configure .
- Use Full screen mode.
- In the menu disable mouse cursor (Settings).
Workflow: The development of the plugin
- Open .
- Edit the code and save it under a new name.
- In the application to select Plugins → Reload Plugins.
- Use Benchmark panel for checking the performance of the new code.
Formats + backends
- Audio: PCM (over ). Support to Stereo i Mono (duplication of the stream).
- Visual: RGB / RGBA surfaces (Pygame). HW acceleration over SDL2.
- Icons: SVG (vector) with rasterization, PNG, WebP (if backend allows).
- Metadata: JSON for setting, .vismod (Python source) for plugins.
Troubleshooting + known limits
- Error: "No audio device found": Check if any other application holds an exclusive lock on the microphone.
- Error: "Module NotFoundError: pygame": Start in the relevant .venv.
- Limit: Maximum FPS is limited by the monitor's recovery frequency (if V-Sync is enabled).
FAQ
- How to add your own icon to the plugin?
- Insert SVG into with the name and state this name in the plugin to .
- Does he support Marvis ASIO?
- Yes, over backend if ASIO drivers are installed in the system.
GPU runtime · September 2026
The formal release remains 0.2.5.1, but the runtime has since been through extensive GPU tuning. ModernGL routes use Native _ gpu or gpu _ bridge and send the result, where possible, through direct _ present without unnecessary reading of the image back from GPU to CPU. CPU / Pygame branch remains compatible fallback, not default architectural target for GPU modes.
The Benchmark Set covers 52 visualization modes. In the last measurement, 43 / 52 of the pipeline was checked and 34 of the modes held at least 60 FPS in p90 at 1280 × 720. The 120 + FPS target remains the subject of optimisation; therefore, the profile separates the completed migration of rendering routes from further power tuning.
Part of the work is also the unification of plugins, isolation of modes, removal of unnecessary GPU → CPU copying and maintenance of full resolution. Automatic resolution reduction belongs only to the optional low-power fallback.
