Use your Co-Producer with confidence.

Requirements

• macOS 13 Ventura or later (Apple Silicon recommended)
• Logic Pro 10.7+ installed
• A built-in or external microphone (for voice mode — optional)
• Internet connection (for GPT responses; all Logic Pro automation runs locally)

Step 1 · Download & install

1. Click the Download Revocalize Co-Producer button on our website. A .dmg will save to your ~/Downloads folder.
2. Double-click Revocalize Co-Producer v0.2.23.dmg. A window opens showing the Revocalize Co-Producer icon next to an Applications folder shortcut.
3. Drag Revocalize onto the Applications shortcut. Wait ~5 seconds for the copy to finish, then close the window and eject the DMG from your desktop.

Step 2 · Launch the app

Open Applications in Finder and double-click Revocalize.

Step 3 · Approve keychain access

On first launch, macOS will show a keychain prompt asking for your Mac account password. You may see it up to three times in a row — that's normal, each prompt is for a different keychain entry.

Step 4 · Grant Accessibility permission

Revocalize uses macOS Accessibility to drive Logic Pro. Without it, no commands will execute.

1. On first launch you'll see a banner inside Revocalize: “Accessibility access required”. Click Open System Settings.
2. Return to Revocalize Co-Producer — the banner disappears and the app is ready.

Voice permissions (only if you use voice)

Two more permissions are requested on-the-fly the first time you use voice — you don't need to set them up in advance:

You can review or change every permission anytime in System Settings → Privacy & Security.

Open Settings (sidebar → gear icon) and walk through these panes:

Voice

• Wake Word — on-device listening so you can summon Revocalize hands-free while producing.
• Push-to-Talk — hold Right Option (⌥) to talk; release to send. No wake word needed.
• Text-to-Speech — pick Apple's built-in voices (free, offline) or OpenAI voices (requires API key).

About · Danger Zone

If you ever want a fresh start, Settings → About → Danger Zone → Clear All History & Sessions wipes chat history, command history, and confirmation allowlists. Irreversible.

The Studio tab is your main workspace. You have two equal input channels:

• Voice — tap the microphone, use push-to-talk, or say the wake word. You'll see a live transcript as you speak.
• Text — type into the prompt box and hit Return.

Revocalize speaks back using TTS (if enabled) and keeps a conversation history so you can say things like "rename that track to Bass" after creating it.

Studio Bot is a lightweight desktop companion for the same Co-Producer session you already use. It stays above Logic Pro and gives you a clear view of what the assistant is doing without covering your arrangement with the full chat window.

What Studio Bot shows

• Live status — see whether Co-Producer is understanding, inspecting, running, verifying, waiting for you, or finished.
• Progress and timeline — click the status bubble to expand the current plan, its completed steps, and elapsed time.
• Safety approvals — choose Approve & Run, review the full details, or cancel before a high-impact change begins.
• In-place controls — stop active work, open the full Assistant, hide the Pet, or collapse the detailed view.
• Recovery actions — retry a failed step or jump directly to the access and Logic recovery action the assistant recommends.

Show and customize it

• Open the Revocalize menu-bar icon and choose Show Pet whenever you want it visible.
• By default, Studio Bot appears automatically when a Logic automation starts. Change this in Settings → Assistant Companion.
• Choose a Small, Medium, or Large companion.
• Set feedback to Minimal, Standard, or Detailed, and optionally enable the completion sound.

Revocalize Co-Producer speaks the language of Logic Pro. Every capability below is available today — just tell it what you want.

🗂️ Project Management

• Create new projects — empty or from any built-in Logic template
• Save projects (as, in a specific folder)
• Close projects
• Import audio files into the Project Audio bin
• Inspect project status (tempo, key, time signature, running state)

🎚️ Track Operations

• Create Audio, Software Instrument, or Drummer tracks — single or in batches
• Name tracks on creation ("called Bass") or rename later
• Delete tracks by index or by name
• Inspect all tracks or drill into one
• Set volume in dB
• Set pan, including batch changes across several named tracks
• Mute / Unmute, Solo, and Record-arm tracks

