Notifications
Clear all

Unify Crashing Abelton on song change


NatureGuy
(@natureguy)
Eminent Member
Joined: 2 years ago
Posts: 22
Topic starter  

Hello,

Ever since the latest update 1.8 my Unify has been causing my Abelton Live version 10.1.42 Standard to Crash. It happens when I switch songs from one to another. I wrote to you technical support already and sent the Abelton Crash report. I wrote also to Abelton and sent them my crash file they confirmed the problem originates with Unify. They recommended I uninstall Unify then reinstall it. Which I did. But before I reinstalled it I opened Abelton Live with no Unify on the PC and when I switched songs as before Abelton did not crash. This confirmed that Unify is causing the problem.

I am using: Windows 10 64bit. Processor Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz 3.60 GHz
Installed RAM 64.0 GB
System type 64-bit operating system, x64-based processor
If you need any other info let me know I will help any way I can.

Thanks, Dave

P.S. I also just sent the crash file to UnifySupport@PlugInGuru.com from Abelton Live 10 just after I posted this.

This topic was modified 4 months ago 2 times by NatureGuy

Thanks!
Dave (Nature Guy)


Quote
getdunne
(@getdunne)
Member Admin
Joined: 3 years ago
Posts: 3502
 

@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?


ReplyQuote
NatureGuy
(@natureguy)
Eminent Member
Joined: 2 years ago
Posts: 22
Topic starter  

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

Thanks!
Dave (Nature Guy)


ReplyQuote
NatureGuy
(@natureguy)
Eminent Member
Joined: 2 years ago
Posts: 22
Topic starter  

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.

Thanks!
Dave (Nature Guy)


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 3 years ago
Posts: 3502
 

@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.


ReplyQuote
NatureGuy
(@natureguy)
Eminent Member
Joined: 2 years ago
Posts: 22
Topic starter  

@getdunne Your welcome take your time no rush.  

Thanks!
Dave (Nature Guy)


getdunne liked
ReplyQuote
SSquared
(@ssquared)
Member
Joined: 3 years ago
Posts: 209
 

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.

Ableton Live 10, Omnisphere, Native Instruments (Pianos), Spire, Hammer + Waves, Heavyocity (Ascend and Mosaic Keys), Diva, SynthMaster, Alchemy 1.55, Addictive Keys, Unify


ReplyQuote
NatureGuy
(@natureguy)
Eminent Member
Joined: 2 years ago
Posts: 22
Topic starter  

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 😉 

This post was modified 4 months ago by NatureGuy

Thanks!
Dave (Nature Guy)


ReplyQuote
NatureGuy
(@natureguy)
Eminent Member
Joined: 2 years ago
Posts: 22
Topic starter  

@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. 

Thanks!
Dave (Nature Guy)


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 3 years ago
Posts: 3502
 

@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.


ReplyQuote
NatureGuy
(@natureguy)
Eminent Member
Joined: 2 years ago
Posts: 22
Topic starter  

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

This post was modified 1 month ago by NatureGuy

Thanks!
Dave (Nature Guy)


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 3 years ago
Posts: 3502
 

@natureguy

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


ReplyQuote
NatureGuy
(@natureguy)
Eminent Member
Joined: 2 years ago
Posts: 22
Topic starter  

@getdunne thanks 😊 

Thanks!
Dave (Nature Guy)


ReplyQuote
zzz00m
(@zzz00m)
Active Member
Joined: 7 months ago
Posts: 18
 

I just saw this thread and so decided to check this out with the latest Ableton Live 11.1.5 and Unify 1.8.0 VST3.

Adding Unify VST3, deleting it, then adding it again caused Live to crash (attached).

Unify VST(2) still works fine.

Found the WER info in Windows 11 (attached).

 
 
This post was modified 3 weeks ago 4 times by zzz00m

ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 3 years ago
Posts: 3502
 

@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.


ReplyQuote
zzz00m
(@zzz00m)
Active Member
Joined: 7 months ago
Posts: 18
 

@getdunne Yes, I saw that it was reported, but the discussion was regarding Live 10. I was just adding updated info for Live 11. Clearly still no solution on the Ableton end with the latest version. So VST2 it is for now!!!


ReplyQuote
NatureGuy
(@natureguy)
Eminent Member
Joined: 2 years ago
Posts: 22
Topic starter  

@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.

Thanks!
Dave (Nature Guy)


ReplyQuote
zzz00m
(@zzz00m)
Active Member
Joined: 7 months ago
Posts: 18
 

@natureguy I am also getting Reaper to crash consistently when adding a new instance of Unify VST3 after deleting the previous one. But the crash type APPCRASH explicitly calls out the VST3 with a c0000005 exception. Was getting a BEX64 type of crash in Ableton.

However with Reaper, if you close the host and reopen it after deleting Unify, no crash when adding a new instance of Unify. It only crashes when this action occurs in the same host session.


ReplyQuote
Share: