>> Why would post-record editing be "horrendous"? This has to be done on-the-fly before it is recorded. After the AGC is applied, it will be played, live, to the community. It is played during the week to a much smaller audience, almost as background noise. Post recording editing would be a waste of time and worthless.
>> Does it record the whole 48 hours into 1 file? Two files, 24 hours each, one for Saturday, the other Sunday -----Original Message----- From: Python-list <python-list-bounces+gronicus=sga.ni...@python.org> On Behalf Of MRAB Sent: Saturday, May 28, 2022 8:57 PM To: python-list@python.org Subject: Re: Automatic Gain Control in Python? On 2022-05-29 01:17, Steve GS wrote: > "My first thought is you are solving the wrong problem. What seems a > better option would be to get your code to actually connect up to the > podcast and just download the audio directly, rather than trying to > get the smart speaker to play the audio and record it with a microphone." > > The smart-speaker is bringing in the podcast by hourly automated > commands and sending by audio cable to a computer which is recording > it with Audacity. This is an automated system that runs for 48 hours every weekend. > Its output is played live throughout the facility and is also recorded > for replay through the week. > > No download to use. > > AGC is to happen when the Smart Speaker is playing it, real time. > Any post-record editing would be a horrendous task to say the least. > [snip] Why would post-record editing be "horrendous"? Does it record the whole 48 hours into 1 file? If it's recording each podcast separately, it could process each one after recording it, even while the next one is being recorded, and I really doubt that processing each one while take long. -- https://mail.python.org/mailman/listinfo/python-list -- https://mail.python.org/mailman/listinfo/python-list