Guitar Pro repeats, alternate endings, D.C., D.S., and Coda
Navigation marks compress a song on the page, but each mark changes the playback route. Build that route in layers and test every pass before adding another jump.
The practical answer
Start with a linear score, add repeat boundaries and endings, then add long-range D.C., D.S., Fine, or Coda navigation last.
A step-by-step approach
-
1
Write the music linearly
Complete the passage without navigation marks so bar content and duration can be checked first.
-
2
Add repeat boundaries
Place repeat open at the first repeated bar and repeat close at the last, then set the intended pass count.
-
3
Add alternate endings
Mark the bars used on the first pass and the replacement bars used on later passes.
-
4
Add long-range navigation
Place Segno, Coda, Fine, and the corresponding D.C. or D.S. instruction only after local repeats work.
-
5
Audit playback
Start before each repeat or jump, follow the cursor, and write down the actual bar sequence to catch loops or skipped endings.
Begin with a simple repeat loop
Place the opening repeat on the first beat of the first repeated bar and the closing repeat on the last bar of the repeated passage. Guitar Pro lets the closing repeat carry a repeat count, so confirm whether the number represents the intended total passes in your version and score.
Play from at least one bar before the opening sign. If the cursor exits early or repeats too much, fix the boundary and count before adding alternate endings.
Use alternate endings for changed final bars
A first ending contains music heard only on the first pass; the next ending supplies the replacement on a later pass. Keep the ending brackets aligned with complete bars and ensure the repeat close is positioned to send playback back at the right moment.
For more than two passes, explicitly assign which pass uses each ending rather than relying on visual proximity. Playback testing matters because a readable-looking volta can still have the wrong pass assignment.
Understand D.C., D.S., Fine, and Coda as pairs
Da Capo sends playback to the beginning; Dal Segno sends it to a Segno marker. Fine supplies an end point after a return, while To Coda sends playback to the separate Coda destination when the relevant return instruction is active.
Every source needs an unambiguous destination. Add the Segno or Coda marker before its instruction, and avoid multiple identical destinations unless the arrangement has been tested carefully.
Keep local repeats separate from global jumps
Nested repeats and long-range jumps can interact in ways that are difficult to infer from the page. Complete and test local repeats first, then add one global jump and retest from before the whole section.
If playback loops forever, temporarily remove the newest jump rather than rewriting bars. If an ending is skipped, inspect its pass assignment and whether a D.C. or D.S. return changes the pass state.
Audit the listener’s path
Follow the cursor and write a compact sequence such as 1–8, 1–6, 9–16. This exposes missing bars and accidental cycles more reliably than staring at symbols in isolation.
Also export or play from the beginning once the structure is complete. Starting playback in the middle may not recreate the repeat state that a listener encounters from bar one.
Common questions
Sources and review notes
Product details were checked against the official sources below on 9 August 2026. Offers and software details can change, so confirm current terms before buying.