Notifications
Clear all

Unify 1.8.0 crashing (MAC)

8 Posts
2 Users
0 Reactions
839 Views
(@melodialworks)
Active Member
Joined: 2 years ago
Posts: 7
Topic starter  

macOS Monterey 12.2.1

Unify 1.8.0 (stand alone)

 

Often, as of late, when I’m going through patches Unify is happy for awhile.  Then, it crashes (not responding) and I have to use FORCE QUIT. After that, when I run Unify again and start to again patches, it almost immediately crashes again.

 

I never used to have this issue. 🙁


   
Quote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4437
 

@melodialworks

Thank you for the report, and I'm sorry to hear you're having this trouble. This is the first time I've seen this issue reported.

I usually distinguish between "crashing" (program quits unexpectedly) and "hanging" (program not responding, but does not quit). This sounds like hanging.

If you get any crash report from MacOS, please save (preferably in plain-text format), zip and post here.

This can be a very difficult thing to reproduce. Any hints you can provide would be very helpful.

  • Is there a specific sequence of patch changes that reliably causes Unify to hang?
  • Does this happen only in some libraries (esp. unified libraries), or will it happen even in the Standard Library?

   
ReplyQuote
(@melodialworks)
Active Member
Joined: 2 years ago
Posts: 7
Topic starter  

Thank you for your reply.

I am getting hanging, i.e. "not responding".

Moving forward I will keep track of what I am doing, and specifically report back, but it has occurred while auditioning patches from "Unified - Korg Wavestate Native", "PluginGuru MegaMagic Keys" and "PluginGuru MM Pads 2 Mosaic".

By crash report, I'm assuming you mean the log found at Utilities | Console | Crash Reports ?

 

 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4437
 

@melodialworks

MacOS typically pops up a crash-report window shortly after any app crashes, and usually after you force-quit as well. I wasn't actually aware there was a list available in the Console app, but I just looked on my Monterey machine and there it is. Useful to know -- thank you.

Problems with newly-released plug-ins such as Wavestate Native don't surprise me (I've heard of others already), but if Unify is hanging when loading patches from a Unify-only library such as the two you mentioned, I'd like to figure out why.

Whenever any app seems to hang, check to see if there might be a dialog box somewhere, perhaps buried beneath some other window due to a programming error. It might just be sitting there waiting for you to click "OK".

Things to watch for when Unify hangs:

  • Can you still play and hear notes?
  • Can you move the Unify main window, or any of other windows it has opened?
  • Can you do any other operations?
  • When the mouse-cursor is over Unify, does the cursor change to the rotating "app not responding" animation?

   
ReplyQuote
(@melodialworks)
Active Member
Joined: 2 years ago
Posts: 7
Topic starter  

It is happening again with the PluginGuru Del Norte EDM Chill library (the unify one). So a Unify-only library . . .

Yes, I can still play and hear notes - limited to the patch that it was on when the “not responding” occurs.

I can move the main window. (No others were open)

I can’t do any other operations.

There is no dialog box waiting for an “OK”.

Yes, the cursor changes to the beach ball, when I move the cursor over the unify application.

 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4437
 

@melodialworks

This is certainly a puzzler. When you say you "never used to have this problem", do you mean before updating to MacOS Monterey? I'm wondering if this might be a Monterey compatibility thing. As I said, no one else has report this, to the best of my knowledge.

Another thing you might try: enable CPU meters in Unify Settings, and tell me what happens to the meters when Unify hangs on you.


   
ReplyQuote
(@melodialworks)
Active Member
Joined: 2 years ago
Posts: 7
Topic starter  

It has happened again, this time loading a Standard Library patch.

I use the CPU keyboard to change patches, pressing the down key for the next patch. I have noticed that when it fails, I have pressed the arrow key on the keyboard, the cursor moves down (as expected) but then jumps back up to where it was, then I get the beachball.

I did enable tie CPU monitoring and in this case very little activity. (Screenshot attached).

I don't know for sure that this problem developed with the upgrade to macOS Monterey, but it actually if fairly likely . . .

 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4437
 
Posted by: @melodialworks

I use the CPU keyboard to change patches

This is the critical bit I was missing. John has also noticed that Unify can lock up like this when using the arrow keys to change patches, and he's on an older Mac that does not use anything as recent as Monterey.

I'll look into this issue further. In the meantime, I'd suggest using the arrow buttons at the top of the GUI to change patches instead of the arrow keys on the keyboard.


   
ReplyQuote
Share: