Unfortunately a lot of forum links broke when the new dev team changed the forum software.
I’ve edited the first post, so hopefully the “latest version” link will work now.
Thanks. But I still wish there was a “Both” option for both a low- and high-pass at the same time. I think this is only on the obsolete version.
Also, I have old Chains (Macros) using the old version and many of these have a Sinc filter using a bandwidth set at 256 I believe. What would be the Bandwidth equivalent on this version? Is there any sort of estimate? I.e. On the old version, window size X = Y bandwidth, Window size X2 = Y2 bandwidth, and so on? Just curious as I want to be consistent with filtering across the old and new versions.
It didn’t actually do them “at the same time”, but ran the audio data through one filter then the other, so there was no benefit in processing time. Given that you are using macros, you can get the same effect by placing the effect twice into the macro.
There isn’t an exact equivalent as the relationship between “Size” and “Bandwidth” depends on the sample rate.
The relationship is:
Size = 4 / (Bandwidth / sample-rate)
or equivalently:
Bandwidth = (4 x sample-rate) / Size
So for a sample rate of 44100 and “Size” of 256, the bandwidth would be approximately 690 Hz.
“Spectral Delete” is now included in Audacity.
Well for me, that’s a little bit hard because I liked the idea of making a band-stop filter without having to actually copy the high-passed audio to the clipboard, undo, low-pass the audio, make a new track and mix them. I doubt macros can actually do that, so that’s why I wish it were back.
You can do a Band-stop filter in a Macro like this:
SetTrackVisuals:Display="Spectrogram"
SelectFrequencies:High="1000" Low="500"
SpectralDelete:Use_Preset="<Current Settings>"
SetTrackVisuals:Display="Waveform"
Hmm. That honestly doesn’t sound like it would be all that accessible since you’re working with visual spectagrams.
As a fellow Audacity user, I’m trying to be helpful, but if you don’t want help then that’s your choice.
The macro that I posted is perfectly accessible - notice that the frequency bounds of the filter are set by the second line. The only reason for switching to Spectrogram view is because “Spectral” effects can only be used when the track spectrogram is displayed (a bit of a dumb decision with regard to macros, but that’s how it is).