← Back to the overview

INVITED BETA / FIRST SESSION

A small show.
A useful first test.

Applications are open for all console families with an implemented driver, including X32 / M32. Your background is reviewed before a complete invitation is prepared. Most new families start with controlled Console validation; Production workflow testing is limited to already-vetted controls. Each console can progress independently. This walkthrough is available to read now; it is not an installer, licence, or an invitation to use an unverified build.

Two ways to help

Console validation: experienced operators help establish what works on an exact model and firmware, starting with offline preparation and a small, controlled test setup. Production workflow: operators thoroughly evaluate already-vetted workflows through preparation and rehearsal before any reviewed production use. Applying does not certify controls or guarantee immediate access.

Initial beta licences last up to 14 days, with extensions reviewed individually. Another console’s testing does not need to wait for the X32 cohort to finish.

What’s new in 0.6.0-beta.3

Released November 19, 2026 for Apple Silicon Macs. Use the Console menu for connection status, Console Undo, and the message log. Find… (⌘K) opens features or jumps to settings. The Routing Assistant can now arrange and group signal paths in its Block Diagram.

Already on beta.1 or beta.2? Use Check for Updates… in the app and install the update when you’re between sessions. First-time testers receive the installer and personal licence by invitation.

Before installing an invited build

Your invitation should identify the build, console family, tested scope, licence period, support contact, and applicable beta/licence/privacy terms. Use the download and activation instructions supplied with that invitation. If anything is missing, ask through the support contact before testing.

Install and activate your invited Mac build

The current invited build is for Apple Silicon Macs (M1 or newer). Use the installer link in your invitation, open the downloaded DMG, drag Console Programming Assistant to Applications, and open it from Applications. If your Mac uses an Intel processor or you use Windows, ask support about availability before downloading.

Open Settings → Licence and paste the entire personal beta key from your invitation. Check the coverage and expiry shown by the app. Review and accept the supplied beta terms as instructed before testing. If the link, key or terms are missing, reply to your invitation.

1. Explore without a console

Start with a new workspace and keep console-control modes off. Download a fictional project below, then open the .cpa file through File → Open. These files contain preparation data, not audio, an app installer, or a licence. Opening a project does not change the saved network address or guarantee that the app is disconnected: check your own connection/settings first.

Neither demo contains parameter automation, macros, gain-compensation selections, or an instruction to send to hardware. Inspect the data before adapting it to any console.

2. Follow the theatre example

Open Channel & DCA Mapping → Script Breakdown. Scene 1, Arrival, includes Alex and Blair. Scene 2, The letter, includes Blair, Casey and Drew. Compare their DCA layouts in DCA Assignments. In Scene 5, Finale, all six performers belong to the Company group on DCA 1.

Make one preparation edit, undo it, then save a separate copy and reopen that copy. You should see the saved result. This checks a useful workflow without sending console commands. You can do every step without an AI assistant.

3. Record what you observed

For each task, note the step, what you expected, what actually happened, and whether the result came from the app, a simulator or a physical desk. A completed checklist is not proof that a console operation worked. Help → Beta Testing… keeps progress on your Mac for the selected console and firmware. Your invitation defines which checks to run. Open and preview a report before sending it. The progress and credit estimates in the window are preliminary and reviewed separately.

4. Test hardware only within your invitation’s scope

Back up the desk and use a small, controlled test configuration. Confirm the selected family and physical channel/DCA numbers; demo indices are not a recommendation for your desk’s patch. Start with a small read-only range. Only make a write when you understand its exact target and expected effect, following the build’s instructions. Do not send an entire demo to an occupied desk.

Test one supported workflow at a time. Inspect actual desk results and your recovery path. Your invitation’s known limitations take priority over a generic feature description.

5. Share a reviewed report

If your build has Send feedback / Report a problem, describe the issue and preview any optional diagnostic attachment. Export works while offline. Direct sending requires a build configured for the feedback service; otherwise send only the reviewed export through the support contact in your invitation. Read how app reports are handled. Do not include private scripts, cast lists, credentials or client material. A written comment without logs is welcome.

Keep preparation and runtime choices clear

CPA focuses on preparing and programming your console. The console’s own scene system remains central. Optional runtime automation, macros and gain compensation depend on the app continuing to run; test the specific controls and overrides for the feature you choose.

Read the broader quick-start guide · Apply or request a console notification