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; Thu, 8 Oct 2020 08:46:34 -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 098C6nZi018910; Thu, 8 Oct 2020 08:07:19 -0400 Received: from outgoing-exchange-1.mit.edu (OUTGOING-EXCHANGE-1.MIT.EDU [18.9.28.15]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 098C6lIY018907 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 8 Oct 2020 08:06:48 -0400 Received: from oc11exedge2.exchange.mit.edu (OC11EXEDGE2.EXCHANGE.MIT.EDU [18.9.3.18]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id 098C6NQE008524 for ; Thu, 8 Oct 2020 08:06:47 -0400 Received: from oc11expo33.exchange.mit.edu (18.9.4.114) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Thu, 8 Oct 2020 08:06:11 -0400 Received: from oc11exhyb5.exchange.mit.edu (18.9.1.110) by oc11expo33.exchange.mit.edu (18.9.4.114) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Thu, 8 Oct 2020 08:06:37 -0400 Received: from NAM12-BN8-obe.outbound.protection.outlook.com (104.47.55.172) by oc11exhyb5.exchange.mit.edu (18.9.1.110) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Thu, 8 Oct 2020 08:06:37 -0400 Received: from MWHPR18CA0062.namprd18.prod.outlook.com (2603:10b6:300:39::24) by DM6PR01MB5179.prod.exchangelabs.com (2603:10b6:5:55::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3455.23; Thu, 8 Oct 2020 12:06:36 +0000 Received: from CO1NAM03FT055.eop-NAM03.prod.protection.outlook.com (2603:10b6:300:39:cafe::9f) by MWHPR18CA0062.outlook.office365.com (2603:10b6:300:39::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3391.14 via Frontend Transport; Thu, 8 Oct 2020 12:06:36 +0000 Received: from mail-pl1-f170.google.com (209.85.214.170) by CO1NAM03FT055.mail.protection.outlook.com (10.152.81.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3455.23 via Frontend Transport; Thu, 8 Oct 2020 12:06:36 +0000 Received: by mail-pl1-f170.google.com with SMTP id c6so2657293plr.9 for ; Thu, 08 Oct 2020 05:06:36 -0700 (PDT) From: Justin Richards To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Thu, 8 Oct 2020 05:06:21 -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: AdadijOtVsmlk8w9RpKqZbJp+fJjIw== 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 gmail.com designates 209.85.214.170 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.214.170; helo=mail-pl1-f170.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=y82Bl2mulbBHscQJdG3aDIl6pD1EwKsqv/kqGtzk578=; b=q7j7x/iz2eVAe7aIaLXi7hFFE+4uKZVKuNtNeZpZRwm93CQReWjiWPh+bbxYjj/JwL iSMbPjRqpV7YBbo82f7BbVQHvSsHRGpqjX1lFx3hFII/oB5UW+0GJN+71ji6O2a8UqED RKSB6pblRX0MC4YLMt/GrMImkTe2edC50DpxeYaDo1/yv0oUyMQ/cGkh+Qa2ffUA1uZ/ Dm2ujS7hpaPtcb5ZUC3RzeLJri+C0zmadXt9EyxDsrApm5wniL9xHfQw9oe0T9JFzEv5 5sru3+u8HuSgbvL5YKqIh9Io1ukOtSxvkl0MBWhX486GgWtQnFSYpSamW/RulixQ8280 QIMQ== authentication-results: spf=pass (sender IP is 209.85.214.170) 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:902:8693:b029:d3:9c6b:ca5f with SMTP id g19-20020a1709028693b02900d39c6bca5fmr7191301plo.67.1602158794675; Thu, 08 Oct 2020 05:06:34 -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 How far apart are the ignition events, VLC has worked well to quickly and cheaply get audio from one place to another via a network where it can be saved to file and/or monitored as required. I used VLC to stream UHF radio whenever it was keyed so it could be monitored locally and 100kms away at a remote site. VLC is handy as it works on many platforms and is somewhat uniform to configure. It is currently being used to reliably stream 4 radio stations (received via satellite) to VLC running on RPi's, Windows and Linux based PC's. On Wed, Oct 7, 2020 at 3:19 AM 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 > --=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 .