🎵 Audio & MIDI Regions

• Add an audio region from a file in the Project Audio bin to any track at a specific bar
• Add an empty MIDI region to a Software Instrument track at a specific bar/length

⏯️ Playhead & Timeline

• Move the playhead to any bar or measure

📄 Templates

• Browse Logic's template library by category (Hip Hop, Electronic, Songwriter, etc.)
• Create a project directly from a template

🎛️ Supported Parameters

💬 General Conversation

Revocalize also answers general music-production questions and follows context across a session:

Use this when a production session needs to become easier to mix without losing the choices already made by the producer. The assistant looks at track names, types, placement, folders, stacks, routing, and other available signals before deciding where a track belongs.

What the organization pass protects

• Intentional folders and nested stacks that already express the arrangement.
• Summing structure, routing, automation, and the regions already on each track.
• Mixed-role stacks such as a production group containing drums, bass, and instruments. If changing one would be ambiguous, the assistant asks first.
• Single tracks that are already classified correctly. Standing alone is not a reason to move a track into UNKNOWN.

Recommended workflow

1. Open the Logic project you want to prepare.
2. Ask “Organize this session for mixing.”
3. Review the audit, proposed structure, and any questions about ambiguous groups.
4. Approve the plan only when the grouping matches your intent.

Describe the musical role rather than hunting through filters. Co-Producer can combine genre, instrument, tempo, key, and mood in one request, then keep the audition process conversational.

Search, audition, place

1. Ask for a sound, including any constraints that matter: instrument, genre, key, tempo, or mood.
2. Preview the result and say “next one” for another option.
3. When you find the right loop, tell Co-Producer to place it in the project.
4. Ask for an alternative when you want an A/B option; the original remains available for comparison.

Co-Producer can inspect the channel strip before changing it, reuse a suitable plugin that is already inserted, and build a processing chain from plugins available on your Mac. Mixer moves use the dedicated Logic control channel and are checked after execution.

Plugin-aware changes

• Inspect existing inserts and avoid adding an unnecessary duplicate.
• Discover compatible Logic or Audio Unit plugins installed on the Mac.
• Build ordered plugin chains and use sends or aux returns when the request calls for them.
• List, load, and save plugin presets, including presets inside folders.
• Target a named plugin when several editor windows are open.

Verified mixer changes

• Set exact volume values in dB across one track or a whole group.
• Pan several named tracks in a single request.
• Mute, unmute, solo, or record-arm tracks without relying on fragile screen positions.
• Verify the resulting mixer state in Logic before reporting completion.

MIDI Generation turns a sentence into playable parts. Ask for “deep-house drums at 124 with a sub bass and a pluck” and the Co-Producer generates the MIDI, creates a Software Instrument track per part with a meaningful name, and imports each part onto its matching track automatically.

Three ways to use it

• Generate. A fresh idea from a prompt — one part (“a funky bassline at 110 in A minor”) or a whole groove (drums + bass + chords + lead), each on its own track.
• Revise. Keep the conversation going — “make the bassline more syncopated and add a punchy kick” builds on the same idea rather than starting over, and re-imports the result.
• Improve. “Improve the pluck — give me 2 variations” analyzes the existing part, generates A/B options on new tracks, and mutes the original so you can compare. The original is never deleted.

How to use it

1. Type or speak what you want — include tempo, key, and vibe for best results.
2. The first generation takes up to a minute (the Co-Producer tells you up front). Each part comes back as its own .mid file.
3. Tracks are created and the parts imported automatically — then keep refining in the same conversation.

Ask “analyze this track” or “is my mix too harsh?” and the Audio Analyzer decodes the waveform and extracts real measurements — peak / RMS / crest, spectral balance across the frequency bands, dynamic range, noise floor — then translates them into plain-language issues and suggested processing.

What it detects

