Creative technology / 2026

ExoAVT

Name: ExoAVT
Author: Filippo Galbo

Android video instrument with audio-reactive effects, editable timing, producer tags, and MP4 export.

The problem

Applying audio-reactive effects to a phone video involves importing media, tuning the visual response, and exporting a usable file from the same session.

My role

Android interface, media-processing engine, and export workflow engineering.

What I built

Installable Android beta
Audio-reactive video preview and MP4 export
Saved project and effect state

The result

An Android beta for processing imported media and exporting the result as a video file.

ExoAVT Android machine interface with media preview, effect controls, and export control

Statusactive

Evidencereleased

Record reviewed2026-08-15

ReleaseVersion 0.3.0-beta.41 / build 43

Implementation

How it works

Import video or photos and audio, combine visual effects, edit sound-guided timing, and add producer tags. The Android app saves reusable looks and exports H.264/AAC MP4 video.

Technical context and methods

The beta is distributed as a versioned APK with a checksum. The project includes screenshot baselines, JVM tests, and Android lint checks; physical-device verification has a separate scope.

Kotlin
Jetpack Compose
Media3
Android GPU effects
Audio analysis
Screenshot testing

Limitations

This release fixes a reproducible native particle-renderer crash during an Audio Motion drag, but the original phone report has no matching device log and is not claimed independently verified. Feral Lava's dark generated background is a separate source-mode behavior, addressed for new choices by the Footage default. Saved Generated projects are not silently migrated: choose Footage in Controls if you want the imported picture. If a crash recurs, report the device model, Android version, selected effects, and exact steps.
Beta40 adds new effect IDs and discrete print events that older builds may not understand. Keep an original project copy. Particle preparation and checkpoints share an 8 MiB CPU budget; discretionary render resources share a 64 MiB GPU budget. These are not total app-memory limits. Seeking may require cancellable preparation. Reduced-resolution fields and snapshots trade fine detail for bounded work. Emulator renders and exports do not establish physical-phone frame rate, thermal stability, HDR quality, or cross-GPU appearance.
New beta39 processors may not render in earlier builds; keep an original project copy. Motion Transport and Time Displacement use at most 32 reduced-resolution history samples at 30 Hz within a 640 × 360 box, with a shared 64 MiB resource budget. This can soften delayed detail. Stacked history increases seek preparation; upstream recursive Temporal Melt can require replay from the clip start. Accurate seeking may scan source timestamps, so longer files can take longer to prepare; Cancel remains available. Multiple-video-track files are not supported for accurate temporal preview. Raster Relief requires working vertex-texture sampling. Known Particle Reassembly and Raster Relief output formats up to 720P at nominal 30 fps request a higher 20 Mbps encoding rate to preserve moving detail, which can increase file size; higher or unknown formats retain the normal encoder policy. Encoder fallback and physical-phone quality still need testing. The existing paused-preview sizing issue remains. Beta41 addresses the reproduced redundant-composition replacement timeout; other player-release failures on physical devices remain unverified. No measured phone frame rate or thermal guarantee is claimed.
Acid Video Synth follows visible effect families in the supplied reference; it does not claim an exact reconstruction, new multi-frame echo, optical-flow simulation, or true codec datamoshing. Physical-phone visual acceptance, sustained frame rate, and thermal behavior remain unverified. Projects using beta38-only processors may not render in earlier builds; keep the original project copy.

Open ExoAVT Download beta APK Verify SHA-256