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; Tue, 6 Oct 2020 17:01:31 -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 096NrXkK005835; Tue, 6 Oct 2020 19:53:41 -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 096NrVdW005800 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 6 Oct 2020 19:53:31 -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 096NrPmJ002633 for ; Tue, 6 Oct 2020 19:53:31 -0400 Received: from OC11EXPO27.exchange.mit.edu (18.9.4.98) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 6 Oct 2020 19:52:48 -0400 Received: from oc11exhyb2.exchange.mit.edu (18.9.1.98) by OC11EXPO27.exchange.mit.edu (18.9.4.98) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Tue, 6 Oct 2020 19:53:13 -0400 Received: from NAM12-DM6-obe.outbound.protection.outlook.com (104.47.59.177) by oc11exhyb2.exchange.mit.edu (18.9.1.98) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 6 Oct 2020 19:53:13 -0400 Received: from DM6PR18CA0007.namprd18.prod.outlook.com (2603:10b6:5:15b::20) by DM5PR0102MB3318.prod.exchangelabs.com (2603:10b6:4:a4::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.39; Tue, 6 Oct 2020 23:53:12 +0000 Received: from DM3NAM03FT030.eop-NAM03.prod.protection.outlook.com (2603:10b6:5:15b:cafe::62) by DM6PR18CA0007.outlook.office365.com (2603:10b6:5:15b::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.38 via Frontend Transport; Tue, 6 Oct 2020 23:53:12 +0000 Received: from mail-ej1-f43.google.com (209.85.218.43) by DM3NAM03FT030.mail.protection.outlook.com (10.152.82.203) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.34 via Frontend Transport; Tue, 6 Oct 2020 23:53:12 +0000 Received: by mail-ej1-f43.google.com with SMTP id a3so332037ejy.11 for ; Tue, 06 Oct 2020 16:53:12 -0700 (PDT) Received: by 2002:ab4:a242:0:0:0:0:0 with HTTP; Tue, 6 Oct 2020 16:53:10 -0700 (PDT) From: Jason White To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Tue, 6 Oct 2020 16:53:10 -0700 Subject: [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: AdacPQNeIrYUz5egTRmNpFevtlHf0Q== 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: TempError X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: received-spf: Pass (protection.outlook.com: domain of gmail.com designates 209.85.218.43 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.218.43; helo=mail-ej1-f43.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=tVhYq61Ku5bJ4lgsBM6sg+4JtfHAfR9L5QVy24veK9c=; b=rkTfHfdtkNhhcbzk7m/qB1vP+XhCYO7XuYOiO5zPdciilZfTbDh+mhAWLDyo1H7PTW 1ifNKpgkT/THozvavaH/YSFlc7ffaSpOnEBWc6ZW7LADQqzyHf/djvf9gTOJ8k9ofb6K ZejipDFpdyeOei3y9bByd5m7yrGkv8eIBNOmkKhxeEKuGNxY1pWwh1QqUoCzvGbW9ahK I15ceTQd9YO63Ar9wr3o/e7hRX1RKLCJHZzYPPUA4mBoWmW+TGuh0Eia++C4Qc+RRmIP kcSRA8PGmUyOfbmEMdVqGLA1cKbBtpEH1tlJ8+h8zmbc5jZomqheQLRGmkr2i+XG44Qh 4krA== authentication-results: spf=pass (sender IP is 209.85.218.43) smtp.mailfrom=gmail.com; mit.edu; dkim=pass (signature was verified) header.d=gmail.com; mit.edu; dmarc=pass action=none header.from=gmail.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:a17:906:284f:: with SMTP id s15mr541504ejc.336.1602028390871; Tue, 06 Oct 2020 16:53:10 -0700 (PDT) x-topics: [EE] x-content-filtered-by: Mailman/MimeDel 2.1.6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 I'd be tempted to use the phone as an internet connected webcam/microphone. Steam audio/video from the phone and record it on the PC. On Tue, Oct 6, 2020 at 3:43 PM The Tyrers wrote: > > I would use a Sd card based security camera, Records prior to sound and during. > > > > On Oct 6, 2020, at 3:18 PM, 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 Jason White --=20 Jason White --=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 .