Media

Audio to Multitrack MIDI (Draft)

Split a full mix into stems (drums/bass/other/vocals) and transcribe each to MIDI — a multi-track starting point for transcription

file· File resultOpen tool

Quick start

Call this tool from your code in three languages.

cURL

# 1) Request a presigned URL → returns { uploadUrl, storageKey }
curl -X POST 'https://api.elysiatools.com/api/upload/presign/audio-to-multitrack-midi' \
  -H 'Content-Type: application/json' \
  -d '{"filename":"audioFile.ext","contentType":"application/octet-stream","size":12345}'

# 2) PUT the file bytes directly to the presigned uploadUrl
curl -X PUT '<presigned uploadUrl>' \
  --data-binary @/path/to/file.ext

# 3) Call the tool, passing the returned storageKey for each file field
curl -X POST 'https://api.elysiatools.com/en/api/tools/audio-to-multitrack-midi' \
  -F 'audioFile=/public/processing/smoke-test-tone.flac' \
  -F 'stems=all' \
  -F 'onsetThreshold=0.5' \
  -F 'frameThreshold=0.3' \
  -F 'minNoteLength=6' \
  -F 'includePitchBend=true'

API reference

Send a POST request with your inputs as JSON. File parameters require a separate upload first.

Endpoint

HTTP

POST https://api.elysiatools.com/en/api/tools/audio-to-multitrack-midi

Parameters

Name	Type	Required	Description
audioFile	fileupload required	Yes	—
stems	select	No	—
onsetThreshold	number	No	—
frameThreshold	number	No	—
minNoteLength	number	No	—
includePitchBend	checkbox	No	—

File-type parameters must be uploaded first via POST /upload/audio-to-multitrack-midi, then the returned filePath is passed to the corresponding file field.

Response format

File result

JSON

{
  "filePath": "/public/processing/randomid.ext",
  "fileName": "output.ext",
  "contentType": "application/octet-stream",
  "size": 1024,
  "metadata": {
    "key": "value"
  },
  "error": "Error message (optional)",
  "message": "Notification message (optional)"
}

MCP integration

Add this tool to your Model Context Protocol server so AI agents can list and call it.

Server configuration

Add this block to your MCP client configuration:

mcp.json

{
  "mcpServers": {
    "elysiatools-audio-to-multitrack-midi": {
      "name": "audio-to-multitrack-midi",
      "description": "Split a full mix into stems (drums/bass/other/vocals) and transcribe each to MIDI — a multi-track starting point for transcription",
      "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=audio-to-multitrack-midi",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

List available tools

After connecting to the SSE endpoint, list the exposed tools:

tools/list

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Call this tool

Invoke the tool by its id, passing arguments built from its parameters:

tools/call

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "audio-to-multitrack-midi",
    "arguments": {
  "audioFile": "/public/processing/smoke-test-tone.flac",
  "stems": "all",
  "onsetThreshold": 0.5,
  "frameThreshold": 0.3,
  "minNoteLength": 6,
  "includePitchBend": true
}
  }
}

Chain multiple tools in one session with a comma-separated toolId list, e.g. /mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp (max 20).

File parameters accept a public file URL only (https://…). Local paths, data: URIs, and Base64 strings are not supported.

Questions or issues? Contact [email protected]