Relativ Studios
0

AbleReport Manual

 

AbleReport Manual v1.0

AbleReport User Manual (v1.0)

AbleReport is a tool for human clarity and AI discovery.

Max for Live diagnostic & analysis tool for Ableton Live

Introduction

AbleReport is a Max for Live diagnostic and analysis tool that turns your Ableton Live Set into structured data that both humans and AI can read. It scans your Live Set (.als) and creates a complete technical snapshot: tracks, devices, routing, levels, clips, and system settings.

AbleReport generates an AI Key – a compact, AI-ready representation of your project. You can give the AI Key (and optionally a bounced audio file) to the AI of your choice so it can “see” your entire set, understand how it’s built, and help you debug, improve, or redesign it.

This manual explains every feature of AbleReport, every button, all reports and data fields, and how to use the output with AI for production, mixing, arrangement work, and troubleshooting.

Contents

1. What AbleReport Does

AbleReport scans your active Live Set (.als) and exports structured reports containing:

  • Track list and group structure
  • Devices per track (including nested devices inside racks)
  • Routing (audio & MIDI)
  • Volumes, pans, sends, latency, and active state
  • Scenes & clip metadata (Session View)
  • Arrangement View clips and lanes
  • System information (Ableton version, CPU, controllers, buffer settings, etc.)

The result is a full diagnostic package (TXT, CSV, and JSON) you can store with your project or send to a mix engineer, collaborator, or AI system.

In addition to the individual reports, AbleReport also generates an AI Key – a single, AI-friendly file that summarizes the key technical details of your set. You can upload the AI Key directly to an AI assistant (optionally together with a bounced audio file) so it can understand both the sound and the structure of your project.

2. How to Use AbleReport

2.1 Before Running

  1. Ensure that an audio output device is selected.
  2. Save your Live Set.
  3. Stop playback.
  4. Avoid editing, recording, or heavy interaction with Live while AbleReport is scanning.

2.2 Running the Report

  1. Drop AbleReport onto any track in your Live Set.
  2. Open the device and click Start Report.
  3. Choose a directory where the report package will be created.
  4. Wait until you see the Complete window and the Tasks Panel shows all tasks as Complete.

Large sets may cause Ableton Live to appear frozen during scanning. This is normal – let AbleReport finish before interacting with the project again.

Depending on the size and complexity of your Live Set, this process can be very quick or take a long time. For extremely heavy .als files with hundreds of tracks and scenes, the scan can run for a long period — sometimes even up to a couple of hours — especially on older CPUs or slower systems.

2.3 Output Folder Structure

Inside your chosen directory, AbleReport creates a folder named after your project and timestamp, for example: 

AbleReport - Track 10 - 2025-11-21_0207/

Inside that folder you will find:

  • AbleReport AI Key - [Project Name] - [Timestamp].json
    The AI Key file. This is the main file to upload to your AI assistant.
  • AbleReports/ – contains all individual reports in three formats:
    • AbleReports/TXT/ – human-readable text versions.
    • AbleReports/CSV/ – spreadsheet/table versions.
    • AbleReports/JSON/ – structured JSON versions.
  • Log_AbleReport.txt – a text log of the entire run, useful for debugging.

Each of the three subfolders contains one file per report:

  • Track Report - [Project Name] - [Timestamp] - AbleReport.[ext]
  • Device Report - [Project Name] - [Timestamp] - AbleReport.[ext]
  • Session Report - [Project Name] - [Timestamp] - AbleReport.[ext]
  • Arrangement Report - [Project Name] - [Timestamp] - AbleReport.[ext]
  • System Report - [Project Name] - [Timestamp] - AbleReport.[ext]

[ext] is txt, csv, or json depending on the folder. All three formats contain the same information, just structured differently for spreadsheets, scripts, or AI prompts.

3. Main Interface Overview

The main device interface contains three functional sections.

3.1 Left Panel – Welcome Area

AbleReport main interface screenshot

  • AbleReport Logo & Tagline
  • Start Report button – This starts the report and opens the Start Report Window.
  • User Manual button – Opens this manual.
  • Version Indicator – Shows the current build, for example v1.0.

3.2 Right Panel – Overview

AbleReport main interface screenshot

Displays a quick snapshot of your Live Set:

  • Tracks – Total number of tracks (audio, MIDI, returns, groups).
  • Devices – Total number of devices scanned across all tracks.
  • Scenes – Number of scenes available in Session View.
  • Clips (Session) – Total number of Session Clips.
  • Clips (Arrangement) – Total number of Arrangement Clips.
  • Refresh Icon – Rescans the overview without running the full report.
  • READY Indicator – Shows AbleReport is idle.

