Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add Optional Settings below-tab lyric placement for tab-only and standard+tab layouts

Open
  • Is something wrong?
#2,776 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@Danielku15 is already working on this.

Since Jul 10, 2026.

Assessment

This issue has not been assessed yet.

Description

Discussed in https://github.com/CoderLine/alphaTab/discussions/2761

Originally posted by AvaTheArchitect July 3, 2026

Summary

This is a feature request for optional lyric placement in tab-focused layouts.

Currently, lyrics render above the tab staff. That may be expected current behavior, but in tab-only or standard+tab guitar layouts, lyrics can compete with bends, dive bombs, slides, vibrato, technique text, and other above-staff guitar effects.

The request is to add an option to render lyrics below the tab staff.

Problem

For guitar tracks, the area above the tab staff is often already occupied by guitar-specific notation:

  • full bends
  • dive bombs / whammy effects
  • slides
  • vibrato
  • technique text
  • phrase markings
  • other effect lanes

When lyrics are also placed above the tab staff, the renderer may need a large amount of vertical space to avoid collisions. Even with improved skyline/effect positioning, above-staff lyrics can still be a poor fit because the upper lane is already crowded by guitar notation.

This is especially visible in tab-only layouts or standard+tab layouts where lyrics would often be more readable below the tab staff.

Requested behavior

Add an option to place lyrics below the tab staff in tab-focused layouts.

Possible API shape:

tabLyricsPosition: "above" | "below" | "hide"
Expected behavior:
  • In tab-only layouts, allow lyrics below the tab staff.
  • In standard+tab layouts, allow lyrics below the tab staff rather than competing with above-staff guitar effect lanes.
  • Allocate appropriate below-staff spacing so lyrics do not overlap the next system.
  • Preserve current above-staff behavior as the default if preferred.
  • Optionally support hiding lyrics, matching the common notation-editor behavior.

Reference behavior

Guitar Pro provides a lyrics placement option under text/style settings with choices such as:

  • Above Staff
  • Below Staff
  • Hide

The attached Guitar Pro screenshots show this setting directly.

This makes tab-focused guitar layouts more readable when the upper staff area is occupied by bends, dive bombs, and other guitar effects.




Screenshot 2026-07-03 at 8 54 23 AM





Image 1 — Problem example
In the attached Guns N’ Roses example, the lead guitar track includes lyrics plus upper-staff guitar effects. Because the lyrics are above the tab staff, they compete with bends/divebombs/effects and require significant vertical headroom.




Screenshot 2026-07-03 at 12 15 02 PM





Image 2 — Expected visual direction / proof of concept
The attached Maestro screenshot shows a custom below-staff lyric overlay rendered under the tab staff. This is not being proposed as the exact implementation for alphaTab, but it demonstrates the layout goal:

  • lyrics sit below the tab staff
  • the upper effect lanes remain available for guitar techniques
  • the tab-focused layout becomes easier to read





Screenshot 2026-07-03 at 12 26 22 PM




Image 3 — Guitar Pro setting
Guitar Pro stylesheet setting showing Lyrics set to Below Staff.




Screenshot 2026-07-03 at 12 25 05 PM


Image 4 — Guitar Pro available options
Guitar Pro dropdown showing Above Staff, Below Staff, and Hide.




Screenshot 2026-07-03 at 12 25 17 PM


Image 5 — Guitar Pro available options (expanded menu drawer)

Guitar Pro dropdown showing Above Staff, Below Staff, and Hide.

Dominant language
TypeScript
Stars
1.9k
Forks
297
Avg merge
9h 41m
Merged PRs (30d)
41

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CoderLine/alphaTab

All issues in CoderLine/alphaTab

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.