Limitations

These are design boundaries, not bugs. They come from what the Live API and Max for Live expose, so they aren't waiting on a fix. For things that are broken or surprising, see Known Issues.

VST/AU Plug-in Internals Can't Be Controlled Directly

Producer Pal can open or close a plug-in's editor window and list the plug-ins you have installed (both Live 12.4+), but it cannot read or set the parameters inside a third-party VST/AU plug-in.

Workaround: map the parameters you need

Map them onto the Live plug-in device with Live's Configure mode by expanding the device, clicking Configure, then clicking the controls you want in the plug-in's window. Producer Pal can then set those mapped parameters like any other device parameter.

You map them yourself, up to 128 parameters, and not every plug-in parameter is mappable, so pick the ones that matter most.

Save the mappings in a rack, not a plug-in preset. Saving a preset for the plug-in device on its own loses the mappings (still true as of Live 12.4). Wrap the plug-in in a rack and save a rack preset instead. A rack preset keeps the mappings of every plug-in inside it.

Workaround: use Live's own devices

Live's instruments and effects expose every parameter, so anything built from them works fully: no mapping step, nothing to keep in sync.

Some Moves Drop Clip Envelopes

Envelopes you already have are safe through most edits: they live in the clip, so they travel with it. The exception is any move that has to re-create the clip (from its notes for MIDI, from its sample for audio), which leaves the envelopes behind:

• duplicating a clip onto or off a take lane
• moving an arrangement clip onto or off a take lane
• moving an arrangement clip to another track
• moving an arrangement clip back into a session slot

A move along a track's own arrangement lane is not affected. A re-created audio clip also loses any warp markers you edited by hand, and the result says which of the two applied.

Arrangement Automation Replaces the Lane Over the Clip

Live's API can't read or draw a track's arrangement automation directly. With the remote script, Producer Pal writes automation onto an arrangement clip by writing the track's automation lane over exactly that clip's span. That comes with limits:

• Producer Pal can't read the lane's points back (it can tell which parameters have a lane), or clear it. Writing again overwrites it over the clip's span, and the lane returns to its old value after.
• The clip is re-created to do it, so it comes back with a new ID.
• Moving an arrangement clip leaves its automation where it was.

Audio Content Can't Be Analyzed or Generated

Producer Pal can manage audio clips (set gain, pitch, and warp settings, change clip length, arrange clips in the Arrangement, and load and manage samples on Simpler instruments, Drum Rack pads included), but it cannot listen to or analyze the audio itself. No detecting key or tempo from a waveform, no synthesizing audio from scratch. The one audio-to-MIDI route is Live's own conversion of an audio clip to a new MIDI track (drums, melody or harmony), which needs the remote script.

Workaround: drive it from a coding agent

A coding agent runs outside Live, with a real runtime and a filesystem, so the companion audio skills cover the whole round trip today: synthesize audio from scratch, render a MIDI track or the entire mix to a file (macOS only), and analyze what comes back. That's the better home for it: synthesis is open-ended enough that an agent writing real code beats any DSL Producer Pal could teach it.

Looped Arrangement Clips Can't Be Lengthened in Place

An unlooped arrangement clip, MIDI or audio, is extended by moving its end. A looped one has no equivalent move. What plays is the loop region, so covering more of the timeline takes more clips.

Workaround: Producer Pal tiles them for you

Ask for a longer looped arrangement clip and Producer Pal duplicates and tiles it to fill the length. It sounds identical, but the result is a row of clips rather than one long one: a 2-bar clip stretched to 32 bars lands as 16 clips, and nothing in the API merges them back into a loop.

That's the default because each tile is a real copy, clip envelopes included.

Workaround: ask for one long clip instead (MIDI only)

If you'd rather have a single clip, say so. Producer Pal turns looping off, extends the clip, and writes the pattern out across the whole span. Bar copying does that in one call however many repeats you need.

The repeats are then real notes, not a loop, so changing the pattern later means changing every repeat. It stays the same clip, so its envelopes stay with it. Audio clips have no equivalent, since there are no notes to write.

Time Signature Changes Aren't Visible

Live lets you change meter partway through the Arrangement. Producer Pal can't see those changes. The Live API exposes a single song time signature (the meter at the playhead) and no list of where the changes are, so Producer Pal treats the whole timeline as one meter.

Two things follow, and both are silent:

• Arrangement bar numbers are wrong past the first change. In a Set that runs 16 bars of 4/4 and then switches to 3/4, asking for bar 17 lands on bar 13.
• The error moves with your playhead. The meter Producer Pal reads is whichever one is under the playhead, so the same request lands somewhere else depending on where the playhead was sitting when you asked.

Live's own API has the same blind spot in its bar-number lookup, which reports bar 22 for the position Live's ruler calls bar 17, so there is nothing to read back to catch the mistake.

Don't arrange with Producer Pal in a Set that changes meter

There is no workaround. If your Set changes time signature, keep Producer Pal away from arrangement positions: place and move clips in Live's timeline yourself.

Only positions on the song timeline are affected. Session clips are fine, and so are clip time signatures: each clip carries its own meter, which Producer Pal reads and sets normally. Arrangement clip positions, arrangement lengths, and locator positions are the parts that go wrong.

Tracks Can't Be Grouped or Ungrouped

Live gives Producer Pal no way to put tracks into a group or take them out. The AI can read groups and work with the tracks inside them, but making or breaking a group is up to you in Live.

One Drum Rack Pitch Map Per Track

Reading a track gives the AI a map of which MIDI pitch triggers which drum pad, so it can place your kick and snare by name instead of guessing. That map comes from the first Drum Rack on the track, including ones nested inside other racks, so if you layer several, the AI goes by the first one's pad names.

Backslashes in Names Read Back Changed

Producer Pal writes a backslash into a track, scene, clip or other name as written, and Live shows it correctly. But Max for Live changes it when Producer Pal reads the name back, so the AI sees a different name than the one in Live:

• macOS: the backslash is dropped. Kick\Snare reads as KickSnare.
• Windows: it reads as a slash. Kick\Snare reads as Kick:/Snare.

If the AI then writes that name somewhere else, the changed version is what gets saved. Leave backslashes out of names you want Producer Pal to work with.

File paths aren't affected in practice. A Windows sample path reads back with forward slashes (C:/Users/...), which Live accepts.

---

For what Producer Pal does do, see Features and the Tool Reference.