Remote + Hybrid Collaboration Ideas | ISMIR 2026

Concept: a remote artist guides modal direction and form, without trying to play in sync.
Roles: remote composer or tradition bearer (modal cues); UAE-based performers (realization and ornamentation); optional technologist (cue system).
Latency Strategy: cues land at phrase boundaries or section changes; local performers choose the exact moment of entry.
Possible Technologies: web cue interface, OSC or MIDI to a shared display, simple chat fallback, optional machine listening to track density or modal area.
Example Realization: a remote artist steers an oud, voice, and percussion set through a modal arc using prompts such as "linger", "thin texture", "modulate", and "open space for voice".
Local Support Requested: 1 to 3 performers, cue display, one short rehearsal to agree on vocabulary.

Concept: build a piece where responses arrive late on purpose and become part of the form.
Roles: remote responders (audio, gestures, text prompts); local ensemble (hosts the majlis, sets tempo and transitions); optional moderator.
Latency Strategy: responses are accepted in a time window (for example, 5 to 20 seconds) and placed as echoes, overlays, or interruptions.
Possible Technologies: streaming + capture, shared clock, queued playback, message board for prompts, simple sampler for incoming audio.
Example Realization: local performers hold a groove; remote participants send short phrases that get replayed and reinterpreted one cycle later.
Local Support Requested: 2 to 5 performers, stable streaming, a laptop for capture and playback, and a brief soundcheck.

Concept: remote input shapes structure and pulse, while local performers keep feeling grounded.
Roles: remote artists (pulse or pattern proposals); local rhythm section (locks groove); optional conductor or cue lead.
Latency Strategy: remote changes apply on the next cycle or marker, not immediately; local groove never waits for packets.
Possible Technologies: shared metronome map, cue cards, OSC tempo messages, click track for the local lead only, and visualization of upcoming changes.
Example Realization: remote artist sends a sequence of tempo curves and accent patterns; local percussion interprets them as groove variations.
Local Support Requested: rhythm-focused performers, one person to run cues, and rehearsal time to define cycle lengths.

Concept: remote processing and local techniques act as a single evolving instrument.
Roles: local tradition bearer(s) (primary sound); remote technologist or musician (processing and control); local engineer (routing).
Latency Strategy: avoid tight timing by processing sustained material, phrase-level sends, or periodic "effect scenes".
Possible Technologies: remote-controlled effects rack, live coding, networked plugin host, stems sent to a remote processor and returned as textures.
Example Realization: an oud line feeds a remote granular patch that returns a shifting drone; the performer reacts to the returned layer as a partner.
Local Support Requested: audio interface, routing support, monitors, a short technical rehearsal.

Concept: collect contributions asynchronously, then realize them live in Abu Dhabi.
Roles: remote contributors (phrases, samples, instructions); local performers (curate and perform); local technologist (assembly and playback).
Latency Strategy: fully asynchronous creation; performance runs off a fixed structure with room for live variation.
Possible Technologies: shared folder, lightweight score template, web form submission, simple playback system, and optional MIR to index and select clips.
Example Realization: over two weeks, contributors submit short motifs tagged by mood or maqam; local ensemble performs a structured collage with live transitions.
Local Support Requested: performers, playback laptop, time to curate submissions before the conference.