• Problems: clipping, sibilance, harshness, mud, boominess, thinness, an audible noise floor, and over-compressed or over-dynamic material.
• Suggested fixes: mapped to the problem — sibilance → de-esser, mud → a targeted EQ cut, and so on.
• Mix-wide checks: “is my mix too loud / muddy / harsh?” renders a full mixdown and reports on the whole balance.

How to use it

1. Select a track or region (or just name it), then ask the Co-Producer to analyze it — it reads your live selection, not a stale snapshot.
2. Read the metrics, the detected issues, and the suggested processing — then ask it to act (“add a de-esser”, “cut the mud”).

Ask the Co-Producer to “revocalize the Lead Vox track with Lora” and it re-sings your audio regions with a voice model from your Revocalize account, then places the result on a new (Revocalized) Audio track aligned to the original bar positions. Your source track is left untouched, so you can A/B instantly.

How to use it

1. Pick what to re-sing. Name a track for all its regions, name one region for just that one, or leave it open to use your current selection.
2. Choose a voice. Use a voice name from your account — “what voices can I use?” lists them. Ambiguous names prompt a clarification rather than a guess.
3. Tweak settings (optional). Key, scale, harmony, autotune, and transpose default to the plug-in's values and can be overridden in the prompt.

A request that combines several goals can affect many parts of a project. For those jobs, Co-Producer prepares a visible plan before execution so you can understand the sequence and catch a wrong assumption early.

What happens before a complex run

1. The assistant interprets the request and inspects Logic.
2. It presents the proposed steps and the important decisions it made while planning.
3. Choose Approve & Run to continue, review the request in the full Assistant, or cancel without executing.
4. Follow progress in the main window, Floating Assistant, or Studio Bot; all three show the same run.

During and after the run

• Cancel cleanly when the result is no longer wanted; the current job is stopped instead of being left silently active.
• Detect stalled work and surface a clear status rather than waiting forever.
• Recover in context with actions such as retrying an available failed step, locating Logic, or reopening Accessibility settings.
• Verify the result after supported Logic operations before the run is marked complete.

Workflows are repeatable Logic Pro automations described in plain English. Build them in Assistant mode, run them from the browser, and switch to Debug mode when one misbehaves.

🧩 What is a workflow?

• A reusable automation. Each workflow is a YAML file that captures a sequence of Logic Pro UI steps — selecting tracks, opening menus, setting values. Run it over and over instead of re-prompting the assistant every time.
• Two modes. Assistant mode plans, builds, and tests a brand-new workflow from your description. Debug mode points the agent at an existing workflow file so you can test, fix, or improve it.
• The browser shows only yours. The Browse panel lists only the workflows you've created. Bundled / system workflows are used by the agent under the hood but stay hidden from the UI so they can't be accidentally deleted.

🛠️ Create a workflow

1. Switch to Assistant mode. In the Workflows tab, set the mode switcher in the header to Assistant (the purple one).
2. Describe what you want. Type a plain-English description of the automation. The more specific the better — include track types, parameter values, ordering.
3. Let the agent plan, build, and test. The status ribbon shows progress through Plan → Build → Debug → Done. The agent saves the workflow as a YAML file when it's confident the steps work.
4. Find your new workflow in the browser. Click the folder icon in the header to open the Browse panel. New workflows appear under their category. From here you can run them anytime.

▶️ Run a workflow

1. Open the Browse panel. Click the folder icon in the Workflows header. The Workflows section lists your custom workflows by category.
2. Tap the workflow you want to run. If the workflow needs arguments (a track name, a tempo, a file path), an inline form appears in the chat. Fill it in and submit.
3. Watch progress in the status ribbon. The phase chain at the bottom shows live progress. When it finishes you'll see a result card with elapsed time, step count, tokens used, and a Run Again button.

🐞 Debug a workflow

1. Switch to Debug mode. Use the mode switcher in the header. The orb turns amber to signal you're in Debug mode.
2. Pick a workflow to test. Open the Browse panel and click a workflow. Its filename appears in the header as a pill — that's the workflow the agent will reason about.
3. Ask questions or run live tests. Type things like “Why does this fail at step 3?”, “Test this against live Logic Pro”, or “Improve error handling here”. The agent will trace the workflow and propose fixes.

