Skip to main content
← SensorSynthFM
Desk Research · Music Technology2026Active Build

SensorSynthFM:
Desk Research

FM SynthesisExpressive TouchDMI MappingPassive SensingAUv3 WorkflowCognitive Load

The Working Question

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.

What the Source Set Says

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.

2. Existing apps

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.

3. FM on 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.

4. Touch expression

GeoShred, Animoog Z, Orphion, and MPE, which gives each note its own expression, show that the iPad can be a serious performance instrument.

5. Workflow

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.

6. Passive sensing

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.

7. Showing the mapping

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.

8. Cognitive load

The first cause-and-effect relationship should be obvious to a new player, and the instrument should still reward practice.

What This Meant for the Thesis Demo, July 2026

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.

  • Build one integrated screen before anything larger.
  • Make two or three sensor-to-FM mappings audible, visible, and explainable.
  • Treat preset browsing, full MPE architecture, integrated sequencing, and store readiness as later work.
  • Use the demo to find which mappings hold up musically.

Selected Source Trail

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.

FM theory and iPad FM

What FM is, the Yamaha DX line it comes from, and which iPad products already do something similar.

Expressive touch instruments

Instruments built for playing by touch.

Mapping, passive sensing, and new instruments

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.

Performance workflow and sequencing

How iPad instruments are used with hosts, loopers, routing tools, modular environments, and tempo sync.

Technical stack and cognitive load

Build constraints: the AUv3 plug-in format, latency, and an interface that shows cause and effect quickly.

Linked Source Atlas

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.

292linked public URLs
368topic placements

FM synthesis and iPad instruments

82 sources

FM theory, the Yamaha DX line, iPad synth products, and related instruments.

Touchscreen expression and glass-interface constraints

73 sources

Playable touch surfaces, MPE, Apple Pencil, glass-instrument limits, and expressive iPad performance.

Gesture mapping and sensor-based instruments

41 sources

Mapping research, motion control, sensor techniques, and instruments that connect physical input to sound.

Performance workflow, looping, and sequencing

46 sources

Host apps, loopers, routing, sequencing, tempo sync, and how iPad instruments are used with them.

iPadOS audio, AudioKit, AUv3, MIDI, and latency

62 sources

Developer references for iOS audio, AudioKit, AUv3, MIDI, latency, and framework decisions.

Visual feedback, interface design, and learning

33 sources

Visual and haptic feedback, touchscreen controls, instrument learning, and cognitive-load references.

Accessible musical interfaces

2 sources

Research on inclusive music practice.

Background and source indexes

29 sources

Artist profiles, instrument history, research indexes, and related technical context.

Source labels and summaries were reviewed with AI assistance.