# 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](/support/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](/features/tools#ppal-library) (Live
12.4+), but it cannot read or set the parameters inside a third-party VST/AU
plug-in.

::: tip Workaround: map the parameters you need

Map them onto the Live plug-in device with Live's
[Configure mode](https://www.ableton.com/live-manual/12/working-with-instruments-and-effects/#plug-in-configure-mode)
— expand the device, click **Configure**, then click 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.

:::

::: tip 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.

:::

## Automation and Envelopes Are Not Supported

Producer Pal cannot read, create, or edit arrangement automation or clip
envelopes — parameter values that change over time. Track and device parameters
like volume, pan, sends, and knobs can be set to static values, but not
automated.

## 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 (including Drum Rack pads) — but it cannot listen to,
analyze, or transcribe the audio itself. No detecting notes, key, or tempo from
a waveform; no audio-to-MIDI; no synthesizing audio from scratch.

::: tip 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](/guide/skills#companion-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.

::: tip 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. Nothing to do on your side — just expect a row of clips
instead of one long one.

:::

## 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.

---

For what Producer Pal _does_ do, see [Features](/features) and the
[Tool Reference](/features/tools).