Reported issues for talkback

Pod holds 9 of 9 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to talkback.

Most discussed

Master track devices return empty parameters — set_device_parameter fails

Description

get_track_details returns "parameters": {} for all devices on the master track (both third-party and Ableton native). This causes set_device_parameter to fail with:

Cannot read properties of undefined (reading 'find')

Steps to reproduce

Place Ableton native devices (EQ Eight, Glue Compressor, Limiter) on the master track, before the Talkback bridge device
Call get_track_details for the master track — devices are listed but all have "parameters": {} 3

Read the thread · 2026-03-23 · closed · external user · 7 comments

v1.8 amxd download actually contains bridge 1.7.3 — get_spectral_snapshot times out

Summary

The file at https://talkback.createwcare.com/downloads/talkback-bridge-v1.8.amxd actually contains bridge version 1.7.3, and get_spectral_snapshot times out on this device.

Environment

OS: Windows 11
Ableton Live 12 Suite (with Max for Live)
talkback-mcp: latest from npm (npx -y talkback-mcp, server v0.1.13)
M4L device: downloaded from the official link above

Steps to reproduce

Download talkback-bridge-v1.8.amxd from the official downloads page, drag ont

Read the thread · 2026-08-03 · open · external user · 2 comments

Write support: rename tracks and set track colors via MCP

Currently the Talkback MCP only supports read operations and a limited set of writes (device parameters, routing, device bypass). There's no way to rename tracks or set track colors programmatically.

Requested operations:

rename_track(track_name, new_name) — rename any track or group
set_track_color(track_name, color) — set track color (Ableton color index or hex)

Use case:

When using Claude or another LLM to analyze a session, the assistant can identify organizational

Read the thread · 2026-03-28 · open · external user · 2 comments

Wrong Node.js runtime picked up by Claude Desktop

Environment

macOS
Claude Desktop (configured via claude_desktop_config.json)
Node.js managed via nvm

Description

When configuring talkback-mcp using the standard npx command in claude_desktop_config.json, Claude Desktop fails to start the MCP server because it resolves node/npx from its own restricted PATH, which might pick up an old nvm-managed Node version instead of the user's active one.

This causes one of tw

Read the thread · 2026-03-20 · closed · external user · 2 comments

Docs: expand 'Other MCP clients' with Cursor and Windsurf config examples

Context

Cursor and Windsurf have large user bases with significant overlap in the music-tech space. Currently, non-Claude MCP client users get a single paragraph: "Point your client at npx -y talkback-mcp." No config examples, no file paths, no troubleshooting.

Problem

Claude Desktop gets full JSON config, file path locations, nvm/fnm warnings, and troubleshooting
Cursor/Windsurf/Codex users get one sentence
The add-mcp tool is mentioned but never explained — what is it? Why s

Read the thread · 2026-03-20 · closed · 1 comment

Docs: non-technical onboarding — Node.js wall and 'What is MCP?' explainer

Context

The primary audience for talkback includes music producers who may have never opened Terminal. The current docs assume familiarity with Node.js, npm, and MCP — creating a significant barrier for non-technical users.

Problems

1. The "Node.js wall"

A producer who's never used Terminal sees curl -fsSL ... | bash with no frame of reference
The installer's "Install it from: https://nodejs.org" message is too bare — a producer doesn't know what "LTS" means or which download

Read the thread · 2026-03-20 · closed · 1 comment

Docs: add 'Verify your setup' section with visual examples

Context

After setup, users have no way to verify the connection is working until they open Claude Desktop, start a conversation, and try a prompt. There's no visual reference for what success looks like at any step.

Problems

No verification step — if something is broken, there's a long feedback loop before the user discovers it
No visuals — the docs never show what a working talkback session looks like (M4L device green indicator, Claude Desktop hammer icon with tools, a s

Read the thread · 2026-03-20 · closed · 1 comment

Add curl installer to npm README as primary install path

Context

The npm README (README.md in this repo, displayed on npmjs.com) doesn't mention the curl one-liner installer at all. Someone discovering talkback on npm gets a worse onboarding than someone finding it on the website.

Problem

Website getting-started leads with curl -fsSL https://talkback.createwcare.com/install.sh | bash as the recommended path
npm README leads with manual M4L device download → manual JSON config
These tell different stories — the npm README should matc

Read the thread · 2026-03-20 · closed · 1 comment

Most recent

Installer: stop swallowing npm stderr, print direct M4L download URL

Context

The curl installer (scripts/install.sh and served at talkback.createwcare.com/install.sh) works correctly but has two small DX issues.

Problems

1. npm stderr is swallowed

Line 74: npm install -g talkback-mcp 2>/dev/null hides diagnostic output. If install fails for a reason other than permissions (network issue, registry down, disk full), the user only sees "npm install failed" with a misleading sudo suggestion.

Fix: Remove 2>/dev/null or redirect stderr to a te

Read the thread · 2026-03-20 · closed · 1 comment

The remaining reports are on the project's issue tracker.