For larger sets, the values for Devices, Clips (Session) and Clips (Arrangement) may not populate until you run a full report. This is intentional to reduce CPU load and allow the device to open quickly on very heavy projects.

3.3 Tasks Panel

AbleReport tasks panel screenshot

Each task corresponds to a separate subsystem:

  • System Report – Gathers system-level data.
  • Track Report – Analyzes every track.
  • Device Report – Extracts all devices.
  • Session Report – Scans Session Clips.
  • Arrangement Report – Scans Arrangement Clips.

All tasks show Ready, Busy, or Complete status.

4. Report Windows

4.1 Start Report Window

AbleReport start report window screenshot

Opens when the main Start Report button is pressed.

Includes:

  • Summary of what AbleReport does
  • Instructions to:
    • Save your set
    • Avoid editing or playback during scanning
    • Warning that large sets may freeze Ableton temporarily
  • Start Report button
  • Close Window button

4.2 In-Progress Window

AbleReport in-progress window screenshot

Shows during the scan.

Features:

  • “AbleReport in Progress…” message
  • Explanation that scanning may freeze Ableton
  • Live log output of progress (for example “Scanned 57/74 Tracks…”) (optional)
  • Buttons: Close Window, Clear Log

The same log file is also written into the chosen report folder while the scan is running. You can open it in a text editor to check progress; each time you reopen the file, it will show the latest information.

4.3 Complete Window

AbleReport complete window screenshot

Opens once all reports finish.

Includes:

  • “AbleReport Complete!” message
  • Report success confirmation
  • View Reports (opens folder)
  • View Log (opens log window)
  • Close Window

5. What Each Report Contains

In addition to the AI Key, AbleReport creates five core reports. Each report is exported as TXT, CSV, and JSON so you can choose the format that works best for you (spreadsheets, scripts, or AI prompts).

Below are the data fields included in v1.0. Exact column order may change in future versions, but the core concepts and column names remain the same.

5.1 System Report

The System Report is a simple key–value table that captures the environment AbleReport was run in.

CSV columns:

  • Category – The setting or property name (for example, Live Version, Operating System, Sample Rate).
  • Value – The recorded value for that category.

Examples of information stored here include:

  • Live Version – Exact Ableton Live version used when generating the report.
  • Operating System – The OS and version (for example, macOS, Windows).
  • Audio Device / Driver – The selected audio interface and driver type.
  • Sample Rate / Buffer Size – Audio engine sample rate and buffer settings.
  • Project Name / File Path – The name and location of the current .als file.
  • Track / Device / Clip Counts – Summary of how many tracks, devices, scenes, and clips exist in the set.
  • CPU Usage – Average and peak process usage as measured by Live.

Use this report when you need to reconstruct the technical environment or include precise system details in a bug report or support request.

5.2 Track Report

The Track Report describes every track in the set and its routing.

CSV columns:

  • Track # – Numerical index of the track from left to right in the Live Set.
  • Track Type – Type of track (Audio, MIDI, Return, Group, or Master).
  • Track Name – Name of the track as shown in Live.
  • Group Path – Full hierarchy of any parent group tracks this track lives inside.
  • Track Color – Color assigned to the track.
  • Arm Recording – Whether the track is record-arm enabled.
  • Solo/Cue – Whether the track is soloed or cue-activated.
  • Track Activator – Track on/off state (mute).
  • Monitor – Monitor mode (In, Auto, or Off).
  • Audio From – Source of the track’s audio input.
  • Audio From Channel – Specific channel of the audio input source, if applicable.
  • Audio To – Audio output destination (for example, Master, a bus, or another track).
  • Audio To Channel – Channel of the audio output destination, if applicable.
  • MIDI From – Source of the track’s MIDI input.
  • MIDI From Channel – Specific MIDI channel of the input source, if applicable.
  • MIDI To – MIDI output destination (for example, an external device or another track).
  • MIDI To Channel – MIDI channel used for the output destination.
  • # Devices on Track – Total number of devices placed on the track.
  • Track Contains Automation – Indicates whether any automation exists on this track.
  • Performance Impact – Simple qualitative indicator of how heavy this track is in the project.
  • Pan – Current pan position of the track.
  • Crossfade Assign – Crossfader assignment (A, B, or none).
  • Volume – Track fader level.
  • Volume Has Automation – Whether the track volume is automated.
  • Send 1 – Level of Send 1 for the track (if present).
  • Send 2 – Level of Send 2 for the track (if present).

Use this report for routing audits, gain-staging checks, send usage, and automation diagnostics on a per-track level.

