It is indeed a little confusing with all the selecting steps.
Let me see if I got it right:
- The purpose of the first selection is to preview the section you’re working with.
- You then play this section and re-set the left margin where (according to your “feel”) the sentence should start.
- difference between desired and momentary start (+ the beginning of the sentence) is stored.
- This selection could be 0.5 s long. However, the louder part at the end is preserved because it lies above the first threshold. Thus, the actual difference could be 0.3 s.
- You now expand the selection again to the left into the region between sentence end and breath taking.
- The plug-in excludes then also the quieter sound from the stored selection (maybe 0.1 s) and we end up with 0.2 s that have to be deleted.
- after the detection of the zero crossing, the sound without the removed silence of about 0.2 s is returned.
It may be advantageous for people that do not use a mouse to save the first selection (edit menu), and to restore it before the actual silence removing.
I guess I would prefer an one-click effect that removes in each call the quietest rms-sections.
Something like this:
- You select the pause including ending and beginning of the concerned sentences.
- You call the plug-in.
- It takes the RMS measurement (let’s say at 20 Hz)
- The curve is now multiplied by a raised half-period sine curve (bowl shape).
- This should ensure that start and ending of the selection aren’t affected.
- You make a list with the time indexes and the weighted RMS values.
- after Sorting out the most silent ones, you can search for the zero crossings and remove these parts.
- The amount of RMS values that have to be removed is of course hard-coded.
20 Hz would mean 50 ms per value.
You could now tell the program to remove 10 of these.
When you additionally multiply this with a random factor of 1, 2 or 3, it is going to be easier to remove longer silences.
By pressing play, you can control the result and undo the last step (and try with a hopefully smaller random value) if necessary.
You could of course also start with relatively high values for longer selections.
Besides, I’ve posted a snippet that returns a list of zero crossings without the use of snd-fetch.
https://forum.audacityteam.org/t/zero-crossing-detection/26237/1