DAW documentation

Aiuto

The session is open, the cue is half written, and the answer you need is buried three levels down in a manual you have not read since the last major version. Aiuto is the specialist that reads it for you.

Reach for it when: A setup question interrupts the session
What it works from: A question, and the software you already selected
Available on: Free with Cubase and Dorico · all sixteen environments on Professional

The problem

Why this one exists

Technical interruptions are not neutral. They are not simply time removed from the day — they remove the state you were writing in. You stop, you open a browser, you read four forum threads written for a different version of the software, you try something, it does not work, and by the time the routing behaves you have lost the shape of the phrase you were reaching for.

The generic assistant makes this worse rather than better. Asked how to route an instrument to separate outputs, it produces something reasonable and useless: look in the mixer or the instrument settings, create additional channels, the exact steps vary by DAW. Every word of that is true. None of it moves you forward, because the thing you needed was the version of the answer that applies to the software actually open on the screen.

Aiuto starts from the opposite end. It knows which environment you are in before you ask, and it answers from that environment's own documentation.

The specialist

What it actually does

Ask a precise question and get a procedure grounded in the official documentation for the software you selected.

The selection is the whole mechanism. Aiuto is bound to one environment at a time — Cubase, Nuendo, Logic Pro, GarageBand, Studio One, Reaper, Ableton Live, FL Studio or Pro Tools; Dorico, Sibelius, MuseScore or StaffPad; or the Kontakt, Sine Player and Spitfire Audio ecosystems. Once it is set, the terminology, the menu names and the order of operations all come from that documentation rather than from a general impression of how music software works.

What comes back is a route, not a hint: the ordered steps, the menus they live in, and the manual context around them so you can tell whether the procedure applies to your case or to a neighbouring one.

The same request, two ways

You ask

How do I route this instrument to separate outputs in my DAW?

A general assistant

Look in the mixer or instrument settings for an output-routing option, then create additional channels. The exact steps vary by DAW.

Aiuto

Uses the DAW and version already selected, finds the documented routing path, and returns the ordered menu and channel steps with the relevant manual context.

Less searching, fewer guessed menu paths, and a procedure matched to the DAW already in use.

In practice

Typical moments in a working week

Mid-session setup

A routing or export setting blocks the take and the answer has to come without leaving the project.

A DAW you use occasionally

The second or third DAW in your workflow, where the menu structure is never quite in muscle memory.

Onboarding a collaborator

An assistant or orchestrator needs the documented procedure for your template, not your improvised version.

How to use it well

Set the environment first

Choose the software and stay in it. Aiuto's advantage collapses the moment it has to guess which DAW you mean.

Ask the operational question

Not "how does routing work" but "how do I route this instrument to separate outputs". The narrower the question, the more exactly the documentation answers it.

Say what you already tried

If a menu path was not where you expected, say so. That usually distinguishes a version difference from a wrong turn.

Keep the session open

The point is to get the procedure without leaving the project. Read it, do it, and go back to the cue.

What it will not do

Aiuto answers from documentation. It will not invent a feature that does not exist in your version, it will not make creative decisions inside your project, and it does not touch your session — it tells you the route and you drive.