1. The test
SensorSynthFM tests whether FM synthesis becomes more playable when a few mapped sensors, touch actions, and visual cues replace a dense editor.
FM on iPad already exists in several forms. The question I started with was whether the iPad can make FM feel more physical: tilt changes timbre, proximity or light shifts modulation, touch gives intent, and the screen shows what changed. On July 12, 2026 the demo changed to an iPad resting on a table.
SensorSynthFM tests whether FM synthesis becomes more playable when a few mapped sensors, touch actions, and visual cues replace a dense editor.
These references show related FM apps, expressive instruments, and host apps. I have not established whether a sensor-driven FM instrument already exists for iPad.
FM gives the project a distinct sound, and it creates the interface problem. A small demo should not put the whole operator matrix in front of the performer.
GeoShred, Animoog Z, Orphion, and MPE, which gives each note its own expression, show that the iPad can be a serious performance instrument.
A future product would have to work with AUv3 hosts, loopers, saved sessions, and tempo sync. The thesis demo keeps sequencing secondary until the sensor-to-FM relationship works.
The sensors are the reason for the project to exist on iPad. The player has to be able to tell what each sensor is doing.
The screen has to show which sensor is active, what it is changing, and how strongly it is changing it. If the mapping cannot be explained fast, it should be cut for the demo.
The first cause-and-effect relationship should be obvious to a new player, and the instrument should still reward practice.
The demo had to show one thing in a short piece of music: a sensor changes the FM sound and the screen shows why. It should answer that one question before anything else is added.
Source identities, topics, and selected notes were checked on October 14, 2026. App listings, product pages, and forum discussions can change. The full source atlas follows this selection.
What FM is, the Yamaha DX line it comes from, and which iPad products already do something similar.
Instruments built for playing by touch.
Research on mapping gestures and sensors to sound. The mapping is part of the instrument, and more inputs only help if the player can still learn the relationship.
How iPad instruments are used with hosts, loopers, routing tools, modular environments, and tempo sync.
Build constraints: the AUv3 plug-in format, latency, and an interface that shows cause and effect quickly.
The atlas contains 292 distinct links across 368 topic placements. Links whose source could not be identified were left out. A source can appear in more than one topic. I have not checked every claim each source makes.
FM theory, the Yamaha DX line, iPad synth products, and related instruments.
Playable touch surfaces, MPE, Apple Pencil, glass-instrument limits, and expressive iPad performance.
Mapping research, motion control, sensor techniques, and instruments that connect physical input to sound.
Host apps, loopers, routing, sequencing, tempo sync, and how iPad instruments are used with them.
Developer references for iOS audio, AudioKit, AUv3, MIDI, latency, and framework decisions.
Visual and haptic feedback, touchscreen controls, instrument learning, and cognitive-load references.
Research on inclusive music practice.
Artist profiles, instrument history, research indexes, and related technical context.
Source labels and summaries were reviewed with AI assistance.