Skip to main content
straightlife
straightlife
Inspiring
January 21, 2021
Question

Thought Audition was the ANSWER but Accusonus ERA plugins crash it

  • January 21, 2021
  • 1 reply
  • 1331 views

I've been struggling trying to do multitrack editing in Audacity. I LOVE the Accusonus plugins. BUT after downloading Audition and saying, wow! This is more like it. KEYFRAMES!!!! It crashed repeatedly when I was using the pro noise remover plugin from Accusonus. Any workaround or, sigh, back to Audacity?

This topic has been closed for replies.

1 reply

SteveG_AudioMasters_
Community Expert
SteveG_AudioMasters_Community Expert
Community Expert
January 21, 2021

I have no idea why it would crash with that plugin, but there are a couple of points to make; firstly, Audition has always been slightly notorious for not suffering some plugins. Even Waves fell foul of this at one point and they had to do a bit of a rewrite to keep them strictly within the VST guidlines - the shortcuts that work with a lot of other software simply don't with Audition. Not saying that this is definitely what's happened - just that it's not unknown. It's always difficult dealing with this, because invariably Adobe blames the plugin, and the plugin manufacturer blames Adobe. I don't know how you resolve this...

 

The second thing is that Audition's NR actually works pretty well. Have you thought or tried using that instead? The best form of it is the process-based one, applied in two or three passes, a fresh sample at different FFT sizes each time, and only a small amount taken off. 

    TenTin
    TenTin
    Known Participant
    September 26, 2022

    I have had this problem since Audition 2022. Accusonus has been working good before the update! If I open a sound in Au and open one of the ERA plugins (VS3), it crashes (Au)!!! I am frustrated. What is wrong with Audition?

    SteveG_AudioMasters_
    Community Expert
    SteveG_AudioMasters_Community Expert
    Community Expert
    September 26, 2022

    As I pointed out before, probably nothing is wrong with Audition - it just expects plugins to be coded correctly, and not take shortcuts in the coding. These programming shortcuts are rather common, and will work with a lot of non-fussy apps, but not with Audition. I should stress that I haven't tried this particular plugin so I have no specific information about it - this is just the generic situation, which has been frequently found to be the situation in the past. Also please note that it is not impossible for Audition to be at fault - it's just that it's rather more likely to be the plugin. Probably the only way to resolve this is to report it as an issue on the Audition Beta forum, and see if you get a response there - the devs look at that one.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices