en.osm.town is one of the many independent Mastodon servers you can use to participate in the fediverse.
An independent, community of OpenStreetMap people on the Fediverse/Mastodon. Funding graciously provided by the OpenStreetMap Foundation.

Server stats:

251
active users

#commandline

4 posts4 participants1 post today

Dear sound/audio folks and engineers,

I have a directory with 3.5GiB of audio files (chiefly opus & m4a) which are spoken word recordings.

Some of them are quite low, and some of them are quite dynamic such that it's a whisper at times and nearly a shout at other times.

I've processed a lot of them with #audacity's compressor filter or #ffmpeg (ffmpeg -i audio.m4a -filter:a "speechnorm=e=50:r=0.0001:l=1" audio-normalized.m4a), but there are some unprocessed files in the collection, which are a pain to individually find and fix.

Is there a way from the #CommandLine to detect the loudness and/or dynamic range of audio files so that I can automatically flag them for processing with ffmpeg?

Thanks!!

I've come to the conclusion that the command line is peak UI. It's fast, and it doesn't freeze as often. I had an issue where I tried to delete a task in the Windows Task Scheduler and every time I would try, the UI froze on me. I piped the below into Powershell and it was deleted! No lag, no nothing!

Unregister-ScheduledTask -TaskName "RClone Backup Writings"