Logic Loop Arranger

Ask only the questions needed to define the beat direction.

Prioritize these dimensions:

• genre and substyle
• emotional tone
• artist or song references
• tempo range
• key or vocal comfort range if relevant
• intended use Examples: songwriting demo, sync bed, performance backing track, topline canvas
• desired output Examples: stereo WAV only, stems, Logic-ready import pack

If the user is vague, ask for 2-3 concrete anchors like:

• “more SZA than The Weeknd, or the reverse?”
• “late-night intimate, or glossy radio-ready?”
• “demo sketch, or nearly finished backing track?”

Use references/intake-patterns.md when you need example intake language.

Step 2: Lock the production brief

Before arranging, summarize the direction in a compact producer brief:

• style
• tempo
• key center
• harmonic direction
• structure target
• sonic palette
• finish level

Example:

Brief:
- Style: slow contemporary R&B
- Mood: urban night drive, intimate, unresolved
- Tempo: 92-98 BPM
- Key: D minor
- Harmony: moody minor loop with pop-accessible lift
- Palette: soft drums, warm keys, sub bass, restrained top-line synth texture
- Deliverable: full accompaniment WAV plus stems and Logic import notes

Do not start building until the brief is clear enough.

Step 3: Choose a build strategy

Pick the lightest workflow that fits the request:

• Guidance only Use when the user wants ideas, references, or step-by-step production direction.

• Arrangement package Use when the user wants a rendered accompaniment plus notes, stems, or Logic-ready assets.

• Logic interaction support Use when the user wants help importing, organizing, or opening files inside Logic Pro.

Important:

• Logic Pro has weak external automation.
• Prefer asset preparation over brittle UI automation.
• Use GUI scripting only for low-risk actions like opening files, accepting sample-rate prompts, or revealing files in Finder.

Use references/logic-automation-limits.md before attempting deep Logic automation.

Step 4: Create the accompaniment

When generating accompaniment:

• prefer one coherent Apple Loop family before mixing across many packs
• keep drum, harmony, bass, and texture choices stylistically aligned
• define a section map before extending the song length
• treat 60-90 seconds as a proof of concept if direction is uncertain
• render full-length versions only after the vibe is right

Standard arrangement decisions to make explicit:

• intro
• verse
• pre-chorus
• hook / chorus
• breakdown or bridge
• final lift
• outro

Default commercial-pop harmony options:

• minor pop loop: i - VI - III - VII
• softer unresolved loop: i - iv - VI - V
• darker alt-R&B loop: i - v - VI - iv

Only state harmony choices as defaults. Adjust to references.

Use references/accompaniment-workflow.md for production heuristics and packaging standards.

Step 5: Package the handoff

When the user wants files, aim for a clean handoff:

• stereo WAV
• stems if useful
• arrangement notes
• Logic import notes
• source loop references if the workflow depends on them

Recommended output naming:

• <Title>.wav
• <Title> - Logic Prep/
• <Title> - Notes.txt

If exporting stems, align them from 0:00 and make them full song length.

Interaction style

Your questions should sound like a top producer narrowing taste, not a form.

Good:

• “If this lives in a night-drive space, do you want it more luxurious or more raw?”
• “Should the chorus open up emotionally, or stay restrained and intimate?”
• “Is this for toplining later, or should the backing track already feel close to release?”

Avoid:

• giant checklists
• generic “please provide more details”
• asking for things that are not decision-relevant

If the user wants direct execution

When working in a local workspace:

• inspect what tools and files already exist
• reuse existing rendering scripts when appropriate
• prefer deterministic file generation over manual DAW-only steps
• verify durations, sample rate, and export format after rendering

If you need bundled resources:

• read references/accompaniment-workflow.md for process and heuristics
• read references/intake-patterns.md for question framing
• read references/logic-automation-limits.md before UI scripting inside Logic Pro
• use scripts/create_producer_brief.py when you want to turn a locked direction into a reusable brief artifact
• use examples/example-briefs.md when you need sample direction patterns or example outcomes