Revocalize Co-Producer Documentation

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

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
• •Mute / Unmute 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:

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.

Revocalize is designed to keep your creative work on your machine.

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.

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