🚀 Share & earn

When a workflow is reliable in your project, you don't have to keep it to yourself. Push it for review by the Revocalize team — if it's accepted, it lands in the marketplace where other producers can run it and you earn revenue every time it's used.

1. Make sure it runs reliably. Run the workflow against a fresh Logic Pro project a couple of times. If it depends on your specific setup (track names, plug-in versions) it won't pass review — workflows should be general.
2. Push it for review. Open the Browse panel, hover the workflow, and click the blue Push button (arrow-up icon). The YAML uploads to our review queue. You can keep using the workflow locally while it's being reviewed.
3. We review it. Our team checks the workflow for safety, quality and uniqueness. You'll hear back when it ships — usually within a few days.

If accepted, your workflow:

• 🏪 Lands in the marketplace. Other producers can browse and run it from inside Revocalize, with you credited as the author.
• 💰 Earns you revenue. You get paid a share every time another user runs your workflow. The more useful and reusable it is, the more it earns.
• ✨ May join the assistant itself. Standout workflows can be integrated directly into the Revocalize assistant — invoked automatically by the agent whenever a user's request matches what your workflow does. Highest-value placement.

💡 Tips for great workflows

• Be specific in your prompt. Say “at 120 BPM” rather than “with a tempo”. Name the track type (Software Instrument, Audio, Drummer) instead of just “a track”. Concrete parameters lead to concrete workflows.
• Keep workflows focused. One operation per workflow tends to be more reusable than one giant workflow that does everything. Smaller pieces compose better.
• Debug after every build. Right after Assistant mode saves a new workflow, switch to Debug and run it once against your project. Fix any failures while the context is fresh.
• Sessions ≠ workflows. The Sessions tab in the browser holds your past chat history — useful for resuming a previous build/debug conversation. The Workflows tab holds the saved automations themselves.

⚙️ Requirements

• Accessibility permission. Workflows automate Logic Pro through the macOS Accessibility API — the same permission the voice agent uses. Grant it in System Settings → Privacy & Security → Accessibility.
• Logic Pro must be open. Workflows act on the currently focused Logic Pro project. Open the project you want to operate on before running a workflow.
• Credits. Building or debugging a workflow via the chat agent draws from your credit balance — billed at the actual AI provider cost, accumulated across every internal turn the agent runs (a simple workflow might be ~$1–3, complex ones $10+). Running an already-built workflow is always free, whether it's bundled, your own, or from the marketplace. Every account starts with $15. Top up at /plans → Co-Producer Credits; view your balance in Profile → Credits.

💳 Credits & pricing

Building and debugging draw from your credit balance, billed at the actual AI provider cost. Running an already-built workflow is always free.

Buying more credits

1. Open /plans.
2. In the Co-Producer Credits card, pick a tier — $10, $50, $100, or Other for a custom amount ($1–$1,000).
3. Complete checkout via Stripe.
4. Credits land in your balance immediately — no expiration.

🚨 Running out of credits

• Running existing workflows still works. Execution is free, always.
• Building or debugging is paused until you top up. The assistant will tell you what to do next.
• Top up in seconds at /plans → Co-Producer Credits.

📊 Usage & policy

• Credits never expire. They sit in your account until you spend them.
• The $15 starter credit is one-time per account.
• Purchased credits are non-refundable.

❓ FAQ

All four modes use the same command language — pick whichever feels right in the moment.

Tips for best voice recognition

• Speak clearly at a normal pace; don't rush.
• Reduce background music playback while issuing commands.
• Be specific: "Create a Software Instrument track called Bass" beats "make a track".
• Include all parameters in one sentence when you can: "Create a Hip Hop project at 140 BPM in A Minor".
• Reference tracks by name when possible — more reliable than counting indices.

