PRONUNCIATION RISKS FOUND (3):
Line V1:3 -> "We live in darknet spaces"
Risk: "live" is homograph
Options: "lyve" (verb) or "liv" (adjective)
-> Needs clarification
Line C:1 -> "SQL injection in the code"
Risk: "SQL" is tech acronym
Fix: "S-Q-L" or "sequel"
-> Auto-fix: "S-Q-L injection in the code"
Line V2:5 -> "Reading Linux logs at 3AM"
Risk: "Linux" commonly mispronounced
Fix: "Lin-ucks"
-> Auto-fix: "Reading Lin-ucks logs at 3 A-M"
Step 4: User Confirmation
For ambiguous words (like "live"): Ask user which pronunciation
For clear fixes (tech terms): Auto-fix
Auto-Fix Rules
Always Auto-Fix
Tech terms (SQL → S-Q-L, Linux → Lin-ucks)
Common acronyms (FBI → F-B-I, GPS → G-P-S)
Numbers (1993 → '93 or nineteen ninety-three)
Ask User First
Homographs (live, read, lead, wind, tear)
Names (confirm pronunciation preference)
Words with regional variants (data, either, route)
Output Format
Track File Updates
If given a track file, update these sections:
Pronunciation Notes (add table):
| Word/Phrase | Phonetic | Notes |
|-------------|----------|-------|
| Jose Diaz | Ho-say Dee-ahz | Spanish name |
| live | lyve | Verb form (to reside) |
| SQL | S-Q-L | Spell out |
Lyrics Box (apply fixes):
Replace standard spelling with phonetic in the Suno lyrics section.
Standalone Report
PRONUNCIATION SCAN COMPLETE
===========================
File: [path or "direct input"]
Risks found: X
Auto-fixed: Y
Needs user input: Z
FIXES APPLIED:
- "SQL" → "S-Q-L" (line V1:3)
- "Linux" → "Lin-ucks" (line V2:5)
NEEDS USER INPUT:
- "live" (line C:1) - lyve or liv?
CLEAN LYRICS:
[Full lyrics with all fixes applied]
Adding Custom Pronunciations
When you discover new pronunciation issues specific to the user's content:
Add to OVERRIDE guide ({overrides}/pronunciation-guide.md):
Read config to get paths.overrides location
Check for {overrides}/pronunciation-guide.md
Create file if it doesn't exist (with header and table structure)
Add the word to appropriate section (Artist Terms, Album Names, etc.)
Include: word, standard spelling, phonetic spelling, notes
Example entry:
| Larocca | larocca | Luh-rock-uh | Character in "sample-album" album |
DO NOT edit the base guide (/reference/suno/pronunciation-guide.md) - plugin updates will overwrite it.
When to add:
Artist names, album titles, track titles
Character names in documentary/narrative albums
Location names specific to album content
Any pronunciation discovered during production
This keeps discoveries version-controlled with the music content in the overrides directory.
Remember
Load both guides at start - Base guide + override guide (if exists)
Homographs are landmines - live, read, lead, wind WILL mispronounce without fixes
Tech terms need phonetic spelling - Don't trust Suno with acronyms
Non-English names always need help - Phonetic spelling mandatory
Numbers are tricky - Write them out or use apostrophes
When in doubt, ask - Better to clarify than regenerate
Add discoveries to OVERRIDE guide - Never edit base guide (plugin will overwrite)