Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#2,776 0 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 1 dia

@Danielku15 já está trabalhando nisso.

Desde 10/7/2026.

Avaliação

Esta issue ainda não foi avaliada.

Descrição

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.

Linguagem predominante
TypeScript
Estrelas
1.9k
Forks
297
Merge médio
9h 2min
PRs com merge (30d)
44

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de CoderLine/alphaTab

Todas as issues de CoderLine/alphaTab

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.