Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > sci.electronics.design > #460212

Re: Microphone risk factors

From Jan Panteltje <pNa0nStpealmtje@yahoo.com>
Newsgroups sci.electronics.design
Subject Re: Microphone risk factors
Date 2017-05-14 08:40 +0000
Organization Aioe.org NNTP Server
Message-ID <of956k$ui5$1@gioia.aioe.org> (permalink)
References (1 earlier) <mbhL8BP0acdfEJUhnospam@invalid.com> <of4t4l$7ce$1@dont-email.me> <of7f7b$p5o$1@gioia.aioe.org> <of7kne$tbc$1@dont-email.me> <of7lq8$136v$1@gioia.aioe.org>

Show all headers | View raw


On a sunny day (Sat, 13 May 2017 19:12:08 GMT) it happened Jan Panteltje
<pNa0nStpealmtje@yahoo.com> wrote in <of7lq8$136v$1@gioia.aioe.org>:

>On a sunny day (Sat, 13 May 2017 11:57:17 -0700) it happened Don Y
><blockedofcourse@foo.invalid> wrote in <of7kne$tbc$1@dont-email.me>:
>
>>You're surrounded by the noise of the mechanism (you're making 35-75
>>tablets concurrently) and trying to hear a little "pop" that is
>>muffled inside a steel box -- that is MOVING past your sensor.
>
>Digital signal processing.
>The problem is not the mike.
>
>You need the spectrum of the 'pop', do an FFT, and look for it.
>
>There are other ways, train a neural net etc etc.
>
>No mike is perfect.
>And this seems in the LF range, no wideband needed.
>
>It is just a specific pressure wave,
>
>But I do not want to start an in depth discussion about mikes,
>I had my part of that, worked in TV and film studio.
>Almost as many opinions as people.
>And I have no experience with MEMS mikes.
>
>You could try learning to write some code.
>In C that is :-)
>
>Endlessly babbling about it gets you nowhere.

So this is how you _could_ go about it:
Mount a microphone near that process, use one that is not obviously crap.
Take your decent quality PC / laptop and record.
Start you stopwatch watch and make a note of the times things go wrong (pop).
Maybe MAKE things go wrong to get the pop sound.

Thank everyone, leave the mike in place, bolted or welded,
create a job for somebody guarding it, contact the White House you created an other American job,
also hire somebody to train these people who will in turn watch the microphone and prevent it from being
moved or obstacles placed in front of it or it being used for other purposes.
thank everybody again, and your president of course,
go home, run your recording, do some FFT, look if you see a difference between 'plop' and normal 'pluff'
sounds, if not contact everybody involved that more money and resources are needed.
If there is a visible difference subtract the  spectra, and use that as trigger for whatever,
counter, activator, email, alarm, sprinkler, fire brigade, anti-terrorist squad,
flashing lights, you name it.
Homework, could be fun.
Once you have the soft (IF you have the soft) then sell them your PC, train a user to configure it
boot it, mail the White House again you created  yet an other American job,
and do not forget to _charge_ for it.

 
Solar cells sucking , what do you know.

Back to sci.electronics.design | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Microphone risk factors Don Y <blockedofcourse@foo.invalid> - 2017-05-10 21:27 -0700
  Re: Microphone risk factors Phil Allison <pallison49@gmail.com> - 2017-05-10 21:39 -0700
  Re: Microphone risk factors jrwalliker@gmail.com - 2017-05-11 07:01 -0700
    Re: Microphone risk factors Don Y <blockedofcourse@foo.invalid> - 2017-05-11 11:06 -0700
      Re: Microphone risk factors piglet <erichpwagner@hotmail.com> - 2017-05-12 09:02 +0100
      Re: Microphone risk factors "Michael Kellett" <nospam@invalid.com> - 2017-05-12 16:02 +0100
        Re: Microphone risk factors Don Y <blockedofcourse@foo.invalid> - 2017-05-12 09:37 -0700
          Re: Microphone risk factors "Michael Kellett" <nospam@invalid.com> - 2017-05-12 18:08 +0100
            Re: Microphone risk factors Don Y <blockedofcourse@foo.invalid> - 2017-05-12 11:02 -0700
              Re: Microphone risk factors Phil Allison <pallison49@gmail.com> - 2017-05-12 17:44 -0700
              Re: Microphone risk factors Terry Newton <nbill@bellsouth.net> - 2017-05-13 17:19 +0000
                Re: Microphone risk factors Don Y <blockedofcourse@foo.invalid> - 2017-05-13 11:57 -0700
                Re: Microphone risk factors Jan Panteltje <pNa0nStpealmtje@yahoo.com> - 2017-05-13 19:12 +0000
                Re: Microphone risk factors Jan Panteltje <pNa0nStpealmtje@yahoo.com> - 2017-05-14 08:40 +0000
                Re: Microphone risk factors Jan Panteltje <pNa0nStpealmtje@yahoo.com> - 2017-05-14 09:17 +0000
                Re: Microphone risk factors Jan Panteltje <pNa0nStpealmtje@yahoo.com> - 2017-05-14 10:49 +0000
                Re: Microphone risk factors Terry Newton <nbill@bellsouth.net> - 2017-05-13 19:26 +0000
                Re: Microphone risk factors (OT -- long) Don Y <blockedofcourse@foo.invalid> - 2017-05-13 13:37 -0700
            Re: Microphone risk factors "dcaster@krl.org" <dcaster@krl.org> - 2017-05-13 11:06 -0700
              Re: Microphone risk factors Don Y <blockedofcourse@foo.invalid> - 2017-05-13 12:11 -0700
              Re: Microphone risk factors krw@notreal.com - 2017-05-13 20:36 -0400

csiph-web