Logic automation is local, and cloud processing is used only by features that need it. Here is what each part of the app does.

More answers live in-app: Help & Tips → FAQ · Troubleshooting · Best Practices.

In-app feedback (fastest)

Hover over any message — yours or the assistant's — and two icons appear on the right side of the bubble: Send Feedback (was this command handled well?) and Request Feature (something you wish worked). Each opens a small inline form you can send in a single click. Both go straight to us with the exact command text attached, so we know what you were trying to do.

Email

We read every message — Revocalize is in early beta and your real-world sessions shape the roadmap.

What's new in Revocalize Co-Producer, newest first. Every release during the beta is free to use.

v0.2.23LatestJuly 2026

The trust build: every change is read back from Logic before it is reported, known blockers get a specific fix and one retry, and mix analysis measures the actual mix.

apply · read back · confirm

Self-Verification

Renames, region mutes, plugin inserts, MIDI FX, and bypasses are now read back from Logic right after they run. If the session doesn't match what was intended, the Co-Producer says so instead of reporting success — so when it tells you the EQ was added, the EQ is there. Learn more

identify · fix · retry once

Self-Recovery

A folded track stack, an open automation view, a leftover plugin menu, no project open — each blocker is now recognized individually and gets a prescribed fix and a single retry instead of repeated blind attempts. In testing, importing audio into a folded stack went from 16 steps down to 3. Learn more

opt-in · Logic window only

Visual Diagnostics

When a step can't be completed or confirmed, the Co-Producer can take one screenshot of the Logic Pro window to see what actually happened. Off by default — you are asked once after launch. Only Logic Pro's window is captured, never the rest of your screen or other apps; the image is used for that one diagnosis, never shown in the app or chat, and deleted immediately. Learn more

• Mix analysis measures the real mix — two bugs are fixed: analysis could fail silently at the export panel, and in some cases it measured a single stem and presented the result as the full mix. It now analyzes the actual bounce, or tells you what it needs from you first.Try: “Is my mix too harsh or too muddy?”
• Organization reads real track names — Perc 2, Congas, Overheads, Room Mic, and Tuner used to end up in UNKNOWN during session organization. They are now sorted where an engineer would put them, whatever suffix you use.
• Audio import works from any state — importing audio files no longer depends on a shortcut that could be unavailable depending on what was focused in Logic.
• Steadier plugin and panel handling — plugin windows close properly, and Apple Loops search, preview, and placement are more reliable.
• Fewer unnecessary confirmations — harmless requests no longer trigger a “are you sure?” prompt just because your wording happened to contain a risky-sounding word.
• Clearer failures — if Logic Pro has no window open (a locked screen, for example), you get a plain explanation instead of an unexplained failed run.

v0.2.21July 2026

The feedback build: safer mix organization, conversational Apple Loops, plan-first production, a live Pet Assistant, and a much more reliable control layer.

audit · understand · preserve

Session-Aware Mix Prep

Co-Producer now audits existing folders, nested stacks, and summing structure before it organizes. It preserves routing and producer intent, uses multiple session signals instead of relying only on track names, and asks before touching mixed-role stacks. Learn more

search · preview · place

Conversational Apple Loops

Search your Apple Loops library by sound, tempo, or key; preview options in conversation; and import only after you choose. Ask for an alternative and the original stays available for A/B. Learn more

watch · approve · recover

Studio Bot Pet Assistant

A lightweight companion now floats beside Logic while automation is running. See live progress, expand the step timeline, approve plans, stop work, or retry a failed step without losing focus on the session. Learn more

• Plans before major changes — multi-goal requests become a visible plan before execution so you can review the intended work first.
• More accurate organization — track classification uses multiple available signals, not just names, and correctly classified single tracks are less likely to be moved into unnecessary UNKNOWN groups.
• Plugin-aware processing — the assistant can inspect existing inserts, reuse a suitable plugin instead of duplicating it, and build a chain when the session needs one.
• Verified mixer control — batch volume, pan, and mute changes use the dedicated control channel and are checked in Logic afterwards.
• Safer long-running commands — cancellation is cleaner, stalled runs are detected, and the app can offer future updates automatically.

