How are your ears doing?


Recommended Posts

35 and can hear 17 pretty decent.

Can hear the clicks on 18, 19. Just the clicks though.

I am not sure how good and reliable this test is, as I know for sure my hearing is not the best.

I grew up playing in metal/punk bands since I was 12 years old, and we never wore earplugs. Only started wearing them in my early 30's in the last band I was in.

The reason I do not think this test is all that real, is because of the aforementioned bands I have played in, combined with a really bad infection, I actually went to an ear doctor in my early 20's.

I had 40% loss in my left ear and 15% loss in my right ear, and again I was in my early 20's. I never went back to an ear doctor as truthfully speaking, I am scared to find out how much worse it has gotten since then.

So yeah, take it with a grain of salt IMHO.

Is this legit? I've done some terrible things to my hears, and I can hear it all the way up to 20khz.

Even odder, I'm not even sure if I can actually hear 19khz, and if I do, it's barely, yet I can hear 20khz clearly.

It really depends on the headphones / speakers, many aren't rated to go above 16-20khz and when pushed above that, they may not reproduce the sound correctly. I have these Sennheiser headphones which can supposedly go up to a ridiculous 38khz.

I have fairly high-grade speakers and a microphone, so I simply recorded my speaker output through the mic. It's no surprise few people can hear above 17khz because the volume levels for the highest frequencies are barely above the noise level for a silent room with only a relatively silent computer in it. In other words it's very inconsistent. Also as pointed out previously, high frequencies at a sample rate of 48khz are far from pure.

For a real test you'd need a real frequency generator (one that doesn't resample) and to normalize the output levels.

Oh and I'm 24 and I can't hear above 15khz. 15khz is already quite faint. I blame 16 years of playing the piano for that. :(

well mine was done professionally becuase I kept hearing things and nobody else could hear (very unpleasant sounds) it everyone thought I lost my mind but I got a hearing test and that's what they said. It's very annoying.

That was done a few years ago it might have changed a bit but I still have it prolly more like 28,000Hz right now, but yeah I cannot stand to be around older electronics and basements of older houses becuase of this.

I avoid going to a couple chain restaurants becuase some of those have that sound emanating from somewhere.

but yeah it's very annoying hearing very high pitched sounds further then others

Most humans cannot hear past 20! At your age that would put your hearing at superhuman levels! Sorry, but I seriously doubt that you can hear those higher frequencies!

I'm 53 and can hear 16 clearly and I am almost sensing something at 17, perhaps I am imagining that I can, not sure!

I'm 32 and I heard all of them. I had problems hearing past 17 at normal volume (Then again I forgot to turn the speakers up) but once I put the ipod ear buds in I heard all of them. This might be because I wear ear protection when I use the lawn mower and snow blower. Back when I was in high school I could tell if the TV was on in the kitchen on mute from the next room just by the high pitch sound the TV made when it was turned on.

I have fairly high-grade speakers and a microphone, so I simply recorded my speaker output through the mic. It's no surprise few people can hear above 17khz because the volume levels for the highest frequencies are barely above the noise level for a silent room with only a relatively silent computer in it...

Thanks for that. I knew something was wrong. I could hear 17KHz very clearly and it was pretty loud, too, even though the speakers were turned down pretty low. Then I went to 18KHz and didn't hear anything until I turned up the volume quite a bit. I'm at a friend's house so I thought it was just these cheap speakers or the integrated audio.

I'm in my lower 30s and got to 18KHz for this test and this poor sound setup.

It really depends on the headphones / speakers, many aren't rated to go above 16-20khz and when pushed above that, they may not reproduce the sound correctly. I have these Sennheiser headphones which can supposedly go up to a ridiculous 38khz.

Well, to be honest, I'm not actually sure of my speakers' rating, but I'm inclined to believe they're better then the standard 20khz. The sounds did get progressively louder, so I dunno..

I'm 29 (will be 30 in 2 months) and I could hear up to 17khz. Weird thing though is that I couldn't really "hear" 18khz+, but when I played them all, my ears started to hurt a little bit. So I may not be able to "hear" it, but I can like "detect" it? Not sure what's going on. All I know is everything past 12khz hurts lol.

24 and I was able to hear up to 20kHz fine, for both 21 and 22 I can hear when the tone starts and stops, but I can't distinguish the tone itself from silence (it seems to make some kind of click when it starts and stops but I don't actually hear the tone itself, just the click....which is likely from my headphones starting and stopping when the sound starts and stops). Although, I am using Razer Carcharias, which have a frequency response up to 20kHz, so its possible my headphones are not even producing the sound (or at least not properly).

Nice to know that my hearing is as good as it is.....when I was younger and my school would do hearing tests (not sure why really, but it got us out of class so I went for it), the test giver always complimented me on my hearing. And I've never been a fan of music in general so I never really listen to any.....good to know that my hearing is as good as it has always been.

Back when I was in high school I could tell if the TV was on in the kitchen on mute from the next room just by the high pitch sound the TV made when it was turned on.

I still do that, nothing bugs me more than someone leaving a tv running with no sound and there's not enough other background noise to block out the high pitch of a tv....of course this doesn't happen often as LED/LCD/Plasma TVs don't do this, but whenever I'm around an older tv that was left on (and muted) I have to turn it off.

39 years old couldn't hear past 14kHz, panicked, popped ears and turned volume right up, heard up to 19kHz...

The click at the beginning spoils it a little as it makes it easier to imagine you are hearing something afterwards.

While true, I personally played each one multiple times, so I could be sure that I wasn't just thinking I was hearing something as each time I did it the tone sounded the exact same in pitch and loudness and was entirely discernible from background noise.....and after 20 I just couldn't hear crap, even with the click at the beginning.

This entire test is kind of meaningless anyways. I'm sure a vast majority of us are getting bad results due to distortions from our speakers, and possibly even sound chips. For example, standard earbuds won't go above 20khz, but many people have claimed to hear above it... most likely, that's just the earbuds trying to reproduce the noise, and failing badly by making a lower pitches noise.

Furthermore, the fact that you are listening to a digital sample of a particular pitch messes it up already. The sound file is most definitely not "pure" for a number of reasons.

They have analogue resonator machines specifically for this kind of test, for when you want to get a legitimate result.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!