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

SensorSynthFM:
Desk Research

FM SynthesisExpressive TouchDMI MappingPassive SensingAUv3 WorkflowCognitive Load

What This Research Can and Cannot Claim

The research is useful because it narrows the build question. It is not a launch argument. App listings, academic papers, product pages, forum threads, and trade coverage can show adjacent products and design constraints. They cannot prove that musicians want this exact instrument.

Supported

FM, touch expression, host workflows, and mapping literature all point to a credible design space.

Not proven

No source here validates demand, product-market fit, accessibility outcomes, or finished prototype quality.

Build implication

The first demo should answer one interaction question clearly before adding product breadth.

The Working Question

The strongest version of the project is not simply “FM on iPad.” That already exists in several forms. The stronger question is whether the iPad can make FM feel more physical: tilt changes timbre, proximity or light shifts modulation, touch gives intent, and the screen explains what changed before the sound feels arbitrary.

What the Source Set Says

1. The test

SensorSynthFM is not trying to prove a market. It is trying to test whether FM synthesis becomes more playable when a few mapped sensors, touch actions, and visual cues replace a dense editor as the performance surface.

2. The landscape

These references show adjacent FM apps, expressive instruments, and hosts. They do not establish whether sensor-driven FM is absent from the iPad market.

3. FM on iPad

FM gives the project a sharp sound identity, but it also creates the interface problem. A small demo should not dump the operator matrix onto the performer.

4. Touch expression

GeoShred, Animoog Z, Orphion, and MPE practice show that iPad performance can be serious. SensorSynthFM should borrow that seriousness without pretending it already matches those instruments.

5. Workflow

A future product has to fit AUv3, looping, host recall, and tempo-sync realities. The thesis demo should still keep sequencing secondary until the sensor-to-FM relationship works.

6. Passive sensing

The sensor layer is the reason for the project to exist on iPad. It has to feel bounded and readable, not like random environmental noise wearing a musical name.

7. Visual legibility

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 best version is deep enough to reward practice and simple enough that the first cause-and-effect relationship is obvious.

What This Changes for the Thesis Demo

The immediate target is not a bigger synth. It is a smaller, clearer proof: sensor input changes FM timbre, the screen explains the change, and the result survives a short musical demo.

  • Build one integrated screen before chasing a larger product surface.
  • 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 are musically defensible and which ones are only interesting on paper.

Selected Source Trail

The links below are a focused argument trail through FM synthesis, touch instruments, passive sensing, and performance workflow. They give readers public references for the design decisions without turning the page into a link dump.

Source identities, topics, and selected notes were checked on October 14, 2026. App listings, product pages, and forum discussions can change. The broader source atlas follows this selected trail.

FM theory and iPad FM

These sources define the sound-engine side of the research: what FM is, where the DX lineage matters, and which iPad products already cover adjacent ground.

Expressive touch instruments

These sources keep the iPad surface from being treated as a mouse replacement. The serious precedent is playable touch, not better parameter editing.

Mapping, passive sensing, and new instruments

This cluster gives SensorSynthFM its design spine: the mapping is part of the instrument, and more inputs only help if the relationship stays learnable.

Performance workflow and sequencing

These sources keep the project honest about where iPad instruments actually live: hosts, loopers, routing tools, modular environments, and tempo-sync systems.

Technical stack and cognitive load

This cluster turns the research into build constraints: AUv3 discipline, latency awareness, and an interface that explains cause and effect quickly.

Linked Source Atlas

This atlas puts the broad set of linked public references on the page by topic. Readers can scan the full field before deciding which references matter to the build.

The atlas contains 292 distinct linked destinations across 368 topic placements. Links whose source identity could not be established were left out. A source can appear in more than one topic; inclusion does not verify every claim it makes.

292linked public URLs
368topic placements

FM synthesis and iPad instruments

82 sources

FM theory, DX lineage, iPad synth products, and adjacent instrument references that define the sound space.

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 the actual workflow ecology around iPad instruments.

iPadOS audio, AudioKit, AUv3, MIDI, and latency

62 sources

Implementation-facing 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. General interface research is background, not validation of this instrument.

Accessible musical interfaces

2 sources

Research on inclusive music practice. These sources do not establish accessibility outcomes for SensorSynthFM.

Background and source indexes

29 sources

Artist profiles, instrument history, research indexes, and adjacent technical context. Indexes and profiles are not substitutes for individual studies.

Source labels and summaries were reviewed with AI assistance.