Notifications
Clear all

Ableton Live Crash / Unify 1.9.1

6 Posts
2 Users
0 Likes
145 Views
(@jeffreyk)
Active Member
Joined: 3 years ago
Posts: 5
Topic starter  

Live 11.2.5 / Mac OS Big Sur / iMac 27 2019 64g

Here is the text from the crash file.  This exact problem is generated each time I try to load the file.  Removing both Unify VST and VST3 from their respective folders allows me to open the file.  Any suggestions on solving this?  Can I regress a Unify version to either solve this problem or at least avoid it on other projects?

Application Specific Information:
Performing @selector(menuItemWasSelected:) from sender NSMenuItem 0x6000908b87e0

Thread 0 Crashed:: MainThread Dispatch queue: com.apple.main-thread
0 com.PlugInGuru.UniWrap 0x000000017430bd71 JuceAU::JuceAU(ComponentInstanceRecord*) + 1137
1 com.PlugInGuru.UniWrap 0x000000017431f8fe APFactory<AUMIDILookup, JuceAU>::Construct(void*, ComponentInstanceRecord*) + 14
2 com.PlugInGuru.UniWrap 0x00000001743290d8 ComponentBase::AP_Open(void*, ComponentInstanceRecord*) + 72
3 com.apple.audio.AudioToolboxCore 0x00007fff21b5563e APComponent::newInstance(unsigned int, bool, void (OpaqueAudioComponentInstance*, int) block_pointer) + 1784
4 com.apple.audio.AudioToolboxCore 0x00007fff21c5c856 instantiate(OpaqueAudioComponent*, unsigned int, bool, void (OpaqueAudioComponentInstance*, int) block_pointer) + 298
5 com.apple.audio.AudioToolboxCore 0x00007fff21c5cbf7 __AudioComponentInstanceNew_block_invoke + 88
6 com.apple.audio.AudioToolboxCore 0x00007fff21aeb095 Synchronously + 87
7 com.apple.audio.AudioToolboxCore 0x00007fff21c5caa4 AudioComponentInstanceNew + 183
8 com.PlugInGuru.Unify 0x000000020ae14771 juce::AudioUnitPluginFormat::createPluginInstance(juce::PluginDescription const&, double, int, std::__1::function<void (std::__1::unique_ptr<juce::AudioPluginInstance, std::__1::default_delete<juce::AudioPluginInstance> >, juce::String const&)>) + 1553
9 com.PlugInGuru.Unify 0x000000020adf557c juce::AudioPluginFormat::createInstanceFromDescription(juce::PluginDescription const&, double, int, juce::String&) + 572
10 com.PlugInGuru.Unify 0x000000020a982508 PluginManager::createWrappedInstance(juce::PluginDescription*, juce::String&) + 1464
11 com.PlugInGuru.Unify 0x000000020a981203 PluginManager::createPluginInstance(juce::PluginDescription*, bool&, juce::String&) + 2451
12 com.PlugInGuru.Unify 0x000000020ac3a3d5 UnifyProcessor::loadPluginInstance(juce::PluginDescription*, int, int, bool&) + 69
13 com.PlugInGuru.Unify 0x000000020ac34274 UnifyProcessor::loadInstrumentLayer(juce::XmlElement*, int, bool, int, int) + 2788
14 com.PlugInGuru.Unify 0x000000020ac319b3 UnifyProcessor::loadPatchXml(juce::XmlElement*, UnifyProcessor::LoadPresetMode, juce::String*) + 6467
15 com.PlugInGuru.Unify 0x000000020ac3e108 UnifyProcessor::loadPatchData(void const*, int, UnifyProcessor::LoadPresetMode, juce::String*) + 56
16 com.PlugInGuru.Unify 0x000000020ac26c17 UnifyProcessor::setStateInformation(void const*, int) + 199
17 com.PlugInGuru.Unify 0x000000020a96e027 juce::JuceVST3Component::setStateInformation(void const*, int) + 279
18 com.PlugInGuru.Unify 0x000000020a9661b6 juce::JuceVST3Component::setState(Steinberg::IBStream*) + 614

This topic was modified 1 year ago by jeffreyk

   
Quote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 
Posted by: @jeffreyk

This exact problem is generated each time I try to load the file.

Please explain in more detail. Load which file? Do you mean when you try to load a patch in Unify, or something else?

Removing both Unify VST and VST3 from their respective folders allows me to open the file.  Any suggestions on solving this?

Run the Unify 1.9 stand-alone app, go to the Known Plug-Ins List, and remove the entries for the Unify VST and/or VST3 if present. Then try the plug-in in again. If this fixes the problem, please let me know ASAP. It might be that Unify is attempting to load one of these instead of the built-in embedded Unify. It should not do that, so if it's doing so, I need to know so I can fix it.

Can I regress a Unify version to either solve this problem or at least avoid it on other projects?

See https://pluginguru.net/unify/manual/doku.php?id=uninstall-106 for details, but it should be sufficient to remove the Unify app (from /Applications) and the Unify plug-ins (from Components, VST, VST3 under /Library/Audio/Plug-Ins), then re-run the Unify v1.8 installer. Let us know if you need help with this.

If at all possible, I'd prefer to track down why Unify 1.9 is failing for you, rather than just downgrade to 1.8 and bury the issue. I'll understand if you're working on a production Mac that you simply must keep working. Either way, please advise.


   
ReplyQuote
(@jeffreyk)
Active Member
Joined: 3 years ago
Posts: 5
Topic starter  

Doh!  Poor bug reporting.  The crash is on loading an Ableton Project File.  Its a file that has existed for a couple of weeks and been opened and closed daily.  It uses several instances of Unify - apparently a mix of VST2 & 3.  It has been stable through until the Unify update.

I will try the middle recommendation and report. 

I am happy to work with you to unpack the issue.  Although this project is important (I wrote it for my sons wedding this past weekend), I don't make a living from this so can put some effort into problem solving.  I do use this Mac for my work so that will influence when I am able to do testing


   
ReplyQuote
(@jeffreyk)
Active Member
Joined: 3 years ago
Posts: 5
Topic starter  

Put both Unify VST and VST3 back in their correct folders. 

Removed the Unify VST from the plugin list in standalone Unify.  The Unify VST3 was not listed. 

The project file loaded.  Rescanned the plugin list in Live, saved and relaunched the project file. 

The project file now loads and all Unify instances function as expected.


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

Put both Unify VST and VST3 back in their correct folders. 

Removed the Unify VST from the plugin list in standalone Unify.  The Unify VST3 was not listed. 

The project file loaded.  Rescanned the plugin list in Live, saved and relaunched the project file. 

The project file now loads and all Unify instances function as expected.

Terrific, thank you, and I'm glad it's working for you again.

I'm pretty sure removing the Unify VST from Unify's Known Plug-In List is what fixed this. That's good to know, because it indicates a potential issue with Unify itself (which I will look into).

BTW I don't recommend mixing VST and VST3 Unify instances in future DAW projects. If your DAW supports VST at all, use that, otherwise VST3.


   
ReplyQuote
(@jeffreyk)
Active Member
Joined: 3 years ago
Posts: 5
Topic starter  

Thanks for the tip.  I will not use the VST3 for future projects.


   
ReplyQuote
Share: