Audacity Forum

"remove Tone" is a nyquist filter built by David R. Sky. You select audio, and it will give you the frequency of the tone, and you have the option to remove it. It can also work as a straight notch filter.

stevethefiddle wrote:A bug has recently been identified in Audacity 1.3.10 alpha where Audacity crashes when running some Nyquist plug-ins. You may be describing the same bug. If so, then a bug fix has just been submitted, so the problem may already be fixed. When the next beta version of Audacity is released it may be a good idea for you to test it and see if you can still reproduce the problem.

Given "Remove Tone" is a Nyquist plug-in (it has a file name that ends in .ny) then it's possible there may be problems depending on the locale you are running Windows in. Please try our very latest 1.3.10 Alpha by clicking this link:
http://www.gaclrecords.org.uk/audacity- ... -alpha.zip

This has been rebuilt since you last tried 1.3.10.

Also many or all effects process much slower in 1.3.9 and 1.3.10 and take much longer to display the resultant waveform after processing. If you are processing a stereo track, some plug-ins process each channel separately so you will also get a hang at half way point (where the effect finishes processing the first channel). Please try 1.3.10 (link as above) and give us

* exact steps to reproduce what you are seeing from launch of Audacity
* the exact name of the effect you are running
* also please tell us if you are running Windows in English or some other language.



Gale

"Also many or all effects process much slower in 1.3.9 and 1.3.10 and take much longer to display the resultant waveform after processing."

Well, so far it's more like they monopolize my system, but that may be a separate problem. Is this something they are working out? This was a stereo file.

Anyway, to duplicate the problem.

1.) Open Audaciy
2.) Generate 45minutes of white noise
3.) Duplicate the track and turn both into a stereo file
4.) Select All, then Click "Effects" then "Notch Filter"
5.) Selection on "0" for 60Hz, then 60Hz, q set to 4.75
Prepare to crash. Though this created file seemed to go longer without crashing, it crashed for me just the same.

Oh, I am definitely running Windows in English. I have tried this in 3.10 with the same result.

I just tested this in Vista with the same results. Dual core AMD Turion x2 2GB RAM

Alright, I tested the latest build (As of 9/13/09) and I still get hung up. It does seem to behave a bit differently, for instance, instead of locking up at the halfway point, it speeds up and locks up when the status bar is at the end, at 3:02 with 2 seconds left.

As a note, I tried applying the filter to a mono channel, and it worked.

orgelquaeler wrote:"remove Tone" is a nyquist filter built by David R. Sky.

Thanks for the info about the plug-in.
I've sent you a PM about it (it's a bit off-topic, so I didn't want to confuse the issue by posting here).

Just an(other) update. Notching the channels one at a time works fine, so I will stick to doing that for now.

I've done a couple of tests with this.
Applying a notch filter to a 1 hour stereo track.

My computer has 3GB of RAM.
When attempting to process the hour long (32 bit) track, memory usage soared to 2.5GB, at which point the computer started manic disk activity (swapping RAM to disk). The computer ground to a standstill an I either had to wait, probably a very long time, for it to clear, or forcibly quit Audacity. I chose the latter.

Processing the track in 20 minute sections resolved the issue as I now had sufficient RAM to complete the operation.

I think that it is quite likely that you were just running out of available RAM.

stevethefiddle wrote:
Processing the track in 20 minute sections resolved the issue as I now had sufficient RAM to complete the operation.

I think that it is quite likely that you were just running out of available RAM.

That is possible. Is this a problem with 3.9 that they are working on to fix? I have never had trouble with 3.4 applying a simple notch filter to long files. I can even browse the web and move files in the background with no problem. In fact, that is one of the greatest things I have liked about Audacity; that it has worked much more efficiently than other programs.

My point is, that I hope this is something the developers are looking to overcome. My desktop has 4GB RAM. Seems like that should be plenty.

Had the same thing happen to a long (90min) mono WAV file, using the Hi-Pass filter. These functions of Audacity are key to the type of work that I am doing, which is mastering and restoring old lectures.

I had hoped to be able to use 3.9 because of the key shortcut for "Play at speed", which seems to not exist in 3.7 (which I have been using successfully so far after upgrading from 3.4). Unfortunately, it is also not time effective for me to switch versions every time I want to run a filter.

In the release for 3.8, it mentions that Nyquist was updated to better use memory. I can't imagine this has become the case, if, as Gale says, Nyquist runs slower and as I have experienced crashes in long samples. Maybe I have misunderstood. Is this the update that is causing me grief, or is this unique to 3.9 and 3.10?

I have to take a minute to thank everybody for their responses. I know it must seem like I am complaining alot here. I owe alot to the Audacity team, and I think the product is really solid. Keep up the great work!