Notifications
Clear all

Unify 1.1.3 - Windows 10 repeatable crash  

  RSS

J Hall
(@zinct)
Member
Joined: 6 months ago
Posts: 99
June 10, 2020 7:25 pm  

I have been having problems with Unify 1.1.3 crashing and exiting (both standalone and as a VST2 in Cakewalk).

I have just loaded Unify 1.1.3 standalone and managed to get it to crash/exit consistently five times in a row. I did the following..

1. Load Unify
2. Click on browser
3. Load patch Arrival IV - Welcome to Unify 1.1
4. Load patch BPM Clap - Airwave Ambi

Thinks about it for a few seconds then exits every time.

This topic was modified 6 months ago by J Hall

Quote
getdunne
(@getdunne)
Member Admin
Joined: 1 year ago
Posts: 1606
June 10, 2020 9:23 pm  

@zinct

Thanks for joining the Forum, and for this feedback.

Are you running on Windows or Mac? I have followed your steps on both, but it doesn't fail for me. The difference might be related to CPU, RAM or disk speeds. What are the basic specs of your machine?

One last thing: if you're on Windows, do you by any chance have the Windows background set to cycle automatically through several images? This has caused issues for some users. If so, please disable this and try again, and let me know if it makes a difference.

 


ReplyQuote
Leszek 1953
(@leszek-1953)
Member
Joined: 1 year ago
Posts: 172
June 10, 2020 9:49 pm  

(@getdunne)

Today I turned on Unify and for good morning he wanted to enter the license key, ok I did it and version 1.1.2 started, although I had 1.1.3 installed. Yesterday Windows did a big update, it may have changed from 1.1.3 to 1.1.2. And this license key is your job. ?

 

Regards

Les.

 


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 1 year ago
Posts: 1606
June 10, 2020 9:56 pm  

@leszek-1953

First, please create a new forum topic when you want to discuss something different. This topic is about a specific crash bug.

Major Windows updates occasionally invalidate our license keys. When this happens, please send email to UnifySupport@PlugInGuru.com, explain what happened, and John will reset your license activation count. For this time, I'll pass this message to John myself.

If you installed Unify v1.1.3, but you ran v1.1.2, either something went wrong with your installation, or (much more likely) you have an old copy of the v1.1.2 stand-alone app that you should replace with the latest one.


ReplyQuote
Leszek 1953
(@leszek-1953)
Member
Joined: 1 year ago
Posts: 172
June 10, 2020 10:13 pm  

(@getdunne)

 

To be honest I don't know how to post new topics in the forum, sorry. As for version 1.1.2, it is current, I installed it as soon as I got it from John for testers. I uploaded 1.1.3 and everything is good. Of course, I will provide info about the key.

 

Les.

 


ReplyQuote
Leszek 1953
(@leszek-1953)
Member
Joined: 1 year ago
Posts: 172
June 10, 2020 10:26 pm  

(@getdunne)

 

I don't know where your indignation is from, but two levels above "Unify 1.1.3 /Crash / Windows 10 "

Next time I will try to post info in a new forum window.

 

Les.

 


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 1 year ago
Posts: 1606
June 10, 2020 10:27 pm  

@leszek-1953

I already asked John to update your license activation count, so you don't need to email him this time.

To make a new forum topic:

  1. Click on "Forums" at the very top left
  2. Select the most appropriate forum, and click on its name.
  3. Click on the blue "Add Topic" button at the top right.

ReplyQuote
J Hall
(@zinct)
Member
Joined: 6 months ago
Posts: 99
June 10, 2020 11:16 pm  
Posted by: @getdunne

@zinct

Thanks for joining the Forum, and for this feedback.

Are you running on Windows or Mac? I have followed your steps on both, but it doesn't fail for me. The difference might be related to CPU, RAM or disk speeds. What are the basic specs of your machine?

One last thing: if you're on Windows, do you by any chance have the Windows background set to cycle automatically through several images? This has caused issues for some users. If so, please disable this and try again, and let me know if it makes a difference.

 

My machine specs are

OS: Windows 10 Home 1909
CPU: Intel Core i7 3770 3.40 GHz
Motherboard: Gigabyte Z77 HD3 mobo
RAM: 16 GB RAM DDR3 
Display card: MSI GTX 1060 Gaming X 6Gb.

I have Unify's factory content installed on a fast NVME drive and the program on my boot drive which is also an SSD.

