Unify Crashing Abelton on song change

@natureguy

Thank you for bringing this to the forum. I'm sorry to hear you're having this trouble. John or Taylor will probably forward your crash report to me very soon, although to be honest, Windows crash reports are rarely useful.

I just recently got a NFR license for Ableton Live 11 Suite, so I should be able to reproduce the issue, unless it's specific to Live 10.

You say that this has started happening only since the v1.8 Unify update? That's unexpected, but of course such bugs are always a surprise.

From what you have written, it sounds like all I need to do to reproduce this is to create two separate Live projects using Unify, and switch from one to the other. Is that correct?

One more thing: Are you using the VST3 version of Unify, or the VST? Have you tried both, or just one?

Hi Shane, yes having two separate songs. Then close one after saving it. Open the other, it crashes before the new song opens. Yes I am using the vst3 version of unify, since that update that's all I have been using. But I will conduct an experiment this morning create two new songs with the standard vst and see if that crashes as well.

Dave

Update!  I did the test using only the VST version of Unify and Abelton Live did not crash... So the problem lies with the VST3 version.

@natureguy

Thank you for the update. At least using the VST version of Unify may provide a work-around for you, and in the meantime, I know to concentrate my debugging efforts on the VST3.

@getdunne Your welcome take your time no rush.  

I can definitely reproduce this with Ableton Live 10.  I've done a bit of testing and trying different things.  You don't even need to open a new project.

• Open Ableton Live.
• Drop VST3 Unify on a track.
• Delete/Remove Unify.
• Then add the VST3 Unify again, and it crashes.

This only happens when you delete the last instance of Unify.  If you have multiple instances of Unify, you can delete and add Unify VST3 as much as you'd like.  But if you delete ALL tracks/instances of Unify, then it crashes as soon as you add a new instance of Unify VST3.

That makes sense when opening a new song in essence it is closing all unify vsts. That's why it crashes.  Something is going wrong when they all close.

Or something is maybe refusing to close causing the conflict 😉 

@getdunne Hi Shane, I am the one that sent you a message on messenger.  This it the thread and the problem that I posted some months ago. Wondered if you addressed the vst3 issue of it causing Unify to crash Abelton. 

@natureguy

Thanks for clarifying. I strongly suggest using the VST2 version of Unify in Ableton Live; there is absolutely no advantage to VST3 that I'm aware of.

The next version of Unify (v1.9, still in beta testing) is built on the newest version of the JUCE framework, so VST3 support may be better. It's not something I have a whole lot of control over, unfortunately, but as I said, there's no functional difference and the VST2 works well.

Is VST actually VST2? Because what comes up in abelton is just vst and vst3. 

@natureguy

Yes "VST" = "VST2" = "VST 2.4" = "VST 2.x" etc.

@getdunne thanks 😊 

@zzz00m

The issues with the Unify VST3 plug-in in Ableton Live have been reported before. Until a solution can be found, we recommend to use the VST2 version of the Unify plug-in with Live. To the best of my knowledge, there is no disadvantage to doing so.

@zzz00m Yes I now have Abelton Live 11 and it is doing the same thing as 10. The problem I have is I have so many songs now that I have to fix because I used VST3. It will take alot of work.