Received: from PCH.mit.edu (18.7.21.50) by mail.efplus.com (192.168.0.8) with Microsoft SMTP Server (TLS) id 8.3.485.1; Wed, 7 Oct 2020 04:52:04 -0700 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 097BgMNr028031; Wed, 7 Oct 2020 07:43:04 -0400 Received: from outgoing-exchange-7.mit.edu (OUTGOING-EXCHANGE-7.MIT.EDU [18.9.28.58]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 097BgLxg028028 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 7 Oct 2020 07:42:21 -0400 Received: from oc11exedge2.exchange.mit.edu (OC11EXEDGE2.EXCHANGE.MIT.EDU [18.9.3.18]) by outgoing-exchange-7.mit.edu (8.14.7/8.12.4) with ESMTP id 097BfpLQ015369 for ; Wed, 7 Oct 2020 07:42:21 -0400 Received: from w92exhyb1.exchange.mit.edu (18.7.71.12) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 7 Oct 2020 07:41:51 -0400 Received: from oc11exhyb6.exchange.mit.edu (18.9.1.111) by w92exhyb1.exchange.mit.edu (18.7.71.12) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 7 Oct 2020 07:42:16 -0400 Received: from NAM12-MW2-obe.outbound.protection.outlook.com (104.47.66.41) by oc11exhyb6.exchange.mit.edu (18.9.1.111) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 7 Oct 2020 07:42:16 -0400 Received: from MW3PR05CA0002.namprd05.prod.outlook.com (2603:10b6:303:2b::7) by BL0PR01MB4212.prod.exchangelabs.com (2603:10b6:208:4e::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.37; Wed, 7 Oct 2020 11:42:14 +0000 Received: from CO1NAM03FT029.eop-NAM03.prod.protection.outlook.com (2603:10b6:303:2b:cafe::4e) by MW3PR05CA0002.outlook.office365.com (2603:10b6:303:2b::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3455.21 via Frontend Transport; Wed, 7 Oct 2020 11:42:14 +0000 Received: from mail-lf1-f45.google.com (209.85.167.45) by CO1NAM03FT029.mail.protection.outlook.com (10.152.80.168) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.34 via Frontend Transport; Wed, 7 Oct 2020 11:42:14 +0000 Received: by mail-lf1-f45.google.com with SMTP id b22so1871297lfs.13 for ; Wed, 07 Oct 2020 04:42:14 -0700 (PDT) From: Alan Pearce To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Wed, 7 Oct 2020 04:42:00 -0700 Subject: Re: [EE] Looking for technique to record audio after level exceeds some value Thread-Topic: [EE] Looking for technique to record audio after level exceeds some value Thread-Index: AdacoEbF8Ays7fm8RruGh6+VWrr+ag== Message-ID: References: List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: TS500.efplus4.local X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-Exchange-Organization-SenderIdResult: Pass X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: received-spf: Pass (protection.outlook.com: domain of googlemail.com designates 209.85.167.45 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.167.45; helo=mail-lf1-f45.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=c0bG9WJdZX8Ev86C60Qn+w6IKnnS3fyjfcCWSSgvmPw=; b=f49TZdrrOxFHMb7iIWpWn7yi/JMfy0zgzSsi4pZ1XWJRdM6urlkASo0uc6S0fX1Udl 4hPngOMU5D3+vTsuD8o9CH73TpfV39eJQWMiCvgMa2xz5Y5Iz8UwfXFxIsaAsw2tGBEJ aIEMdK5yAUEsGPdTmOz0646EmgCNTmquSCM5gtA2Rbeb4KVZelUQblf4y5YZvMCNZjIM rwMrIXm6cWK5bvY31RATsPVmLEGXZeIyerLf14fI87Rupj1cKBPKnrRwFHokZLJbIGJj g9py/hfbelwqrEnRJCvWidLu/J4daf2NjSqkVQHbvmOp9MikjqK6OfO8bBjfNjY4NxT9 0OWQ== authentication-results: spf=pass (sender IP is 209.85.167.45) smtp.mailfrom=googlemail.com; mit.edu; dkim=pass (signature was verified) header.d=googlemail.com;mit.edu; dmarc=pass action=none header.from=googlemail.com; errors-to: piclist-bounces@mit.edu list-id: "Microcontroller discussion list - Public." list-post: x-beenthere: piclist@mit.edu x-mailman-version: 2.1.6 x-received: by 2002:a19:94:: with SMTP id 142mr796478lfa.577.1602070931845; Wed, 07 Oct 2020 04:42:11 -0700 (PDT) x-topics: [EE] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 > Many of the cheap dashcams have sound and record on a loop > so you could have video and audio? That was my thought too. If it could be mounted so the thump of the 'explosion' triggered the crash detector then the clip would not get overwritten if left recording. Would make an interesting court exhibit if there was a major 'bang' resulting in emergency services callout, especially after multiple complaints to the HVAC engineers :) On Tue, 6 Oct 2020 at 23:50, Clint Jay wrote: > > Many of the cheap dashcams have sound and record on a loop so you could > have video and audio? > > On Tue, 6 Oct 2020, 20:19 Dwayne Reid, wrote: > > > Good day to all. > > > > I have a peculiar problem and I am hoping there is an off-the-shelf > > solution. > > > > It is approaching winter in Canada, which means that heating season > > is about to be on us. One of the roof-top HVAC boxes on our building > > appears to have a gas ignition problem. I hear explosions both quiet > > and loud when the heater turns on. > > > > This is obviously a gas ignition problem and we have called the > > service people a couple of times to get this fixed before the heat > > exchanger becomes damaged. Specifically, what I think is that the > > fuel gas (Natural Gas) is accumulating in some area away from the > > ignitor, reaching some level higher than the Lower Explosive Level, > > then some traces of the fuel reaching the ignitor. > > > > But the service people can't see any problem and they are questioning > > whether I am just imagining the problem. > > > > What I would like to do is to set up one of my spare Android devices > > with the microphone in the heating duct. But I need some way to have > > the device record just of few seconds BEFORE the explosion occurs as > > well as a few seconds AFTER the explosion occurs. > > > > Kind of like how pre-trigger works with a DSO. > > > > I've been looking but have not yet found an app that does this. I'm > > hoping that someone here might have a suggestion. > > > > Note that I'm not married to the idea of using an Android device - > > just that's what I have handy. I could also set up a laptop or > > netbook running Windows or DOS if I can find an appropriate application= .. > > > > I do have a fair amount of audio equipment here - mixers, preamps of > > various types, microphones ranging from really inexpensive to stupid > > expensive, audio recorders of various types. > > > > Problem is that none of the audio recorders that I have (DAT, SD-card > > based, Compact Flash based, etc) have the capability to continuously > > record a buffer, then capture several seconds before and after the > > loud sound occurs. > > > > Individual files with time stamps would also be desirable. > > > > IBM compatible Shareware or paid Android app is just fine. > > > > Suggestions gratefully accepted. > > > > dwayne > > > > -- > > Dwayne Reid > > Trinity Electronics Systems Ltd Edmonton, AB, CANADA > > 780-489-3199 voice 780-487-6397 fax 888-489-3199 Toll Free > > www.trinity-electronics.com > > Custom Electronics Design and Manufacturing > > > > -- > > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > > View/change your membership options at > > http://mailman.mit.edu/mailman/listinfo/piclist > > > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .