The AI features

The AI tab sits in the tools panel. Two menus and a few direct actions — Create makes something new, Enhance works on the score you have open.

Everything here is optional. Every AI feature has a manual equivalent, and the editor is fully usable without touching any of it.

Create — starting from something

Create sits on the top bar, next to Export, because half of it isn’t AI at all: importing MusicXML and pasting notation are plain conversions.

Action	What you give it
Compose from scratch	A description — “a gentle 3/4 communion hymn”
Lyrics → melody	A hymn text; you get a singable tune for it
Import MusicXML / MIDI	A file from MuseScore, Finale, Sibelius or a DAW
Paste notation	Jianpu or solfa as text
Sing to score	Your voice, with a metronome
Upload recordings	Already-recorded parts → an SATB score
Group composition	Two singers, one click track, a duet
Warm-up → score	A warm-up in plain words, or a preset. See Warm-ups

Enhance — working on this score

• Harmonize to SATB — a four-part arrangement under your melody, voice-led, lyrics carried across. The most-used action here.
• Transpose — move to another key, optionally with voice-leading that keeps tenors out of the basement.
• Counter-melody — a descant or second line.
• Chords — a suggested progression, shown in a table you can copy. It doesn’t write chord symbols onto the score; type the ones you want into the Text tab’s Chord box (chord symbols).
• Dynamics & tempo — sparse, phrase-aware markings and shaping like a closing ritardando, applied to the score.
• Style transfer — reimagine the whole piece in another idiom: Yoruba praise, gospel, contemporary worship, plainchant, or your own description.
• Pronunciation guide — IPA plus an easy respelling for lyrics in a language your choir doesn’t speak.
• Auto-tag — discovery tags (mood, occasion, style, difficulty) so the piece is findable when you publish it.

Each applies to the open score. If you don’t like it, undo.

The assistant

Assistant opens a chat beside the score. Ask in plain language and it carries out the work — “harmonize this into SATB, move it to F, then add dynamics” is one request, not three menu trips.

Point at a bar

It reads the bar numbers you see in the editor, so you can be specific:

• “Make bar 12 louder”
• “The alto is too high in bar 8”
• “Put a repeat at bar 8 and mark bar 17 as the chorus”
• “Delete bar 4”
• “Fix the words in bar 3 — they should be al-le-lu-ia”

Select some notes first and “this”, “here” and “this bar” mean your selection. With nothing selected it asks which bar rather than guessing.

Bar operations — insert, delete, duplicate — always apply to every part at once, so the voices stay lined up. That’s a rule of this notation, not a limitation: bar 8 has to mean the same place in every voice.

Not yet: slurs, hairpins, glissandi, tuplets, chord stacking, grace notes and the guzheng fingering/technique marks — and warm-ups, which have their own builder under Create. Ask and it’ll tell you so rather than pretend.

Watching it work

A turn can take a minute or two. The panel shows which step it’s on and what it’s doing — “Harmonizing…”, “Editing notes…” — and a Stop button. Stop takes effect after the step it’s on; anything already applied stays applied, and you can undo it.

If a request needs more work than one turn allows, it says so and offers to continue rather than quietly stopping half-done.

Undo, and the second opinion

Every turn that changes something gets its own Undo, labelled with what you asked for — “Undo ‘make it gospel’”. The last five turns per score stay undoable, and they survive closing the panel, reloading, and coming back on another device.

DomiSol also checks the assistant’s work independently. If a turn leaves a voice a different length from the others, a note stranded octaves from its part, or a bar that doesn’t fit the meter, a Worth checking note appears under the reply — even when the reply itself sounds confident. It only reports problems that turn introduced, so a deliberate pickup bar is left alone.

Help

⋯ → Help is a different thing: it answers questions about DomiSol from this manual and links the pages it used. Use it when you’re hunting for a control rather than for musical work — and if the manual doesn’t cover something, it says so instead of guessing.

What it costs

AI actions spend credits, and they are priced by what they actually cost us to run:

Action	Credits
Photo → score	4 per page — a seven-page PDF costs 28
Harmonize to SATB	4
Compose a melody	3
Sing/hum → score · style transfer	2
Write or translate lyrics	1
Warm-up: fill from description (the builder itself is free)	1
Transpose · chords · explain · dynamics · tags · pronunciation · search	1

Assistant turns are the exception: they’re billed by how much work the turn actually did, from 2 credits for a quick change upward if it fires the heavy tools. Asking one question or nudging a bar stays at the bottom of that range.

Your balance sits in the editor bar and in the top navigation, on every screen, and each completed action tells you what it took.

Every account starts with a one-time grant of free credits. It is a starting stock, not a monthly refill — it does not come back on the 1st. Pro and the other paid plans do refill every month; the pricing page has the current numbers.

Nothing else is gated by credits: writing, playback, lyrics, parts, sharing and the solfa/jianpu PDF never touch them.

Where to go next

• Photos, files and recordings — getting existing music in.
• Playing your score back — hearing what the AI wrote.