Hi Audacity crashes when working with Spitfish De-esser
Win 7 64
Audacity 2.1.2
installed today via exe installer
Thanks
Rick
Thanks for the report, Rick.
Spitfish does not crash for me on Windows 10.
Do you have any exact steps we could follow to reproduce the crash?
Gale
Yeah Gale, it happens when I click the play/stop preview > button. Not always, just after a few times, this is with a ~10 second selection. I am usually in listen mode also.
Thanks for the fast response!
While we are there, I don’t see any presets named, they all say “none” but each produce a different setting.
I could get it to crash once if I pumped the Play/Stop button in the effect as fast as I could. I wouldn’t call that normal usage.
Have you changed the effect’s options (Manage button > Options…)? Does reducing the buffer size make it more stable?
Did you use Spitfish before in a previous version of Audacity without crashes?
There are a few other free De-essers such as Lisp.
That’s how the effect is as far as I know - it has been left undeveloped for the last 10 years or so.
If you find a factory preset you like, select it, then save it as a user preset (Save Preset…).
Gale
I halved and quartered the buffer size and it helped a little at 4096 but still crashes. Strange that no others have this problem. You are testing in Win 10 huh? I guess it’s getting close to upgrade time.
Thanks
Hello,
I’m having the same problem as Rick. I have Windows 10.
I have Audacity 2.1.3 and just installed spitfish.
When trying to apply changes, or hitting the “play” button my Audacity program halted/crashed many times and I had to recover the project. These were the messages I received:
0:12:06: Audacity 2.1.3
20:12:06: Trying to load FFmpeg libraries...
20:12:06: Trying to load FFmpeg libraries from system paths. File name is 'avformat-55.dll'.
20:12:06: Looking up PATH environment variable...
20:12:06: PATH = 'C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Users\rjjin\AppData\Local\Microsoft\WindowsApps;'
20:12:06: Checking that '' is in PATH...
20:12:06: FFmpeg directory is in PATH.
20:12:06: Checking for monolithic avformat from 'avformat-55.dll'.
20:12:06: Error: Failed to load shared library 'avformat-55.dll' (error 126: the specified module could not be found.)
20:12:06: Loading avutil from ''.
20:12:06: Error: Failed to load shared library '.dll' (error 126: the specified module could not be found.)
20:12:06: Loading avcodec from ''.
20:12:06: Error: Failed to load shared library '.dll' (error 126: the specified module could not be found.)
20:12:06: Loading avformat from 'avformat-55.dll'.
20:12:06: Error: Failed to load shared library 'avformat-55.dll' (error 126: the specified module could not be found.)
20:12:06: Error: Failed to load FFmpeg libraries.
20:12:06: Error: Failed to find compatible FFmpeg libraries.
Still researching what to do next. I would greatly appreciate any feedback anyone has for this matter.
Janet
Please try upgrading to the current version of Audacity (2.2.2). You can get it via the Audacity website: https://www.audacityteam.org/download/windows/
Does the crash occur only when Spitfish is open?
Yes, the crash only happens when Spitfish is open. This has never happened before. The first time was when using Spitfish.
Does your Spitfish plug-in have a version number?
Perhaps there’s an earlier version of Spitfish that works, and a later version that doesn’t (?)
Spitfish works for me on 2.2.2 and the latest 2.3.0 alpha on W10 - no crash
And it works for me too on 2.1.3 - the version that Janet was using.
My Spitfish version is 1.1
Steve,
I upgraded to 2.2.2 and tried using Spitfish again but the Audacity screen left me again when I hit the play button. I had turned off the “listen” button in order to preview my adjustments of sensor and depth knobs. As to your earlier question, I’m not sure how to determine what version of Spitfish I have. But I used this website link to download it: www.digitalfishphones.com/main.php?item=2&subItem=5
Do you have any other ideas? By the way, I didn’t receive an error report (from Help Show screen) and was able to get back to my file again.
My Spitfish version was also 1.1
Steve,
I’m wondering if I should have a particular driver installed to go along with Spitfish? If so, what do you recommend? Also, which de-ssing program is best between Spitfish and Lisp? I really would rather try to make Spitfish work if possible. If I cannot do this, then I would resort to Lisp.
Does anyone have any feedback on these questions? I’m grateful for anyone’s help.
I’m wondering if I should have a particular driver installed to go along with Spitfish? If so, what do you recommend? Also, which de-ssing program is best between Spitfish and Lisp? I really would rather try to make Spitfish work if possible. If I cannot do this, then I would resort to Lisp. Or do you have another preference?
The drivers on my Windows 10 HP Envy laptop are the bog-standard out-f-the-box items from HP/Microsoft - and as I said earlirer Spitfish 1.1 works for me on various released Audacity versions and the recent alphas for the upcoming 2.3.0
Sorry I can offer no further insight.
And sorry, I can’t comment on comparable functionality as I only have Spitfish for QA testing purposes - not for production work.
Peter
Thank you. Do you have any ideas about what I should try next? I saw somewhere about doing this:
The overwhelming majority of VST effect plug-ins should display and process correctly. If an incompatible VST plug-in does cause a problem, click the Manage button in the effect’s dialog then choose “Options…”. In the dialog that appears, try reducing Buffer Size, disabling Latency Compensation or disabling graphical display. See VST Effect Options in the Manual for more information on these choices.
To report a plug-in that is problematic in current Audacity, please add it below, or write to our feedback address.