@miadi/termux-motion
v0.2.0
Published
An Android phone in Termux takes the stage as the movement sender — the succession of the deprecated iOS MotionSender. Casts device sensors by role (linear acceleration, gyroscope, orientation), normalizes them into the nine-channel movement frame contrac
Downloads
397
Readme
@miadi/termux-motion
An Android phone in Termux takes the stage as the movement sender — the
succession of MotionSender, the deprecated iOS app that carried the Miadi
Episode 083 landbase practice (body-worn device → /wek/inputs → Wekinator).
- Sensors cast by role, never by hardcoded name: linear acceleration (fallback: raw accelerometer, declared), calibrated gyroscope, orientation. The casting is carried on the source and lands in any score recorded from it.
- The bridge's measured dialect, spoken correctly: pretty-printed JSON
cycles (not JSONL), a
{}warm-up emission, per-cycle partial sensor keys, E-notation numbers — brace-balanced assembly, last-note holding per role. - Normalized into the nine-channel frame contract of
@miadi/movement-conductor: m/s² → g, deg → rad, device attitude[azimuth, pitch, roll]reordered into channels[roll, pitch, azimuth].
The command
# Perform toward a Wekinator and keep the score as a TLID-named take:
termux-motion-send --host gaia --port 6448 --fps 10 --record
# Offline practice — score only:
termux-motion-send --record --duration 60
# What would this device cast?
termux-motion-send --listEnvironment defaults: MIADI_MOVEMENT_OSC_HOST, MIADI_MOVEMENT_OSC_PORT,
MIADI_MOVEMENT_FPS. Requires the Termux:API app and termux-api package
(termux-sensor on PATH).
Specification of record: rispecs/termux-motion.spec.md in
miadisabelle/gmtermux.