5.3 Device Report

The Device Report lists every device on every track, including rack structure and latency.

CSV columns:

  • Track# – Numerical index of the parent track that holds this device.
  • Track – Name of the parent track.
  • Arm – Whether the parent track is record-armed.
  • Solo – Whether the parent track is soloed.
  • Mute – Whether the parent track is deactivated (muted).
  • Chain Path – Rack / chain path (for example, Instrument Rack > Bass Chain > FX Rack).
  • Dev# – Index of the device in the track device chain.
  • Enabled – Device on/off state.
  • Device Name – Device name as shown in Live.
  • Device Class – High-level device class (AudioEffect, MidiEffect, Instrument, etc.).
  • Device Type – More specific device type information from the Live API.
  • Plugin Format – Plugin format (Built-in, VST2, VST3, AU, etc.).
  • Rack Type – If the device is a rack, its rack type (Instrument Rack, Drum Rack, Effect Rack, etc.).
  • # of Parameters – Total number of exposed parameters on this device.
  • # of Automated Parameters – How many parameters have automation in the Live Set.
  • Automated Parameters – List or summary of parameters that are automated.
  • Rack – Indicates whether this device is a rack.
  • Has Chains – Whether the rack contains one or more chains.
  • Drum Rack – Whether this rack is a Drum Rack.
  • Device ID – Internal AbleReport identifier for this device (for cross-referencing in JSON).
  • Latency (samples) – Device latency measured in samples.
  • Latency (ms) – Device latency converted to milliseconds.

Use this report as a plugin inventory, to review automation, and to identify heavy chains or redundant devices.

5.4 Session Report

The Session Report covers Session View slots, scenes, and clips.

CSV columns:

  • Track # – Numerical index of the parent track.
  • Track – Name of the parent track.
  • Track Type – Type of the parent track (Audio, MIDI, Return, Group, or Master).
  • Arm – Whether the parent track is record-armed.
  • Solo – Whether the parent track is soloed.
  • Mute – Whether the parent track is deactivated.
  • Slot # – Slot index in Session View for this clip.
  • Scene # – Scene index that this slot belongs to.
  • Clip Name – Name of the clip, if present.
  • Type – Clip type (Audio, MIDI, or Empty).
  • Clip Color – Color of the clip.
  • Clip Color Index – Numeric index of the clip color.
  • Clip Muted – Whether the clip itself is muted.
  • Length – Clip length in beats.
  • Loop – Whether clip looping is enabled.
  • Loop Start – Start position of the loop region.
  • Loop End – End position of the loop region.
  • Start Marker – Position of the clip start marker.
  • End Marker – Position of the clip end marker.
  • Playing Position – Current playback position within the clip, if playing.
  • Is Audio Clip – True if the clip is an audio clip.
  • Is MIDI Clip – True if the clip is a MIDI clip.
  • Has Notes – Whether the MIDI clip contains any notes.
  • Note Count – Number of MIDI notes in the clip.
  • Clip has Automation – Whether the clip contains automation.
  • Track Contains Automation – Whether the parent track has any automation.
  • Loop Length – Length of the loop region.
  • Track Color Index – Numeric index for the track color.
  • Signature Numerator – Numerator of the clip’s time signature.
  • Signature Denominator – Denominator of the clip’s time signature.
  • Launch Mode – Clip launch mode.
  • Launch Quantization – Quantization used when launching the clip.
  • Legato – Whether Legato mode is enabled for this clip.
  • Warping – For audio clips, whether warping is enabled.
  • Warp Mode – Warp mode used for audio clips.
  • Gain – Clip gain setting.
  • Pitch Coarse – Coarse pitch adjustment.
  • Transpose – Transpose setting applied to the clip.
  • Pitch Fine – Fine pitch adjustment.

Use this report to analyze scenes, build performance documentation, and debug clip launch, warp, and timing behaviour in Session View.

5.5 Arrangement Report

The Arrangement Report describes all Arrangement View clips, per lane.

