Current System
- Runs Rekordbox. - Runs Pose Coach / camera viewer. - Runs AirDeck bridge. - Owns keyboard/MIDI dispatch. - Owns the final safety gate. - Can work from camera pose without Sony sensors.
Full Public Reader
Current System
Working Direction
The architecture should be:
K11 camera/Bolt pose -> K11 AirDeck bridge -> Rekordbox
|
+-> recordings/training data
Mac4 sensors/mocopi/Mega -> Unity/DYK visuals
|
+-> optional MotionMix BodyTruth source
MotionMix hub -> shared body state, session storage, future fusionCurrent Reality
K11 is the DJ machine.
- Runs Rekordbox.
- Runs Pose Coach / camera viewer.
- Runs AirDeck bridge.
- Owns keyboard/MIDI dispatch.
- Owns the final safety gate.
- Can work from camera pose without Sony sensors.
Mac4 is the visual/sensor integration machine.
- Runs Unity/DYK.
- Receives Sony mocopi when sensors are on.
- Feeds Unity locally.
- May post mocopi state to MotionMix.
MotionMix is the shared hub and archive.
- Has recording/session infrastructure.
- Has BodyTruth contract direction.
- Has SensorLogger and iPhone-related data lanes.
- Should become the place where movement datasets are structured and queryable.
Current Constraint
Do not let Mac4, Unity, mocopi, or raw sensors send Rekordbox commands directly. They may visualize, record, or advise. K11 decides.
Current Correction
Mocopi must not be treated as required. If hand raise works with the camera, then camera-first AirDeck is valid. The full gesture library should be built around camera pose and then enhanced with optional sensors.
Promotion Decision
Promote into a technical note or architecture paper with implementation anchors.
Source Anchor
MotionMix/research/computational-choreography-nko-2026-05-27/02-architecture/current-system.md
Detected Structure
Method · Architecture