v0.2.18July 2026

A reliability-focused drop: hands-free mixing at any scale, producer-language exports, and a steadier ride overall.

volume · pan · mute, at any scale

Hands-Free Mixing

Balance, pan, or mute any number of tracks in a single request — even a whole session. It runs over a control-surface channel, so it's fast, hits exact dB, and never locks up your keyboard while it works. Every change is verified against Logic afterwards, so “done” means done. Learn more

stems · mixdowns · delivery

Export Packages

Just say what you need — “send this to my mixing engineer,” “files for mastering,” or “a client package” — and the Co-Producer plans the right stems, mixdowns, or full delivery, shows you the plan, then exports to the folder you name. Learn more

• Reliable export destinations — exports now navigate to any folder you name (Desktop, a subfolder, anywhere) and create it if it doesn't exist.Try: “Export wet stems to my Desktop.”
• Steadier Logic Pro detection — fixed cases where the app reported Logic Pro as “not installed” even when it was.
• Accurate volume & pan — level and pan moves always land on the track you asked for, at the exact value.
• Bug fixes & stability — many under-the-hood fixes across saving, exporting, and automation for a smoother, more dependable session.

v0.2.17May 2026

The biggest beta drop yet — Revocalize Co-Producer goes from "moves tracks around" to a true creative partner that generates, listens, and re-sings.

AI producer

MIDI Generation

Describe a part in plain English and the Co-Producer generates the MIDI, then auto-imports each part onto its own named track. Keep chatting to revise or improve it into A/B variations. Learn more

listens to the sound

Audio Analyzer

Decodes the actual audio to flag real issues — clipping, sibilance, mud, boominess — and suggests concrete fixes. Honest by design: no invented metrics for silent or MIDI tracks. Learn more

re-sing with a voice

Revocalize Regions

The Revocalize plug-in's one-click flow, built into the assistant. Re-sing a track with any voice from your account onto a new aligned (Revocalized) track — source untouched for A/B. Learn more

• MIDI analysis & classification — identify a part (bassline / chords / lead / arp / pad / drums), key, polyphony, and the right instrument from a .mid file or a software-instrument track.Try: “Classify all the MIDI files in my import folder and tell me what instrument each needs.”
• Region operations — select and mute regions by name to clean up bleed, count-ins, or breaths without deleting anything.Try: “Mute the count-in region on the BG Vocals track.”
• Plug-in presets — list, load, and save settings on any plug-in (Logic stock, third-party AU, or Revocalize), including nested preset folders.Try: “Open the Channel EQ on track 5 and load a vocal preset.”
• Smart plug-in discovery & chains — map an intent to plug-ins actually installed on your Mac, plan the chain, route sends to aux returns, and verify the result.Try: “Add a vocal chain to the Lead Vox track.”
• Multi-window targeting — with several plug-in editors open, commands act on the plug-in you named.Try: “With the Compressor and Stereo Delay open, load a preset on the Stereo Delay.”
• Instrument loading & transport — load an instrument patch by name and toggle cycle/loop ranges from chat.Try: “Load a Rhodes patch on the Keys track and loop bars 1 to 8.”
• End-to-end song building — generate the core groove, import local parts, organize into colored folder stacks, and mix to a finished record in one conversation.Try: “Create a deep-house track called Demo and mix it.”

v0.2.0Early 2026

First public beta. The foundation: control Logic Pro by voice and text — create projects and tracks, edit the transport, import audio and MIDI, and build reusable Workflows.

• Voice & text control of Logic Pro through the macOS Accessibility API.
• Project, track, and transport operations — create projects, add and organize tracks, play / stop / record.
• Audio & MIDI import from your workspace, plus color-coding and folder organization.
• Custom Workflows — build, debug, and re-run reusable automations described in plain English.

These are on the immediate roadmap. Today you get the Assistant and Workflows; these land in future releases: