Fade out: track silent until the end
Maintainers usually reply within 1 day
Assessment
This issue has not been assessed yet.
Description
Is there an existing issue for this?
- I have searched the existing issues
I have read the contribution rules
- I have read CONTRIBUTING.md and, if any AI agent helped draft this issue, AGENTS.md.
AI authorship
AI-assisted (disclosure block included as described in AGENTS.md)
Current Behavior
- beat with fade out (or volume swell)
- after it: track silent until the end of the song
- changeTrackVolume(): no effect (volume × 0 = 0)
Expected Behavior
- fade out = only its beat
- next notes: normal track volume (like Guitar Pro)
Steps To Reproduce
- Track with: fade in on a beat, fade out on a later beat, more notes after
- Load the file
- Play the track (solo)
- Notes after the fade out: no sound
Link to jsFiddle, CodePen, Project
No response
Version and Environment
[AlphaTab][VersionInfo] alphaTab 1.8.4
[AlphaTab][VersionInfo] commit: 022a45c8e42370f9e12e68949d11eada370da83d
[AlphaTab][VersionInfo] build date: 2026-07-05T14:46:18.224Z
[AlphaTab][VersionInfo] High DPI: 1
[AlphaTab][VersionInfo] Platform: BrowserModule
[AlphaTab][VersionInfo] WebPack: false
[AlphaTab][VersionInfo] Vite: false
[AlphaTab][VersionInfo] Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/156.0.8078.4 Safari/537.36
[AlphaTab][VersionInfo] Window Size: 1400x1000
[AlphaTab][VersionInfo] Screen Size: 1400x1000
Also on: Chrome Android (same result) and Firefox Android (same result)
Same code in: 1.9.0-alpha.1963
Platform
Web
Anything else?
Cause:
- MidiFileGenerator._generateFade
- fade out → VolumeCoarse down to 0 (primary + secondary channel)
- no reset after
Fix idea:
- fade out + volume swell: add VolumeCoarse = track volume at beatStart + beatDuration
- track volume = playbackInfo.volume, or current volume automation if any
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 297
- Avg merge
- 3h 55m
- Merged PRs (30d)
- 53
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CoderLine/alphaTab
-
Respect systems layout of MusicXMLPossibly taken @Danielku15 claimed this 24 days ago. Open
CoderLine/alphaTab#2909 · 1 assignee ·
Maintainers usually reply within 1 day
-
Expose Lyrics in public apiPossibly taken @Danielku15 claimed this 24 days ago. Open
CoderLine/alphaTab#2908 · 1 assignee ·
Maintainers usually reply within 1 day
-
Show accentuations on tab-only stavesPossibly taken @Danielku15 claimed this 24 days ago. Open
CoderLine/alphaTab#2906 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Support tuning alterationsPossibly taken @kulek1 claimed this 76 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Add Optional Settings below-tab lyric placement for tab-only and standard+tab layoutsMay be free again @Danielku15 claimed this 112 days ago, and no pull request is open. Open
CoderLine/alphaTab#2776 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in CoderLine/alphaTab
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 86/100
awslabs/visual-asset-management-system#937 ·
Maintainers usually reply within 1 day
-
t0ggles
Difficulty 1/5 Under an hour Newbie friendliness 82/100
nolimits4web/swiper#8255 · 1 comment ·
Maintainers usually reply within 15 days
-
render: --variables-file (and --variables <path>) fails with "io.readFile is not a function" since 0.8.212Possibly taken @miguel-heygen claimed this today. Openbug triage/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
heygen-com/hyperframes#6830 ·
Maintainers usually reply within 1 day
-
bug launch local use
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
account: profile bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 5 days