I found in my stereo wav sound file an artifact to be deleted so I isolated the glitch in the spectral logarithmic view and invoked the notch filter after having identified the corresponding frequency with the spectral analysis tool. When invoking the notch filter, its window pops up and I put the frequency in the first field and left the Q to 1. Result : no artifact cleaning ! I did the same thing with a Q = 3 to no avail. Q = 5, same result.
Does anybody have any clue on what’s happening here ?
Describe the glitch. As a fuzzy rule, notch filter doesn’t do anything useful with ticks, pops, or other very short time duration disturbances. The tool needs time. Motor whine, computer fan, kettle whistle, etc.
My silly metaphor is telling somebody to identify all picket fences whose pickets (boards) are six inches apart.
Then you present them with a fence that has one picket.
Ummmmm. Not enough to go on.
There’s another possible error, too. Where is the notch? If it’s above about 10,000Hz, many people can’t hear that high.
My system uses the dot character as the decimal separator.
Note that changing the decimal separator character is risky because it MUST be consistent, and for most operating systems it MUST be set the same in multiple places. I’ve never had to worry about this because my computer has always use the dot character as the decimal separator.
I have done NO special mod in audacity and it puts commas instead of periods as decimal symbol. Would gladly configure it to use periods but I don’t know how… Even if I type a period, it converts it as a comma !!!
There are no special settings in Audacity for the decimal separator. It takes the decimal separator settings directly from the operating system (in your case “Windows”, in my case “Linux”). If there are conflicting settings for the decimal separator in the operating system, then it WILL cause problems.
I reverted the Windows 10 regional settings to english (US), rebooted the pc to no avail : same notch filter with commas decimal symbol.
The next step now is to fill a bug report (feature request) to the notch filter programmer (or audacity board) in order for him (them) to allow commas as decimal symbols. Where do I fill this report/request ? I NEED this notch filter ASAP…
It isn’t an Audacity bug. It seems that there is still a conflict somewhere in your Windows settings.
I can probably write a version of the Notch filter that isn’t affected by the Windows settings, but you are still likely to have problems with other effects. You really need to fix the problem on your computer.
Installation of your custom notch filter successful but… same outcome : there were no decimal to mess with, great but… it returned the same window (that I figure now it is not an error window but an “info” window) :
with NO notch cleanup performed.
I wonder if that window is normal and usually shown regardless of the success of the operation, or shown only if a problem occurred ? You tell me !