Re:What’s up with the Beep driver in Windows 7? (2010)
by maaaats on Tuesday January 13, 2015 @05:48AM
(#8879002)
This reminds me of a talk by two of the Nobel price winners in medicine this year (Moser couple). They, together with O'Keefe, measured brain activity in various parts of the brain. Before computer loggers and visualization was very viable, neuroscientists hooked the sensors up to speakers. So they sat and watched mice move in a maze, and listened to various parts of the brain "fire".
Re:What’s up with the Beep driver in Windows 7? (2010)
by stinos on Tuesday January 13, 2015 @11:37AM
(#8880842)
The listening is still being done today in experiments. An experienced neurophysiologist (in the particular field of single cell recordings) can distinguish the sound of an actual braincell firing, or groups thereof, from all surrounding noise. Which is sometimes more convenient than recording the signal, feeding it into rather complicated template matching algorithms and waiting for results. Especially since braincells might die while being recorded from, so you have to decide quickly.
Re:What’s up with the Beep driver in Windows 7? (2010)
by raverbashing on Tuesday January 13, 2015 @04:28AM
(#8878813)
Oh wow, this brings memories.
But I didn't use it for user space debugging, but for kernel space debugging on windows.
Set a different set of beeps for different steps in the code, then listen for the beeps as things unfold.
Re:What’s up with the Beep driver in Windows 7? (2010)
by WorldWideWayne on Tuesday January 13, 2015 @10:35AM
(#8880438)
I was initially surprised to find that Beep is still available in the latest .NET framework (in multiple forms) because it just seems so archaic, but I guess the most basic audio feedback can still be useful.
- http://msdn.microsoft.com/en-us/library/system.console.beep%...
- http://msdn.microsoft.com/en-us/library/kz27k38z%28v=vs.90%2...
[dead]
You set up uniquely pitched beeps for certain events, and then listen for the order in which the events occur. It worked because a call into Beep() halted the entire process and all of its threads for the duration of the beep. It prevents multiple threads from beeping at the same time, and it slowed everything down just enough so that you could pick up each individual event with your ear. It beat the hell out of staring at a massive log file.