Re:Locating the Source of a Mysterious Beep
by pavo-etc on Monday November 09, 2026 @08:56PM
(#50435100)
Woah this is cool. Another interesting simonw project based around sound through browsers. Lots of simple real world problems that can be tackled with this.
Re:Locating the Source of a Mysterious Beep
by dolmen on Tuesday November 10, 2026 @10:23AM
(#50441681)
A few additional constraints:
- the boxes are stacked
- the heavy boxes are at the bottom of a stack, and you can't stack a heavy box on top of a light one
- boxes aren't the same size
- some boxes are open, so must be put on top
- storage space and height are limited
Re:Locating the Source of a Mysterious Beep
by peri-cl on Monday November 09, 2026 @11:14PM
(#50435994)
Yes, but that's also O(log n) physical effort. This one's O(1) sitting on your butt.
(Solely for entertainment purposes: I think "physical binary search" is more properly O(n^{1/3} log(n)), or maybe O(n^{1/2} log(n)). Because real objects have sizes, and moving things (or moving between things) takes time proportional to distance).
Re:Locating the Source of a Mysterious Beep
by akoboldfrying on Tuesday November 10, 2026 @12:02AM
(#50436271)
Good point about the moving effort required. But if moving an object takes constant time, then it's O(n) overall -- since even though there are O(log n) steps, among all n-1 non-beeping items, either (i) all are moved exactly once (this case occurs when the beeping item is not moved during the initial halving) or (ii) half are never moved and the other half are moved exactly twice for O(2 * n/2) = O(n) work, and this term dominates the log n term.
Re:Locating the Source of a Mysterious Beep
by globular-toast on Tuesday November 10, 2026 @01:30AM
(#50436795)
You could also solve it by getting rid of the boxes of stuff you clearly don't need (if you needed it, it wouldn't still be in a box). The best way to solve a problem is to make the problem go away.
Re:Locating the Source of a Mysterious Beep
by tourmalinetaco on Tuesday November 10, 2026 @03:30AM
(#50437562)
That was my proposed solution to finding something just today; it didn’t work, but one of the bags ended up containing an old contract from General Development Company. Apparently a late family member had been buying some land down there through them, but county appraisers showed that the land never changed hands until after GDC’s bankruptcy. Not even their kid had heard about this, so it really makes me wonder what the story was behind that considering they lived in the Midwest (but did have some relatives nearby in Florida).
Re:Locating the Source of a Mysterious Beep
by wky on Tuesday November 10, 2026 @10:02AM
(#50441368)
In terms of physical effort taken it’s O(n). Move half, then a quarter, then one eighth, etc.
The number of partitions doesn’t matter either, the most straightforward case is the beeping box always being in the original room, so regardless of strategy you move n-1 boxes to narrow it down, and by symmetry it doesn’t matter which room beeps.
Re:Locating the Source of a Mysterious Beep
by tim333 on Tuesday November 10, 2026 @04:43PM
(#50446724)
I did roughly that to find my mum's missing hearing aid the other day. The bluetooth would locate which room it was in but not much more detailed than that. It was stuck to some orange peel in a recycling bin.
Re:Locating the Source of a Mysterious Beep
by radicality on Monday November 09, 2026 @10:36PM
(#50435755)
Oh, was gonna post a comment about this, I actually bought just last week their USBc version (Fotric Sonic 3), on eBay, for around $700. Works quite well, it has 64 mic array, I think it would be tough to replicate it to this level.
Lmk if anyone has any questions about it! It’s android-only, but I’ve gotten an agent to write a Mac version of it though haven’t tested yet.
Re:Locating the Source of a Mysterious Beep
by jcims on Monday November 09, 2026 @10:38PM
(#50435769)
Are you able to gather the multichannel recordings off the device? I’ve often wondered if you could do that, then replay a video while focusing on specific parts of the scene. Kind of like a virtual stethoscope.
Re:Locating the Source of a Mysterious Beep
by simonw on Tuesday November 10, 2026 @12:21AM
(#50436383)
For an intermittent beep, could you point it at a room and then leave it recording video for an hour, then come back later and scrub through that video looking for the source of the noise?
Re:Locating the Source of a Mysterious Beep
by dangistan202611 on Monday November 09, 2026 @11:01PM
(#50435907)
Does it work for infrequent sounds? The sound might for example come in the middle of the night for two seconds, loud enough to wake one up, then go away. If I leave it on, can it do continuous recording and max or threshold-based capture?
Re:Locating the Source of a Mysterious Beep
by simonw on Monday November 09, 2026 @11:20PM
(#50436022)
That should work. You could always have Claude Code run the server itself and explain to it the rough parameters of the sound (two seconds, late at night) - then let it listen for hours and occasionally tweak its own configuration to try to better capture what's happening.
In my case it identified that the likely beep was about every 62 seconds pretty quickly - then I confirmed that one of the recordings was the mystery sound and it locked in from there.
Re:Locating the Source of a Mysterious Beep
by luma on Tuesday November 10, 2026 @01:09AM
(#50436678)
Yes it can, works like a thermal camera. No recording (apart from stills), but you can watch the video image and, depending on overlay options, new sounds will be localized on the screen. Use mine to track down air leaks in a compressed air system, thing is magic.
Re:Locating the Source of a Mysterious Beep
by gandreani on Monday November 09, 2026 @09:37PM
(#50435407)
Hahahaha. You should slow down when you read
"The system worked as intended. It gave me the position of the beep to within about 40cm, then I dug through that specific pile of boxes and found an ancient carbon monoxide detector that desperately wanted its batteries replaced."
Re:Locating the Source of a Mysterious Beep
by thenthenthen on Monday November 09, 2026 @11:51PM
(#50436190)
Pff that sound is horrible, and sorta hard to locate (because of the pitch?). Anyway. None of my neighbours seem to care and in summer I used to hear an orchestra of beeps every 5 seconds. It was maddening, I was contemplating of buying 1000 batteries, print a manual and shoving it in peoples mailboxes, although somehow I think it wouldnt have made a difference. I moved out eventually (not because of the beeps)
Re:Locating the Source of a Mysterious Beep
by db48x on Tuesday November 10, 2026 @02:37AM
(#50437230)
It’s because it doesn’t have enough overtones, or a notable attack. You might have noticed that some trucks these days make a weird noise when they back up instead of a beep. They’re using white noise because it’s easier to locate; it has many overtones that allow your brain to pick the sound out of the background more easily, and thus more easily correlate the signals from both ears. You get a much more accurate location just from hearing that sound than you ever could with a pure tone.
Re:Locating the Source of a Mysterious Beep
by thenthenthen on Tuesday November 10, 2026 @02:56AM
(#50437356)
Interesting! I also feel the pulse is just to short… starting to question yourself if you actually heard something or that you are imagining it. Here the cars and trucks play musicals tunes or a crappy voice recording hahah
Re:Locating the Source of a Mysterious Beep
by tourmalinetaco on Tuesday November 10, 2026 @03:22AM
(#50437518)
That makes sense; we were searching for a family member’s blood sugar monitor just today and it barely seemed to come from any single direction. Ultimately it wasn’t the sound itself but the loudness of it that let us find it, because a blanket got shoved over it mid-search that we could deduce from there.
Re:Locating the Source of a Mysterious Beep
by HPsquared on Tuesday November 10, 2026 @04:30AM
(#50437952)
Consider a pure sine wave, it's impossible (in theory anyway) to match the signals from the left and right ears, and identify the time delay between the two signals because of aliasing: one sinen wave like just like the others, so there's no distinct signature to match and say "the sound reached the left ear 0.5 ms before it reached the right ear".
Animal species use this in different sounds they make. An alarm call has that kind of "smooth tone" characteristic, so a predator can't locate the source of the sound but it still works to raise the alarm. Meanwhile more social sounds are more "chirpy" and sharp, so they can locate each other.
Re:Locating the Source of a Mysterious Beep
by SenHeng on Tuesday November 10, 2026 @11:49AM
(#50442904)
I think some people are immune to beeps. My wife drives a Suzuki Crossbee and the fucking thing beeps every 10s for some alert or another. It drives me insane but she doesn’t notice it at all.
Examples
- beep: curve coming up ahead in X metres
- beep: curve coming up
- beep beep beep (too close to lane divider)
- beep: the speed limit is X
- beep: you’re speeding (no, I’m transitioning from a 60kmh to 40kmh section)
- beep: gps directions
- beep: gps directions again in case you missed it
Re:Locating the Source of a Mysterious Beep
by pseudohadamard on Tuesday November 10, 2026 @11:29PM
(#50449753)
A friend of mine drove a... something-or-other that dinged every time you exceeded the speed limit by 10 or 15mph/kmh. He gave it a dingectomy after meeting his goal of driving home from work without the dinging ever stopping.
Re:Locating the Source of a Mysterious Beep
by hypfer on Tuesday November 10, 2026 @02:07AM
(#50437020)
This is very humanizing. I like that.
Nicely done!
> Claude doesn’t have native audio input (yet), but it can run JavaScript and Python code that can analyze audio captured by a microphone.
LLMs can also do that with non-mic audio, btw. I had GLM (or was it qwen?) answer the question of "Why does the spotify version of the Metal Gear Rising" soundtrack sound so bad" - to great results.
Compared with the CD rips on archive.org, the noise floor was 27dB (!!!) higher, and, the whole thing was 10dB more compressed.
I cannot vouch for these specific numbers, but subtracting the good version from the bad one gave me a horrible delta wav file with lots to listen to, so there was definitely a _lot_ of difference.
Re:Locating the Source of a Mysterious Beep
by Anthony-G on Wednesday November 11, 2026 @10:12AM
(#50454392)
That’s terrible. As an Apple Music subscriber, I’m now wondering if I’m not experiencing music as it should be. For new recordings that I’m not previously familiar with, I’ve attributed the bad sound quality to the source not being mixed and/or mastered correctly. Until now, I hadn’t considered that Apple might also be processing the audio files.
When you say “very compressed” are referring to the dynamic range or a low bit-rate? If it’s dynamic range, that would be somewhat ironic. The loudness wars resulted in remastered CDs from the 90s and 2000s having a reduced dynamic range compared to the original album release. Back in the good old days, many What.CD users valued rips from vinyl over CD re-issues for this reason.
Re:Locating the Source of a Mysterious Beep
by simonw on Tuesday November 10, 2026 @12:17AM
(#50436355)
I spend $200/month on an Anthropic subscription which this all fit into easily, and I don't have a good estimate for the first part (in Claude Code Cloud with Opus 5.5), but the subsequent Fable 5.2 session on my laptop would have cost $31.04 at API prices (517.9k ctx / 331.4k out), according to `uvx agentsview serve`.
Re:Locating the Source of a Mysterious Beep
by gouggoug on Tuesday November 10, 2026 @12:37AM
(#50436492)
This article is about a weekend project and not a serious product, so what I'm saying below is not criticizing the author's approach — I'm making a point about something tangential.
The post touches on my biggest pet peeves about how many software engineers currently use AI at work: they ask it to "write out a problems.md file describing the problem we want to solve" then lob the output over the fence for the rest of the engineering org to review, often times without even disclosing they used AI to generate it (it's, of course, obvious).
AI can not do the reasoning for us; thinking that because it is great at writing code that works, the same applies to documents whose primary purpose is to demonstrate critical thinking, explore trade-offs, and reason through a problem is absurd.
In fact (or IMO?), this "problems.md" document is entirely unnecessary. In many cases, simply describing the issue and providing the relevant context is enough for AI to come up with a working solution.
AI can not do critical thinking (yet), so don't ask it to (and stop sending your fellow software engineers AI-slop RFCs).
Re:Locating the Source of a Mysterious Beep
by simonw on Tuesday November 10, 2026 @12:47AM
(#50436557)
Yeah, I wouldn't do this for code that I was expecting anyone else to review.
This is actually the first time I've told an agent to write out a "problems.md" document - it was an experiment to see if stating the problem provided decent results, as opposed to working directly on a spec.
It did seem to work well though. I was outsourcing as much judgement as possible to the model, and the model did a good job at making decisions that got me to my required end result.
In this case, the AI could do the reasoning for me. Opus 5.5 and Fable 5.2 are really good!
Re:Locating the Source of a Mysterious Beep
by Confiks on Tuesday November 10, 2026 @04:16AM
(#50437867)
> In fact (or IMO?), this "problems.md" document is entirely unnecessary. In many cases, simply describing the issue and providing the relevant context is enough for AI to come up with a working solution.
I don't mean to respond to your 'professional work' scenario, but I find it quite useful to first let it draft a PLAN.md, even when "in many cases" it would one-shot some implementation without it. I mostly prompt it with a problem statement, "write a PLAN.md", "ask me any questions in prose and numbered", "don't start implementation until my say-so". The back-and-forth questions are often pretty significant to the final result.
When you ask most models to write that plan, you see an extended thinking trace similar to implementation itself, making a lot of decisions all at once instead of while half of the implementation has been written and some architectural choices have been locked in. I then frequently adjust that plan to end up (IMO) with a much better implementation, or much better suited to my situation, with less shortcuts.
Re:Locating the Source of a Mysterious Beep
by uptrails on Tuesday November 10, 2026 @12:37AM
(#50436494)
I'm only here with a friendly tip for the designers of beeping devices: make sure to gradually ramp high-pitched beeps up and down, so that there's no sharp edge that an adversary could time.
Re:Locating the Source of a Mysterious Beep
by uptrails on Tuesday November 10, 2026 @01:01AM
(#50436639)
Not with any kind of precision if the slope is gentle and you're using random commodity devices with different frequency response, automatic gain control, etc.
Re:Locating the Source of a Mysterious Beep
by meatmanek on Tuesday November 10, 2026 @12:26PM
(#50443372)
You joke, but birds' alarm calls are usually fairly spectrally simple for exactly this reason: simple monotone sounds (or those with a very gradual frequency slide) with soft edges are hard for predators to locate while still communicating meaning to other prey animals.
On the other hand, warning calls are often spectrally complex. Think of a cat's hiss: it's nearly white noise, one of the easiest sounds to locate. By telling another animal exactly where you are, you project your confidence that you're able to win a fight.
Re:Locating the Source of a Mysterious Beep
by NitpickLawyer on Tuesday November 10, 2026 @12:43AM
(#50436527)
Ha! This reminded me of that old famous entry from bash org: "I can't find a server in my house. It responds to ping, but I can't physically locate it."
Re:Locating the Source of a Mysterious Beep
by foo12bar on Tuesday November 10, 2026 @01:18AM
(#50436729)
Why didn't you time the interval between the beeps? Then when the next beep was coming up, just listen to a particular part of the room or set of boxes until you found it.
Re:Locating the Source of a Mysterious Beep
by globular-toast on Tuesday November 10, 2026 @01:41AM
(#50436856)
This is the problem with technology. Some people just want to use it, so it's quite hard to tell whether this is really a quality of life improvement, or if it's just exciting for some weirdo (any programmer counts as weirdo here).
I've personally had to track down a beep before and used a similar technique as you suggest: time the beeps then be in right place to perform a kind of binary search to home in on it. I found a smoke alarm in the roof space above my flat, nailed to the top of the rafters that had been there since the building was built 20 years prior. It was annoying but I'm sure it took way less time and effort than "getting AI to do it".
Re:Locating the Source of a Mysterious Beep
by devilsdata on Tuesday November 10, 2026 @03:41AM
(#50437628)
This is also why it's been difficult for me to decide on portfolio projects to build. I just don't have anything I really need to build. I made a compound interest calculator as my first React app, but could have made an excel sheet or python script.
Re:Locating the Source of a Mysterious Beep
by skydhash on Tuesday November 10, 2026 @08:15AM
(#50439858)
I use a frustration threshold. A lot of times, I’ve got a working solution, but it’s not “right”, so when that become frustrating enough, I build something.
A few examples
dotnet does not work on OpenBSD, so to run jellyfin (supported by the infuse app on the apple tv), I have to run Linux. I wonder if I can replicate the API somehow
calibre is quite nice, but I don’t use much of its capabilities. I could try to make a simpler system for my use cases.
Re:Locating the Source of a Mysterious Beep
by Melatonic on Tuesday November 10, 2026 @01:32AM
(#50436807)
Not related to the beep but if you still have natural gas (guessing based on the old carbon monoxide detector) you likely also want to get a simple plugin alarm that also detects natural gas in its natural un burned state.
Carbon monoxide is only produced when it's burned and builds up. And is obviously very dangerous. But a small gas leak building up over time or an oven pilot out and left on is not great for you either.
Make sure you place it relatively near the ceiling as it pools up there apparently. Saved my life during Covid lockdowns
Re:Locating the Source of a Mysterious Beep
by globular-toast on Tuesday November 10, 2026 @01:48AM
(#50436908)
What I'd like to know is: did it make you feel good? Did you get a sense of satisfaction at having solved a problem? Do you feel more stronger and more capable than you were before?
What I've been finding is just setting AI loose like this doesn't give me any of that. I've decided not to think, so I don't feel any struggle. No struggle means no relief, no feeling of accomplishment. I also don't learn anything because AI read the paper for me. Learning is what I live for.
Re:Locating the Source of a Mysterious Beep
by simonw on Tuesday November 10, 2026 @02:47AM
(#50437286)
It makes me feel great!
There is no world in which I would have spent the days (more likely weeks) necessary to learn enough about audio analysis in both JavaScript and Python and the WebAudio APIs necessary to build this thing, just to help me identify an annoying beep.
Thanks to coding agents, I got to build a wildly ambitious system that still taught me a bunch of interesting things about audio analysis and network web application design, all in about an hour and a half of clock time.
The alternative wasn't learning those things at increased detail, it was not learning anything about them at all.
And I added more tools to my tool belt for the future. I now know that it's possible to measure distances to sounds using cheap devices over a network, and I've got code in a GitHub repository that shows exactly how to do that.
The trick where the server could inject additional JS modules into the clients without needing to refresh the page (and hence lose the microphone permission) was neat, too.
Re:Locating the Source of a Mysterious Beep
by globular-toast on Tuesday November 10, 2026 @04:20AM
(#50437885)
Well, I envy you, I guess.
I don't believe you learnt anything to any appreciable depth in 1.5 hours. I guess you learnt what's possible, but not much more. I get it, learning is learning and you got 1.5 hours' worth. Fair enough.
The bit I struggle with, though, is celebrating things being easy. I'm not excited by easy things. I like hard things. It's a bit like reading an account of how easy it was doing the Alpe d'Huez in a car. I'm more excited by people cycling up it because I know how difficult that is, or building the car. But driving it? Meh.
I do wonder if I'm descended from the people who built Stonehenge. I get restless if things are too easy. I need something hard, like erecting huge stones. But damn it's been nice being able to get that kind of satisfaction just sitting at a desk.
Re:Locating the Source of a Mysterious Beep
by sirtaj on Tuesday November 10, 2026 @05:31AM
(#50438370)
Surely it matters that you can choose the things you want to be hard. Practicing guitar is hard, but I choose to do it, because I want to be better at that specific thing and the journey is the point. But not everything we do is like that. I don't want paying my bills to be hard.
Re:Locating the Source of a Mysterious Beep
by globular-toast on Tuesday November 10, 2026 @06:32AM
(#50438844)
Those things you don't want to be hard are chores. Software wasn't a chore for me; I enjoyed it. I play guitar too, I'm really glad I have another hobby that isn't programming actually. I guess it would be like if I could get programmed like Neo in The Matrix, I say "I know guitar" and suddenly I'm Jimmy Page. I wouldn't bother. Anyone could do it so it would be pointless to play. That's how I feel about programming now.
Re:Locating the Source of a Mysterious Beep
by simonw on Tuesday November 10, 2026 @09:15AM
(#50440707)
No, it's more active than that.
It's closer to sitting in a lecture and actively asking questions, then discussing the material with others in the room (but still skipping the homework).
Re:Locating the Source of a Mysterious Beep
by ozyschmozy on Tuesday November 10, 2026 @01:57AM
(#50436961)
Several years ago, I had a bed that occasionally creaked, but I couldn't reproduce it, and by virtue of only happening when we were already in bed, it was not possible to just listen for where the creaking may be coming from. I had an idea to put a few esp32s with mics under the bed to do this exact thing, but figured it was not worth the effort. I guess I can just throw some tokens at it if it happens again
Re:Locating the Source of a Mysterious Beep
by voidUpdate on Tuesday November 10, 2026 @02:59AM
(#50437380)
> "I demonstrated it’s possible to give Claude Code ears"
You found out you can connect a microphone to a computer and have it record and process the audio? Well I'm glad you can be one of todays 10,000 https://xkcd.com/1053
Re:Locating the Source of a Mysterious Beep
by simonw on Tuesday November 10, 2026 @03:13AM
(#50437456)
The less obvious part is giving Claude five WebAudio ears spread around a room, wired together with WebSockets and using synchronized chirps to estimate each other's locations.
Re:Locating the Source of a Mysterious Beep
by skydhash on Tuesday November 10, 2026 @06:48AM
(#50438981)
Not less obvious as it’s generally the way for a group’s member to locate each other if a bit far away. And my receiver does the same for tuning itself. It has a wired microphone that you put in the middle of the room, with a general template on how to put the 5 speakers, then it will play sound on them to estimate phase shift and distance.
Re:Locating the Source of a Mysterious Beep
by jonathanstrange on Tuesday November 10, 2026 @03:46AM
(#50437661)
How did you "connect as many devices as you can spare to act as listeners"? I assume you didn't create iOS and Android versions of this and put them in app stores. Do you run Python on all of them, is there a direct way to connect devices as listeners I'm not aware of, or is this a PWA/web app? My guess is the last option but I'd be interested in this technical aspect.
Re:Locating the Source of a Mysterious Beep
by Confiks on Tuesday November 10, 2026 @03:51AM
(#50437693)
> I think the most interesting part of this project is that I demonstrated it’s possible to give Claude Code ears
Of course it can analyze audio. I made it detect Marijn Frank saying a high pitched "Hallo" in a much better way that I could have done myself (subtitle matching), namely by frequency analysis, in the process learning how that works with librosa: https://marijnfrankzegthallo.nl
Re:Locating the Source of a Mysterious Beep
by interloxia on Tuesday November 10, 2026 @04:52AM
(#50438095)
It's still a bit surprising the first time. Especially if you've been playing with these things for years now almost exclusively with text and perhaps checking for extra fingers now and then.
I didn't have birdnet to hand and wanted to identify something. It was hard to take a picture with my phone but easy to record. Turns out one of the models was able to identify it.
I guess the Americans might appreciate gunshot identification and localisation or someone might drive around in winter/summer recording the streets to listen for heat pumps that are on the way out so they can advertise repair services. I would like a local version for movement/presence detection based on footprints as an alternative to having pir sensors all over the place for my hall lights.
Re:Locating the Source of a Mysterious Beep
by chimpontherun on Tuesday November 10, 2026 @04:38AM
(#50437990)
Around '05 or so, the house we were staying in started beeping. Smoke alarm sounds, as usual. For almost a day we couldn't find the source. Contacted the owners -- they didn't know it either. They bought the house few years prior, so not much of a help.
Standing in the hallways listening at different angles, as the article says, didn't help. No Fable in '05 either.
So I had to improvise. Got a ~1 meter stick and two headphones (every headphone is a microphone, even if it sucks as a microphone). Plugged them into the stereo mic port, and started recording in Audacity. The phase shift between L and R pointed directly to the source. Took about 4 or 5 beeps to get the sucker.
Turns out, it was hiding above the ceiling tiles in the garage. My wife still tells this story to all her friends as one of my biggest life achievements. Everything I shipped, the companies I founded -- pales in comparison to finding a dead smoke alarm
Re:Locating the Source of a Mysterious Beep
by chimpontherun on Tuesday November 10, 2026 @04:58AM
(#50438131)
it didn't have to be sensitive or even high quality. The beep was loud enough to register on these improvised "mics" and the phase shift of up to 3ms (~50 samples at 16 kHz) was clearly visible
Re:Locating the Source of a Mysterious Beep
by frumiousirc on Tuesday November 10, 2026 @07:35AM
(#50439446)
The cross-correlation function can be applied to measure time shift between two waveforms, even those collected from different devices. The accuracy of this is not limited by the sample period. In fact, the two waveforms need not even have a common sample period. I think this approach could let simonw's network become self locating.
Re:Locating the Source of a Mysterious Beep
by brookst on Tuesday November 10, 2026 @06:47AM
(#50438965)
I have almost the opposite story.
Many many many years ago, I was a wee IT manager. Sort of a weird company, I was too young to be much more than smart kid who can install / fix anything.
Anyways, worked a few years there, made some friends, had one CAD engineer who was an utter jerk. In hindsight, probably a bully, but at the time just a really irritating person.
So that was my first foray into small electronics… worked up a small breadboard with a 555, some source of randomness I don’t remember now, a piezo speaker, and a 9v battery. It would emit a short beep at random intervals between roughly 60 and 240 minutes.
Re:Locating the Source of a Mysterious Beep
by pseudohadamard on Tuesday November 10, 2026 @11:22PM
(#50449716)
It's a temperature thing, if they're failing then they've reached their lowest-available-power level by about 2-4am depending on house conditions. Then when they warm up again later the beeping stops, until the next night. Crude test for a suspect alarm if you can't exactly monitor the battery voltage is to put it in the fridge for a few hours.
Re:Locating the Source of a Mysterious Beep
by zbentley on Tuesday November 10, 2026 @08:44AM
(#50440246)
In college, some friends bought (they were less imaginative than you) the equivalent, powered by a 2032 cell, and hid it in my room as a prank.
Good times. I bet it’s still magnetically attached to the inside of the steel riser column of one of their desk chairs, though the battery is likely long dead.
Re:Locating the Source of a Mysterious Beep
by rkagerer on Tuesday November 10, 2026 @07:18AM
(#50439264)
Could you elaborate on how you converted the phase shift into a precise direction? Or did you just hone in by adjusting the stick until the phase shift disappeared, then proceed in that direction?
Re:Locating the Source of a Mysterious Beep
by sandworm101 on Tuesday November 10, 2026 @08:38AM
(#50440167)
Not the OP, but the phase shift of a known frequency can be converted into a distance (portion of a wavelength) which can then be used to triangulate between the two microphones, yielding a vector to the target.
Re:Locating the Source of a Mysterious Beep
by chostetler on Tuesday November 10, 2026 @08:54AM
(#50440394)
Also not OP, but it seems it would be a bit different than this. The phase-distance can't differ by more than 1 meter between the signals, because the receivers are only 1 meter apart. And that phase difference doesn't give information about the distance of the chirp.
My guess is that the phase difference would give you a measurement between 0m and 1m. A phase difference of 0m indicates that the source lies on a plane perpendicular to the center of the meterstick, whereas a phase difference of 1m indicates that the source is collinear with the meterstick. A number in between there would give you a cone (?) of possible locations.
Re:Locating the Source of a Mysterious Beep
by chimpontherun on Tuesday November 10, 2026 @03:05PM
(#50445572)
I did in manually, i.e., visually. By looking at the phase shift and moving in direction of the channel that heard the beep first.
The beep frequency is about 3000-3500 Hz, which makes its wavelength about 10cm (1/3 of a foot). The piezo speaker in the smoke detector is so small that it takes 3-4 wave periods to go from silent to full blast. Meaning, if my stick was pointing perfectly to the source (it never was, obviously, but if), then one of the "mics" would hear the sound at full blast while the other still wouldn't hear anything.
So, I would have Audacity recording, hear the beep, stop the recording and zoom at the wavefront of the beep. Whichever mic shows the signal first, I'd move my stick (and the laptop) in that direction. After 2 or 3 moves and I was right under the source. Took me about 2 or 3 beeps at different stick orientation to understand that the sound is coming from above.
Re:Locating the Source of a Mysterious Beep
by steveBK123 on Tuesday November 10, 2026 @08:35AM
(#50440121)
> above the ceiling tiles
So I may in the future be the villain in a story like this if I am forgetful when I sell my apartment.
My upstairs neighbor is a moron who has flooded their apartment at least twice, so I have stashed moisture sensors into the access panels in multiple rooms as a sort of early warning system.
Re:Locating the Source of a Mysterious Beep
by Vinnl on Tuesday November 10, 2026 @09:07AM
(#50440605)
> My wife still tells this story to all her friends as one of my biggest life achievements. Everything I shipped, the companies I founded -- pales in comparison to finding a dead smoke alarm
Do you not feel this way about it yourself? I know I would.
Re:Locating the Source of a Mysterious Beep
by simonw on Tuesday November 10, 2026 @09:29AM
(#50440906)
I brought the carbon monoxide detector downstairs to show my wife after finding it with Claude and she said "you look like a cat that's proudly showing me the mouse that it caught".
Re:Locating the Source of a Mysterious Beep
by koolba on Tuesday November 10, 2026 @11:26AM
(#50442585)
My version of this story is coming back from turbulent red eye to this type of beeping, spending an hour walking around trying to figure it out it by ear, eventually giving up as it always seems to be somewhere else.
It wasn’t until the next day did I realize that it was two separate locations!
Re:Locating the Source of a Mysterious Beep
by looperhacks on Tuesday November 10, 2026 @04:51AM
(#50438091)
There's some beeping in my apartment, and we also cannot figure out where it's coming from. The problem is that it's really quiet - sometimes only my wife can hear it, but I can't. It also seems to occur randomly, we can only hear it every few days. I tried recording it with my phone, but it doesn't pick anything up. It drives me crazy
Re:Locating the Source of a Mysterious Beep
by dolmen on Tuesday November 10, 2026 @11:01AM
(#50442224)
> I tried recording it with my phone, but it doesn't pick anything up.
Doesn't pick anything or doesn't pick anything that you can hear back? Might still be worth giving for processing to an LLM as some nerd is able to locate a webcam location from the recorded sound and date [1].
Re:Locating the Source of a Mysterious Beep
by Aachen on Tuesday November 10, 2026 @12:37PM
(#50443492)
Phone mics are really frustrating. Haven't improved since the Nokia era as far as I can tell, but everyone's obsessed with camera quality. They're now better than human eyes while recording neighbours' music at 2am is either completely inaudible or solidly in the "what's your problem, I can barely even hear it's on" range
Re:Locating the Source of a Mysterious Beep
by thrawn0r on Tuesday November 10, 2026 @05:13AM
(#50438217)
Does this work with low rumbling sounds as well?
We have this annoying noise we hear from our bedroom, sounds like a dishwasher, but layouts of apartments around dont have their kitchens closeby.
Re:Locating the Source of a Mysterious Beep
by AnneTrotter on Tuesday November 10, 2026 @05:58AM
(#50438554)
Sound location is slightly different from sound identification. Is the noise constant or intermittent? Could be a clothes washer or drier, could be a sound system, could be pipes and water, could be sound transfer along a surface.
Re:Locating the Source of a Mysterious Beep
by simonw on Tuesday November 10, 2026 @09:25AM
(#50440855)
The problem was actually described in the agent output that I hadn't read when requested that additional feature:
> Distances only fix the layout up to translation, rotation and mirror image. That doesn't matter for the maths, but the map I'm shown has to match the real room, so the UI needs "rotate" and "flip" controls, or a way to say "Blue is next to the door".
Re:Locating the Source of a Mysterious Beep
by FerretFred on Tuesday November 10, 2026 @07:29AM
(#50439388)
I like that tale! However, I've found that my Wire Fox Terrier has somehow trained himself to distinguish a smoke alarm beep from the plethora of beeps in the house and came upstairs today at 3am waking me up to tell me batteries were running out. He followed me around until I located the culprit and then went back to bed. Next time he'll have upped his game to tell me which device it is. He's a good boi!
Re:Locating the Source of a Mysterious Beep
by osener on Tuesday November 10, 2026 @07:51AM
(#50439632)
I need this but for macos and browser tabs. Sometimes tabs or apps start randomly making sounds and play/pause button only deals with the latest playback. I want to be able to bring the tab or window making the sound directly to the front.
Re:Locating the Source of a Mysterious Beep
by BubbleRings on Tuesday November 10, 2026 @07:58AM
(#50439691)
I’ve been trying to think of other uses for the system. I’m wondering about this:
What use could a teacher make of a locator system, if students could identify their location and desire to be singled out for a moment, by simply clapping once?
In a big auditorium, a spotlight could track over to the student, who could then ask a question.
And/or, directional microphones could zero in on the student so the question could be played on the PA system.
Re:Locating the Source of a Mysterious Beep
by rjmill on Tuesday November 10, 2026 @08:39AM
(#50440172)
I love the idea of accidentally triggering this system.
You're trying to catch a fly that's been tormenting you. You clap your hands together to catch it, but it slips out. The motors on the spotlight whir. "No no no, cancel cancel!" It's too late. Your hunt now has an audience. The spotlight is on you. Your classmates are calling out when they see the fly, cheering your swats, and groaning when you miss. Even the professor is silently praying for your victory so they might be able to regain some semblance of control over the class.
Re:Locating the Source of a Mysterious Beep
by simonw on Tuesday November 10, 2026 @09:35AM
(#50440995)
I'm not convinced the heading "Here's how I meticulously typed out and debugged code implementing an algorithm from a 2007 Microsoft Research paper" would have been any more interesting.
Re:Locating the Source of a Mysterious Beep
by onaclov2000 on Tuesday November 10, 2026 @08:28AM
(#50440010)
Ok I wondered years and years ago about doing something similar to the triangulation Simon mentions but for a car, like setup a handful of mics, and let it record as you drive around, later process the data and it points at each thing making noise as you do the triangulation, in 3d so you can figure out oh that weird noise is coming from my tires, or the engine, or the muffler. Anywho, neat idea!
Re:Locating the Source of a Mysterious Beep
by meatmanek on Tuesday November 10, 2026 @12:12PM
(#50443224)
If you have an array of microphones all connected to a single device (so they share a sampling clock), and you know where in space every microphone is, this is a relatively solved problem. There are commercial "sound cameras" that have a panel covered in microphones to determine the angle the sound waves come in from.
I really like the idea of sound as automatic maintenance issue detection for cars. You could correlate repetitive noises with wheel speed or engine speed to help narrow down the subsystems involved, or even which cylinder is firing when a sound happens. Even one or two microphones would be helpful. You'd need to be careful not to accidentally record conversations inside the car and leak them to any maintenance tech, though.
Re:Locating the Source of a Mysterious Beep
by bermlee on Tuesday November 10, 2026 @08:32AM
(#50440061)
I've been ruminating on the inverse of this idea, where lavalier and directional mics would soon give way to any amateur being able to isolate a clean sample of any voice of your choosing, with AI processing recordings from two or three or four ordinary phone mics strewn about in an indoor environment.
In the meanwhile, every day around 10AM (sometime after, or later if I happen to not log in in the morning), my Mac makes a super loud DING! DING! sound, like a boxing match just started or a cable car trolley is about to pass through. I've tried using the Console and combed through the launchd.log to no avail. :)
Re:Locating the Source of a Mysterious Beep
by ddmf on Tuesday November 10, 2026 @08:39AM
(#50440178)
I randomly hear a succession of beeps in my house, random times, random days.
Was starting to drive me absolutely bonkers.
Then I saw a neighbour up a couple of houses reversing their SUV into their drive - it was the proximity sensor beeping - they had reversed with their car so many times that they'd become masters at performing the manoeuvre so the noise was always the same: "beep beep beepity beep beep beeeeeeeeeeeeeeep"
Re:Locating the Source of a Mysterious Beep
by pglevy on Tuesday November 10, 2026 @12:43PM
(#50443568)
Also under using-LLM-to-stop-incessant-beeping, we just moved and the new dishwasher plays like a full song in chime tones. I told chat, "I never want to hear these sounds again" and it instantly gave me the secret key code sequence to make it stop.
Now, what to do about the neighbor's wind chimes against humanity?
Re:Locating the Source of a Mysterious Beep
by mikewarot on Tuesday November 10, 2026 @09:52PM
(#50449247)
This is damned cool, and the audio version of Fox Hunting, which I used to do in my youth, with the Lake County Amateur Radio club here in Indiana. Someone would go and hide, somewhere within Lake County, with a 2 meter radio, transmitting for 1 minute, every 5 minutes, and we would find them.
One time, the guy was hiding under a pile of debris in the woods next to a high school. We found him at night time. I'll never forget it.
1) Move half the boxes to another room.
2) Listen for a beep and determine which room the beep comes from.
3) Take the boxes in that room and split it in half again.
4) Repeat until one box is left.
Alternatively, no.
I also feel like ordering the moves by lightest box first is reasonable as a real-world optimization.
(Solely for entertainment purposes: I think "physical binary search" is more properly O(n^{1/3} log(n)), or maybe O(n^{1/2} log(n)). Because real objects have sizes, and moving things (or moving between things) takes time proportional to distance).
O(log n) is if you can split the collection in half in an O(1) step, like, *shoving* the whole pile together as a unit
O(n) if you're moving items one at a time. So, splitting the pile in half is O(n)
O(n^{3/2}) if the project is growing out of control and walking distances start to matter
O(n^{4/3}) if that, but somehow it's taking place in 3-dimensions
I like to keep a lot of things in storage, and sometimes go through my boxes and “rediscover” things I haven’t used in a while.
Sure I have a lot of things I never use also. Some things I could sell, and some things I could give away, and some things I could throw away.
But just because a lot of things are in boxes, doesn’t mean that I might as well get rid of all of it for that reason alone.
And the piles of rubbish at the landfill are probably beeping too.
n. Sum(2^-i)=n
So its o(n. Log(n))
sum_{i=1}^{log_2(n)} {(n/2^i)} = n - 1
So it's O(n).
The number of partitions doesn’t matter either, the most straightforward case is the beeping box always being in the original room, so regardless of strategy you move n-1 boxes to narrow it down, and by symmetry it doesn’t matter which room beeps.
I'll see myself out...
https://www.youtube.com/shorts/ai1gIWacf0I
Of course, at ~$1,000 you'd probably want to rent it for this purpose, but it's interesting to know such a thing exists.
[1] https://navat.substack.com/p/diy-acoustic-camera-using-uma-1...
[2] https://www.minidsp.com/products/usb-audio-interface/uma-16-...
Lmk if anyone has any questions about it! It’s android-only, but I’ve gotten an agent to write a Mac version of it though haven’t tested yet.
eBay link to what I bought: https://www.ebay.com/itm/960060893216
In my case it identified that the likely beep was about every 62 seconds pretty quickly - then I confirmed that one of the recordings was the mystery sound and it locked in from there.
"The system worked as intended. It gave me the position of the beep to within about 40cm, then I dug through that specific pile of boxes and found an ancient carbon monoxide detector that desperately wanted its batteries replaced."
Maybe I should have asked Claude to help triangulate it for me.
Who would win?? :-)
I lack the courage to plant such a PCB prank device... it really feels like you could drive people completely crazy haha
Our dog goes outside and hides in the lavender bush if a smoke alarm starts making a "I need a battery" noise.
So I went into this project with very much the attitude that I would like to solve this class of problem forever.
Animal species use this in different sounds they make. An alarm call has that kind of "smooth tone" characteristic, so a predator can't locate the source of the sound but it still works to raise the alarm. Meanwhile more social sounds are more "chirpy" and sharp, so they can locate each other.
Examples
- beep: curve coming up ahead in X metres
- beep: curve coming up
- beep beep beep (too close to lane divider)
- beep: the speed limit is X
- beep: you’re speeding (no, I’m transitioning from a 60kmh to 40kmh section)
- beep: gps directions
- beep: gps directions again in case you missed it
- beep: yes again, turn left here you idiot!
Nicely done!
> Claude doesn’t have native audio input (yet), but it can run JavaScript and Python code that can analyze audio captured by a microphone.
LLMs can also do that with non-mic audio, btw. I had GLM (or was it qwen?) answer the question of "Why does the spotify version of the Metal Gear Rising" soundtrack sound so bad" - to great results.
Compared with the CD rips on archive.org, the noise floor was 27dB (!!!) higher, and, the whole thing was 10dB more compressed.
I cannot vouch for these specific numbers, but subtracting the good version from the bad one gave me a horrible delta wav file with lots to listen to, so there was definitely a _lot_ of difference.
It got the job done is what I want to say.
I bought an album from Apple Music, it was “in flames - reroute to remain” an album I’m very fond of when growing up.
Turns out that the digital version just sounded like trash, it sounded very compressed, so I had to find a CD to rip.
Could be interesting to know how they butchered it.
When you say “very compressed” are referring to the dynamic range or a low bit-rate? If it’s dynamic range, that would be somewhat ironic. The loudness wars resulted in remastered CDs from the 90s and 2000s having a reduced dynamic range compared to the original album release. Back in the good old days, many What.CD users valued rips from vinyl over CD re-issues for this reason.
https://xkcd.com/3100/
Then its solved.
The post touches on my biggest pet peeves about how many software engineers currently use AI at work: they ask it to "write out a problems.md file describing the problem we want to solve" then lob the output over the fence for the rest of the engineering org to review, often times without even disclosing they used AI to generate it (it's, of course, obvious).
AI can not do the reasoning for us; thinking that because it is great at writing code that works, the same applies to documents whose primary purpose is to demonstrate critical thinking, explore trade-offs, and reason through a problem is absurd.
In fact (or IMO?), this "problems.md" document is entirely unnecessary. In many cases, simply describing the issue and providing the relevant context is enough for AI to come up with a working solution.
AI can not do critical thinking (yet), so don't ask it to (and stop sending your fellow software engineers AI-slop RFCs).
This is actually the first time I've told an agent to write out a "problems.md" document - it was an experiment to see if stating the problem provided decent results, as opposed to working directly on a spec.
It did seem to work well though. I was outsourcing as much judgement as possible to the model, and the model did a good job at making decisions that got me to my required end result.
In this case, the AI could do the reasoning for me. Opus 5.5 and Fable 5.2 are really good!
I don't mean to respond to your 'professional work' scenario, but I find it quite useful to first let it draft a PLAN.md, even when "in many cases" it would one-shot some implementation without it. I mostly prompt it with a problem statement, "write a PLAN.md", "ask me any questions in prose and numbered", "don't start implementation until my say-so". The back-and-forth questions are often pretty significant to the final result.
When you ask most models to write that plan, you see an extended thinking trace similar to implementation itself, making a lot of decisions all at once instead of while half of the implementation has been written and some architectural choices have been locked in. I then frequently adjust that plan to end up (IMO) with a much better implementation, or much better suited to my situation, with less shortcuts.
[1] https://github.com/obra/superpowers
On the other hand, warning calls are often spectrally complex. Think of a cat's hiss: it's nearly white noise, one of the easiest sounds to locate. By telling another animal exactly where you are, you project your confidence that you're able to win a fight.
I've personally had to track down a beep before and used a similar technique as you suggest: time the beeps then be in right place to perform a kind of binary search to home in on it. I found a smoke alarm in the roof space above my flat, nailed to the top of the rafters that had been there since the building was built 20 years prior. It was annoying but I'm sure it took way less time and effort than "getting AI to do it".
A few examples
dotnet does not work on OpenBSD, so to run jellyfin (supported by the infuse app on the apple tv), I have to run Linux. I wonder if I can replicate the API somehow
calibre is quite nice, but I don’t use much of its capabilities. I could try to make a simpler system for my use cases.
And so on.
I spelled it out a bit more on Bluesky etc:
> There is a mysterious intermittent beep coming from somewhere in your room of unopened boxes. Do you:
> 1. Open the boxes methodically one by one until you find it
> 2. Vibe code software that lets you set up two laptops, two iPads and a phone in various points around the room to triangulate it
https://bsky.app/profile/simonwillison.net/post/3mzvuqd4ndk2...
... your awesome vibecoded project has now told you what to unpack first.
Carbon monoxide is only produced when it's burned and builds up. And is obviously very dangerous. But a small gas leak building up over time or an oven pilot out and left on is not great for you either.
Make sure you place it relatively near the ceiling as it pools up there apparently. Saved my life during Covid lockdowns
What I've been finding is just setting AI loose like this doesn't give me any of that. I've decided not to think, so I don't feel any struggle. No struggle means no relief, no feeling of accomplishment. I also don't learn anything because AI read the paper for me. Learning is what I live for.
There is no world in which I would have spent the days (more likely weeks) necessary to learn enough about audio analysis in both JavaScript and Python and the WebAudio APIs necessary to build this thing, just to help me identify an annoying beep.
Thanks to coding agents, I got to build a wildly ambitious system that still taught me a bunch of interesting things about audio analysis and network web application design, all in about an hour and a half of clock time.
The alternative wasn't learning those things at increased detail, it was not learning anything about them at all.
And I added more tools to my tool belt for the future. I now know that it's possible to measure distances to sounds using cheap devices over a network, and I've got code in a GitHub repository that shows exactly how to do that.
The trick where the server could inject additional JS modules into the clients without needing to refresh the page (and hence lose the microphone permission) was neat, too.
I don't believe you learnt anything to any appreciable depth in 1.5 hours. I guess you learnt what's possible, but not much more. I get it, learning is learning and you got 1.5 hours' worth. Fair enough.
The bit I struggle with, though, is celebrating things being easy. I'm not excited by easy things. I like hard things. It's a bit like reading an account of how easy it was doing the Alpe d'Huez in a car. I'm more excited by people cycling up it because I know how difficult that is, or building the car. But driving it? Meh.
I do wonder if I'm descended from the people who built Stonehenge. I get restless if things are too easy. I need something hard, like erecting huge stones. But damn it's been nice being able to get that kind of satisfaction just sitting at a desk.
It's closer to sitting in a lecture and actively asking questions, then discussing the material with others in the room (but still skipping the homework).
Going through life angry that things that once were hard and are now easy go directly against why we are doing the hard things.
To your example. Building Stonehenge was HARD back in 3000BC. Now, a guy and some hydraulic tools could do it as a weekend project.
LLMs have made "hard" (but previously solved) problems "easy". And it opens up a large window of new hard problems.
You found out you can connect a microphone to a computer and have it record and process the audio? Well I'm glad you can be one of todays 10,000 https://xkcd.com/1053
Of course it can analyze audio. I made it detect Marijn Frank saying a high pitched "Hallo" in a much better way that I could have done myself (subtitle matching), namely by frequency analysis, in the process learning how that works with librosa: https://marijnfrankzegthallo.nl
I didn't have birdnet to hand and wanted to identify something. It was hard to take a picture with my phone but easy to record. Turns out one of the models was able to identify it.
I guess the Americans might appreciate gunshot identification and localisation or someone might drive around in winter/summer recording the streets to listen for heat pumps that are on the way out so they can advertise repair services. I would like a local version for movement/presence detection based on footprints as an alternative to having pir sensors all over the place for my hall lights.
Standing in the hallways listening at different angles, as the article says, didn't help. No Fable in '05 either.
So I had to improvise. Got a ~1 meter stick and two headphones (every headphone is a microphone, even if it sucks as a microphone). Plugged them into the stereo mic port, and started recording in Audacity. The phase shift between L and R pointed directly to the source. Took about 4 or 5 beeps to get the sucker.
Turns out, it was hiding above the ceiling tiles in the garage. My wife still tells this story to all her friends as one of my biggest life achievements. Everything I shipped, the companies I founded -- pales in comparison to finding a dead smoke alarm
Many many many years ago, I was a wee IT manager. Sort of a weird company, I was too young to be much more than smart kid who can install / fix anything.
Anyways, worked a few years there, made some friends, had one CAD engineer who was an utter jerk. In hindsight, probably a bully, but at the time just a really irritating person.
So that was my first foray into small electronics… worked up a small breadboard with a 555, some source of randomness I don’t remember now, a piezo speaker, and a 9v battery. It would emit a short beep at random intervals between roughly 60 and 240 minutes.
Stashed it above the ceiling tiles in his office.
Good times. I bet it’s still magnetically attached to the inside of the steel riser column of one of their desk chairs, though the battery is likely long dead.
My guess is that the phase difference would give you a measurement between 0m and 1m. A phase difference of 0m indicates that the source lies on a plane perpendicular to the center of the meterstick, whereas a phase difference of 1m indicates that the source is collinear with the meterstick. A number in between there would give you a cone (?) of possible locations.
The beep frequency is about 3000-3500 Hz, which makes its wavelength about 10cm (1/3 of a foot). The piezo speaker in the smoke detector is so small that it takes 3-4 wave periods to go from silent to full blast. Meaning, if my stick was pointing perfectly to the source (it never was, obviously, but if), then one of the "mics" would hear the sound at full blast while the other still wouldn't hear anything.
So, I would have Audacity recording, hear the beep, stop the recording and zoom at the wavefront of the beep. Whichever mic shows the signal first, I'd move my stick (and the laptop) in that direction. After 2 or 3 moves and I was right under the source. Took me about 2 or 3 beeps at different stick orientation to understand that the sound is coming from above.
So I may in the future be the villain in a story like this if I am forgetful when I sell my apartment.
My upstairs neighbor is a moron who has flooded their apartment at least twice, so I have stashed moisture sensors into the access panels in multiple rooms as a sort of early warning system.
Do you not feel this way about it yourself? I know I would.
It wasn’t until the next day did I realize that it was two separate locations!
To answer the inevitable question, EE students with a tiny amount of spare time. Not much, but just enough.
Doesn't pick anything or doesn't pick anything that you can hear back? Might still be worth giving for processing to an LLM as some nerd is able to locate a webcam location from the recorded sound and date [1].
[1] https://www.youtube.com/shorts/4CEHH2WyRKs
Maybe the directionality of typical speaker and mic spoils an attempt to apply a 1/r^2 fit?
> Distances only fix the layout up to translation, rotation and mirror image. That doesn't matter for the maths, but the map I'm shown has to match the real room, so the UI needs "rotate" and "flip" controls, or a way to say "Blue is next to the door".
https://github.com/simonw/beep-locator/blob/main/problem.md#...
It was nearly impossible to get decent repeatable results.
In fact about:processes is a good enough replacement: just sort by CPU usage descending and you'll find the source in the top 5.
What use could a teacher make of a locator system, if students could identify their location and desire to be singled out for a moment, by simply clapping once?
In a big auditorium, a spotlight could track over to the student, who could then ask a question.
And/or, directional microphones could zero in on the student so the question could be played on the PA system.
You're trying to catch a fly that's been tormenting you. You clap your hands together to catch it, but it slips out. The motors on the spotlight whir. "No no no, cancel cancel!" It's too late. Your hunt now has an audience. The spotlight is on you. Your classmates are calling out when they see the fly, cheering your swats, and groaning when you miss. Even the professor is silently praying for your victory so they might be able to regain some semblance of control over the class.
You didn't.
Did you really learn nothing at all from this?
I really like the idea of sound as automatic maintenance issue detection for cars. You could correlate repetitive noises with wheel speed or engine speed to help narrow down the subsystems involved, or even which cylinder is firing when a sound happens. Even one or two microphones would be helpful. You'd need to be careful not to accidentally record conversations inside the car and leak them to any maintenance tech, though.
In the meanwhile, every day around 10AM (sometime after, or later if I happen to not log in in the morning), my Mac makes a super loud DING! DING! sound, like a boxing match just started or a cable car trolley is about to pass through. I've tried using the Console and combed through the launchd.log to no avail. :)
Was starting to drive me absolutely bonkers.
Then I saw a neighbour up a couple of houses reversing their SUV into their drive - it was the proximity sensor beeping - they had reversed with their car so many times that they'd become masters at performing the manoeuvre so the noise was always the same: "beep beep beepity beep beep beeeeeeeeeeeeeeep"
How loud does that noise need to be though?!
Now, what to do about the neighbor's wind chimes against humanity?
One time, the guy was hiding under a pile of debris in the woods next to a high school. We found him at night time. I'll never forget it.
This is an excellent use of LLM generated code.