Support
Stable URL: https://midi-sink.vibetuned.com/support/ — referenced by the
store listings; it will not change.
The apps
Section titled “The apps”- iPad: midi-sink on the App Store (iPadOS and iOS 16 or later).
- Android: midi-sink on Google Play (Android 10 or later, OpenGL ES 3).
- macOS, Windows, Linux and the browser: the install page.
Where to ask
Section titled “Where to ask”- Bugs and feature requests: github.com/vibetuned/midi-sink/issues. Search first — the issue tracker is also the beta wave’s confusion log.
- Email: info@vibetuned.com for anything that should not be public (a device you cannot name, a recording you would rather not post).
- Discussions, performances, “is this expected?”: open an issue with the
questionlabel, or send a link to a recording — the gallery grows from what people play.
What to include in a bug report
Section titled “What to include in a bug report”- Platform and version. The version is in Settings → About on every
platform (it comes from the release tag, e.g.
1.0.0). Say which app: macOS, Windows, Linux, iPad, Android, or the web canvas and its browser. - The instrument and how it is connected (USB, network session, Bluetooth), or “fingers/pencil” for the Play surface.
- What you did, what you saw, what you expected. A short screen recording beats a paragraph.
- For MIDI problems on the tablets: Settings → Evidence flushes the
byte log (
midi_log.csv) and the session log into the app’s documents folder. Attach them — they contain only MIDI messages and timestamps, no personal data — and the analysers intools/will tell us what went wrong in seconds. The MIDI implementation chart is the contract they are checked against. - For visual problems on desktop: run with
--devand use--field-dumpif asked; the cross-backend field regression usually localises a rendering difference to one backend in one run.
Known limits, before you file
Section titled “Known limits, before you file”- Play mode exists on the eight keyed layouts and the theremin; the circle of fifths and the piano rolls are Marble-only by design.
- On the Galaxy Tab the S Pen’s palm rejection drops the fingers while the pen is near the glass, so the brass layouts’ valves and slide cannot be worked by a finger while the pen plays — a platform limit the iPad does not have (the instruments).
- The web canvas is Marble mode only — the instruments are overlays, a
replay there is the picture alone — and needs WebGPU (Chrome, Edge,
Safari 26, Firefox 141+) in a secure context —
https://orlocalhost. - Many MPE synths ignore polyphonic key pressure (0xA0); the Play surface’s “pull back to stir” axis is primarily a visualizer dimension.
- Prints are what touches the water: the live ripple shimmer is not in them, on purpose.
The changelog lists what each release fixed; the design notes explain why things are the way they are.
midi-sink 2.0.0-rc.5 · AGPL-3.0 · source
