Nectar 4 crashing DAW

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

Just out of curiousity, was wondering if anyone else was experiencing this same issue (Izotope appears to be clueless about it, even though I have a ticket open about it.

When I insert an instance of nectar 4 on a MONO vocal channel, it works fine… UNTIL you use the assistant feature. Then it crashes my Daw. My current one is Studio One 6, however it also crashes Logic Pro X.

However, when used on a stereo bus/channel, the assistant feature works as intended.

Can anyone else confirm this situation happening for them? Maybe I can light a fire under izotope to finally get this issue fixed.

Post

Hey, I have the same error with Nectar 14 in Cubase 13 on win 11. Have you been able to fix the issue? The DAW crashes when using the assistant. Sometimes I even get a BOSD.

Post

Izotope are the only plugins that consistently give my DAW (Reaper) issues

Post

SiriusVI wrote: Thu Mar 07, 2024 8:54 pm Hey, I have the same error with Nectar 14 in Cubase 13 on win 11. Have you been able to fix the issue? The DAW crashes when using the assistant. Sometimes I even get a BOSD.
So the steps to reproduce are just to make a channel mono? I can try later today if you want. (macOS/Bitwig).

Post

crookedmacs wrote: Thu Mar 07, 2024 10:47 pm Izotope are the only plugins that consistently give my DAW (Reaper) issues
I don't have any issue with nectar, neutron and ozone, while using them a lot.
But stutteredit crash every hour ... Fortunately I got it for cheap, I would be so pissed....

Depending of ozone/neutron next versions and how the brand evolve, I may move fully to Fabfilter.

Post

SiriusVI wrote: Thu Mar 07, 2024 8:54 pm Hey, I have the same error with Nectar 14 in Cubase 13 on win 11. Have you been able to fix the issue? The DAW crashes when using the assistant. Sometimes I even get a BOSD.
Yes. After I opened a ticket with izotope, they responded back that it would be fixed in a future update. And sure enough, everything was working in the following update.

Post Reply

Return to “Effects”