Melody notes act like rests

Happens on these theorytabs and probably some others as well

Based on my tests it seems if the melody note is too high or too low then it will act like a rest (i.e. it will stop sounds, that means if you play an unbugged melody note or chord and then the bugged note then the sound will stop)

For the first 3 theorytabs bass notes in chords and the notes in chords can also be silent

1 Like

@Vaz123, thanks for the bug report. Does this also happen in Hookpad, or just in Theorytab? In one of the examples above, can you call out specifically which section/measure this is happening?

@Ryan it only happens in theorytabs

The conditions for the bug to happen varies from tab to tab, e.g. in Together Forever and Penantianku, any notes higher than F#4 act like rests (the measure and section don’t affect anything) whereas in Go Cart any notes higher than A3 act like rests (the measure and section don’t affect anything here either)

@Ryan also it doesn’t happen in a theorytab’s version history

Thanks for the detailed report, we know what’s going on, working on a fix now.

EDIT: I believe we’ve fixed this issue and will be pushing this to the site shortly. The issue is that Theorytab was getting confused in some cases and looking at the first analysis to decide which sound files to cache. In the case of Forever Together, the verse was much lower than the chorus, which is why the high notes of the chorus melody weren’t sounding. This also explains why the first analysis on each page was sounding correctly. This is a bug that was introduced with Hookpad v2.12.0, so we wouldn’t have seen it before then. We moved to this new caching pattern to improve the loading times of Theorytab pages generally.


@Ryan why for this theorytab sometimes the bug happens

@Ryan you didn’t fully fix the bug

Sorry for the late response, we are looking into this

@Ryan Why isn’t it fixed yet

@Vaz123, appreciate your patience. I’m reasonably confident that we’ve properly fixed the issue this time and will be pushing the a new version of the theorytab player shortly. Also noticed that the V11 display bug was fixed in Hookpad but never found its way to theorytab so that will also be included. Thanks again for the bug reports, they’re very helpful


It’s still not fixed

Make sure you load the sections from top to bottom and then the last section will have the bug

Also a way to fix it is to change the key of the section (idk how that works but it would be nice if I didn’t have to do that)

Hey @Vaz123, both of these examples appear to be working on my end, I’m wondering if your browser might have an outdated copy of theorytab somehow. The key change thing makes sense, the bug had to do with a section grabbing a different section’s melody to determine which sounds to download, but this lookup is repeated when the key changes to account for a potentially different melodic range. However, this should have been fixed in the last update.

@Ryan for me sometimes the bug happens and sometimes it doesn’t, idk why

if it doesn’t happen then try reloading the page and doing it again

and fyi I use Google Chrome and Windows 10

@Ryan it happened on these theorytabs as well (the bass notes in the chords are silent this time, I didn’t scroll at all I just let it load)

Yeah, I’m a little stumped, both of those examples appear to be working ok for me too. Can you try clearing your cache to see if you somehow have a stale resource that hasn’t been updated?

@Ryan for Flowers In The Window the bass notes in the C, D7 and Em7/B chords are silent and for Aurea Carmina the bass note in the Em7 chords are silent

Also try it on Windows 10 Google Chrome, I feel like that’s important

And also if I go to Google Chrome settings > Site Settings > Cookies and Site Data > See all cookies and site data then search hooktheory I can only find cache storage for the forum and hookpad

@Ryan By the way it also happens here (the E° chord in the instrumental):

@Ryan and now Go Cart is bugged again in the same way it was before


Yeah all of those examples working for me, also working on Windows machine in Chrome. I guess what we can do is revert back to the old caching system where all piano files are cached. It’s just missing one or two files probably so we’re not saving much by excluding them.