CSV columns:

  • Track # – Numerical index of the parent track.
  • Track Name – Name of the parent track.
  • Lane – Name or label of the lane, if any.
  • Lane # – Lane index for multi-lane tracks (for example, automation lanes).
  • Clip # – Index of the clip within this lane.
  • Clip Name – Name of the clip, if any.
  • Clip Type – Type of clip (Audio or MIDI).
  • Clip Color – Color of the clip.
  • Clip Color Index – Numeric index of the clip color.
  • Start Time – Start time of the clip in the arrangement timeline.
  • End Time – End time of the clip in the arrangement timeline.
  • Length – Clip length in beats.
  • Looping – Whether looping is enabled for this clip.
  • Loop Start – Start of the loop region.
  • Loop End – End of the loop region.
  • Loop Length – Length of the loop region.
  • Start Marker – Position of the clip start marker.
  • End Marker – Position of the clip end marker.
  • Playing Position – Current playback position within the clip, if playing.
  • Muted – Whether the clip is muted in the arrangement.
  • Is Audio Clip – True if this is an audio clip.
  • Is MIDI Clip – True if this is a MIDI clip.
  • Warped – For audio clips, whether warping is enabled.
  • Warp Mode – Warp mode used for this audio clip.
  • Gain – Clip gain setting.
  • Pitch Coarse – Coarse pitch setting.
  • Pitch Fine – Fine pitch setting.
  • Transpose – Transpose setting applied to the clip.
  • Note Count – Number of MIDI notes contained in the clip, if applicable.
  • Signature Numerator – Numerator of the clip’s time signature.
  • Signature Denominator – Denominator of the clip’s time signature.
  • File Path – File path to the underlying sample, for audio clips.
  • Track Contains Automation – Whether the parent track has automation.
  • Clip has Automation – Whether this specific clip has automation.

This report is useful for understanding the full timeline structure of your track, spotting overlaps, gaps, and automation-heavy areas in Arrangement View.

6. How to Use AbleReport with AI

6.1 AI Key Overview

The AI Key is the primary file for working with AI. It condenses the most important information from all AbleReport outputs (system settings, tracks, devices, routing, clips, and more) into a single, AI-friendly structure.

On its own, the AI Key allows an assistant to:

  • See your full track list and routing – including groups, returns, sends, and I/O assignments.
  • Understand devices and racks – what lives on each track, and which parameters are automated.
  • Inspect Session View and Arrangement View – how clips, scenes, and sections are laid out.
  • Know your technical environment – Live version, OS, buffer size, sample rate, and CPU usage.

You can paste the AbleReport AI Key directly into an AI chat, or upload it as a file if the assistant supports file uploads.

6.2 Working with AI using only the AI Key

Even without any audio, the AI Key is enough for the assistant to do deep technical analysis of your project. With just the AI Key, an AI can:

  • Check routing and gain staging – spot tracks routed to the wrong place, muted paths, or extreme level settings.
  • Audit sends, returns, and buses – see how your effects are wired and where signal might be lost.
  • Analyze plugin usage and complexity – identify heavy chains, redundant processing, and places to simplify.
  • Review Session and Arrangement structure – see where sections, scenes, and clips may feel unbalanced or cluttered.
  • Inspect automation strategy – understand which parameters are automated and where conflicts might occur.

Example prompt:

“Here is my AbleReport AI Key for this track. Please analyze the routing and gain staging, and tell me where you see potential problems or confusion.”

6.3 Adding a stereo bounce (AI Key + audio)

If you also provide a stereo bounce of your project, the assistant can relate what it hears to what it sees in the AI Key.

  • Audio = emotional and sonic truth.
  • AI Key = technical and structural truth.
  • Together = a virtual AI mix engineer that understands your whole set.

6.4 Mix & Sound Analysis

With the AI Key and a stereo bounce, AI can combine sonic impressions with precise knowledge of your chain and make very targeted suggestions. For example, it can:

  • Identify tonal and dynamic issues – muddy lows, harsh highs, weak low-end, overcompression, or reverb build-up.
  • Connect problems to specific tracks and devices – for example, pointing to a specific EQ or compressor that is likely causing an issue.
  • Suggest precise parameter changes – like gentle cuts at certain frequencies, adjusting compressor thresholds, or taming overly bright sends.
  • Review master bus behaviour – checking loudness, dynamics, and stereo image against your master chain.

6.5 Arrangement & Structure

Using the Session and Arrangement information from the AI Key (and optionally the audio bounce), AI can:

  • Break down sections – intro, builds, drops, breakdowns, and outros by time and scene.
  • Spot weak or repetitive areas – sections that are too long, too short, or not evolving enough.
  • Suggest structural edits – such as moving a breakdown earlier, extending a build, or adding a bridge.
  • Flag missing transitions – sections where the energy jumps too quickly without support.

6.6 Sound Design & Devices

From the Device and Track information encoded in the AI Key, AI can dig into your sound design chains and:

  • Inspect synths, racks, and FX chains – for your key sounds, busses, and returns.
  • Suggest parameter tweaks – filters, envelopes, saturation, and modulation to better fit the mix or style you describe.
  • Highlight redundant processing – effects that can be consolidated to reduce CPU or simplify the project.
  • Recommend alternate strategies – for example, moving processing from individual tracks to buses or groups.