My main DAW is Cakewalk by Bandlab but I also own Cubase 10 Pro, Studio One 4.6 Pro, Reaper 6, Ableton Live 10 Standard and Reason 10 Intro.

My audio interface is an IK Multimedia AXE I/O.

I use a plain colour for my desktop background so there's no background switching going on.

Before the 1.1.2 then 1.1.3 update the old version 1.0.12 was running fine. I updated the factory content by dragging/dropping the new guru file and then re-scanning the database. 

I would say that the crashes are more frequent when switching between patches where one of them has a lot of content e.g. Arrival IV.

Does Unify produce any logs to show what it is doing for crash purposes? 

 

This post was modified 6 months ago 2 times by J Hall

ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 1 year ago
Posts: 1606
June 10, 2020 11:25 pm  

@zinct

Thanks for sharing your system specs. Changes in Unify v1.1.x seem to be at the root of these crashes. We fixed what we thought was all the crashing before releasing, but it seems something remains. I agree the number of layers seems to be a factor. We're able to make super-complex patches now, which we never even attempted in earlier versions.

I will test on some other PCs here.


ReplyQuote
J Hall
(@zinct)
Member
Joined: 6 months ago
Posts: 99
June 10, 2020 11:59 pm  
Posted by: @getdunne

@zinct

Thanks for sharing your system specs. Changes in Unify v1.1.x seem to be at the root of these crashes. We fixed what we thought was all the crashing before releasing, but it seems something remains. I agree the number of layers seems to be a factor. We're able to make super-complex patches now, which we never even attempted in earlier versions.

I will test on some other PCs here.

Thanks Shane. I don't know if this would help but here is a video of the crash. This time I'm starting with Arrival IV (loads fine) and then selecting the Bass patch just below it - boom!

https://youtu.be/cA0WC1srWe4  


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 1 year ago
Posts: 1606
June 11, 2020 1:06 am  

@zinct Thank you for the video. This is so tantalizing. There's no doubt it's crashing for you, but I can't seem to get it to crash.

We'll track this down eventually.

 


J Hall liked
ReplyQuote
J Hall
(@zinct)
Member
Joined: 6 months ago
Posts: 99
June 11, 2020 8:54 am  
Posted by: @getdunne

@zinct Thank you for the video. This is so tantalizing. There's no doubt it's crashing for you, but I can't seem to get it to crash.

We'll track this down eventually.

 

Thanks Shane. I'm sure you will crack it sooner or later 🤞🏻


ReplyQuote
saif_sameer
(@saif_sameer)
Member
Joined: 10 months ago
Posts: 37
June 12, 2020 9:48 pm  
Posted by: @zinct

I have been having problems with Unify 1.1.3 crashing and exiting (both standalone and as a VST2 in Cakewalk).

I have just loaded Unify 1.1.3 standalone and managed to get it to crash/exit consistently five times in a row. I did the following..

1. Load Unify
2. Click on browser
3. Load patch Arrival IV - Welcome to Unify 1.1
4. Load patch BPM Clap - Airwave Ambi

Thinks about it for a few seconds then exits every time.

Try these options:

- increasing the audio buffer size, try 1024 samples for example.

- Change the audio device.

Then load Arrival IV, and report back. If it crashes, I will send an edited variant of that patch to help finding out what's causing this issue.

"In heaven, all the interesting people are missing."
Friedrich Nietzsche


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 1 year ago
Posts: 1606
June 12, 2020 11:38 pm  

@saif_sameer

I have been working directly with @zinct via email, and we seem to have found the problem: He was using an older installed version of Dexed instead of the one bundled with Unify. When he removed that, the crashes stopped.


ReplyQuote
J Hall
(@zinct)
Member
Joined: 6 months ago
Posts: 99
June 13, 2020 10:55 am  
Posted by: @getdunne

@saif_sameer

I have been working directly with @zinct via email, and we seem to have found the problem: He was using an older installed version of Dexed instead of the one bundled with Unify. When he removed that, the crashes stopped.

Hi Shane, 

Thanks again for sticking with it and helping to get to the bottom of it. I am pleased that it wasn't actually an issue with 1.1.3.

I have had a good play with Unify 1.1.3 again this morning loading up multiple very taxing patches e.g. Arrival I, II, III and IV plus a couple of BPM drum patches all at once. Seems rock solid and all without any audio glitches when loading patches just like John demonstrates in his livestreams. It is such a creative workflow. 

@saif_sameer thanks for trying to help. 👍 


ReplyQuote
Share: