Tests sometimes register inputs in the next frequency band

[MoralCode]

as a hearing user wearing bluetooth headphones, I gave this a try and noticed that, because i was able to hear the tones until they were rather quiet (i.e. low y values), i would sometimes click the spacebar too late and it would register the input for the next tone. (that is at least until i got bored a few frequencies in and started spamming the spacebar as you can see in the data haha)

I feel like it might help produce better data if the app waits for user input before moving onto the next tone

Seems like a cool app though! might also make for a fun tool for hearing users to compare different pairs of headphones and things like that with a little more empirical rigor than just subjective listening

[Jah-On]

Solution proposal: Omit the auto reset system and instead notify the user with a text node that auto hides/shows telling them the pitch has reached 0 and to either press space if they could hear the pitch or 0 if they could not. Does this seem like a reasonable proposal?

[MoralCode]

Yeah, i was sorta thinking of something like that as well!

[Jah-On]

Fixed in 53a6657, thanks!