7. Troubleshooting with AI

AbleReport is designed to work hand-in-hand with AI assistants. In almost all cases you only need to provide the AI Key (and optionally a stereo bounce) — you do not need to paste individual CSV or JSON reports into the chat.

7.1 No Sound / Routing Issues

  1. Run AbleReport and generate a fresh AI Key for your project.
  2. Paste the AbleReport AI Key into an AI chat.
  3. Add a short description of the problem, for example: “I cannot hear my bass track. Please use my AbleReport AI Key to check my routing and tell me what might be wrong.”

The AI can:

  • Find tracks routed to nowhere – or to buses that never feed the master.
  • Check monitor modes and activators – for example, Monitor Off, muted tracks, or solo conflicts.
  • Spot send-only paths – where signal is sent to returns that are themselves muted or not routed correctly.

7.2 Gain Staging & Volume Problems

With only the AI Key, AI can read your track volumes, sends, and automation flags and suggest a gain-staging plan.

  • Identify extreme levels – tracks that are very quiet or very loud compared to the rest.
  • Review send usage – find sends that are driving too much signal into reverbs, delays, or parallel chains.
  • Flag volume automation conflicts – where automation fights your intended fader positions.

Example prompt: “Here is my AbleReport AI Key for this project. Please propose a clean gain-staging strategy and tell me which tracks or sends I should adjust first.”

7.3 Plugin & CPU Troubles

The AI Key includes a complete Device Report, so AI can see which tracks and racks are heaviest.

  • List heavy chains – tracks with a large number of devices, racks, or automated plugins.
  • Spot repeated devices – plugins that appear on many tracks and could be moved to a bus.
  • Suggest consolidation – ways to simplify chains or freeze/flatten specific tracks.

7.4 Timing, Warp, and Groove Issues

Using Session and Arrangement information from the AI Key, AI can investigate timing and warp-related problems without hearing the audio.

  • Compare warp settings – across all drum or loop tracks to find inconsistencies.
  • Detect potential phase problems – for example, layered kicks or snares with different warp modes.
  • Review clip start/loop points – to see if misaligned markers might cause flamming or drift.

7.5 Automation & Arrangement Conflicts

The AI Key encodes where tracks and clips contain automation. AI can help you untangle conflicts between track-level and device-level automation.

  • Highlight automation-dense areas – sections of the arrangement with many simultaneous changes.
  • Compare track vs. clip automation – to find where they may be fighting for control of the same parameter.
  • Suggest simplifications – for example, moving automation from many small clips to a single track envelope.

7.6 Preparing a Bug Report or Support Ticket

When Live or a plugin behaves strangely, AbleReport can help you prepare a clear bug report for AI, Ableton, or third-party developers.

  1. Run AbleReport and keep the full output folder together with your project.
  2. Paste your AbleReport AI Key into an AI chat and briefly describe the bug.
  3. Ask the AI to help you draft a bug report that includes:
    • System environment (from the System Report encoded in the AI Key).
    • Exact track and device configuration relevant to the issue.
    • Clear, step-by-step instructions to reproduce the problem.
  4. Attach the AbleReport folder (and optionally the AI Key file itself) when you contact support.

8. Best Practices

  • Treat AbleReport as a project manifest – run it whenever you reach a major milestone in your track (finished arrangement, pre-mix, final mix). Save the AbleReport folder next to your .als file.
  • Use the AI Key as your default AI input – whenever you ask an assistant for help with this project, start by providing the AI Key so it sees the whole set.
  • Regenerate after big changes – if you make major routing, device, or arrangement changes, generate a new AI Key so future analysis reflects the current state.
  • Name folders clearly – keep the automatic folder name, or add comments like “Pre-mix” or “Mastering version” to track project history.
  • Use TXT/CSV/JSON for human and advanced workflows – TXT is easiest to read, CSV is ideal for spreadsheets, and JSON is best for scripting or custom tools.
  • Protect sensitive information if needed – before sharing externally, you can duplicate the project and rename tracks or remove identifying details, then run AbleReport on that copy.

9. Version Notes (v1.0)

  • Added AI Key export for AI-assisted analysis.
  • Standardized output folder structure with dedicated TXT / CSV / JSON subfolders.
  • Optimized BUSY/DONE sequencing and Live API readiness checks.
  • Improved routing, device parsing, and clip detection.
  • Refined UI windows and manual to highlight AI workflows.

10. Contact

For feedback, feature requests, or bug reports, contact the developer:

AbleReportM4L@gmail.com

End of Manual