Notifications
Clear all
Questions about UNIFY
2
Posts
2
Users
0
Reactions
291
Views
Topic starter
December 15, 2025 12:04 am
Hi, I have noticed unusually high cpu usage in all Unify 2 instances where I have bypassed plugins in a synth chain (ex. DMG trackComp or Ghz Tupe). Deleting them clears up considerable cpu. This seems to happen both on intel 10.15.7 and Seqoia ARM 15.7.2. All my previous sessions in Ableton Live 11/12 and FL studio 2024/5 with such instances have to be manually toggled every session start (track comp OS setting) to get back some cpu.
Included is a hopefully relevant crash report along with an extreme crash instance. Cheers and Thanks.
-----
Process: Live [2018]
Path: /Applications/Ableton Live 11 Suite.app/Contents/MacOS/Live
Identifier: com.ableton.live
Version: 11.3.43 [2025-10-06_b466d4f56c] (11.3.43 [2025-10-06_b466d4f56c])
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Live [2018]
User ID: 501
Date/Time: 2025-12-14 18:48:08.041 -0500
OS Version: Mac OS X 10.15.7 (19H1615)
Report Version: 12
Thread 429:: Triggered Scope Rendering Thread
0 libsystem_kernel.dylib 0x00007fff6797f882 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff67a40425 _pthread_cond_wait + 698
2 libc++.1.dylib 0x00007fff64b0c623 std::__1::condition_variable::__do_timed_wait(std::__1::unique_lock<std::__1::mutex>&, std::__1::chrono::time_point<std::__1::chrono::system_clock, std::__1::chrono::duration<long long, std::__1::ratio<1l, 1000000000l> > >) + 93
3 com.PlugInGuru.Unify2 0x00000001855a3353 0x184f88000 + 6402899
4 com.PlugInGuru.Unify2 0x00000001855a5427 0x184f88000 + 6411303
5 com.PlugInGuru.Unify2 0x00000001855a3f80 0x184f88000 + 6406016
6 com.PlugInGuru.Unify2 0x00000001855cfd76 0x184f88000 + 6585718
7 libsystem_pthread.dylib 0x00007fff67a40109 _pthread_start + 148
8 libsystem_pthread.dylib 0x00007fff67a3bb8b thread_start + 15
Thread 430 Crashed:: Dispatch queue: CA::CG::Queue
0 libsystem_kernel.dylib 0x00007fff6798333a __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff67a3fe60 pthread_kill + 430
2 libsystem_c.dylib 0x00007fff6790a8a2 __abort + 139
3 libsystem_c.dylib 0x00007fff6790a817 abort + 135
4 libsystem_malloc.dylib 0x00007fff67a0050b malloc_vreport + 548
5 libsystem_malloc.dylib 0x00007fff67a11d27 malloc_zone_error + 183
6 libsystem_malloc.dylib 0x00007fff679f8ced small_free_list_remove_ptr_no_clear + 1243
7 libsystem_malloc.dylib 0x00007fff679f5b3b free_small + 853
8 com.apple.CoreGraphics 0x00007fff2ec27b1c CG::Path::~Path() + 50
9 com.apple.CoreFoundation 0x00007fff2e8a5f39 _CFRelease + 238
10 com.apple.QuartzCore 0x00007fff3a1a0a22 CA::CG::FillPath::~FillPath() + 28
11 com.apple.QuartzCore 0x00007fff3a12a352 CA::CG::Queue::render_callback(void*) + 456
12 libdispatch.dylib 0x00007fff677e2658 _dispatch_client_callout + 8
13 libdispatch.dylib 0x00007fff677e7d7e _dispatch_lane_serial_drain + 911
14 libdispatch.dylib 0x00007fff677e85d6 _dispatch_lane_invoke + 363
15 libdispatch.dylib 0x00007fff677f1c09 _dispatch_workloop_worker_thread + 596
16 libsystem_pthread.dylib 0x00007fff67a3ca3d _pthread_wqthread + 290
17 libsystem_pthread.dylib 0x00007fff67a3bb77 start_wqthread + 15
This topic was modified 9 months ago by Graig
December 16, 2025 2:17 am
A few questions:
Are you using fixed block size processing in FL Studio (per plugin setting) ? (Because currently Unify has issues with the variable/constantly changing block size in FL Studio - which impacts audio processing load significantly).
What are your interface settings?
Are you a prior user of Unify1 - if so, did you observe the same issues with Unify1?
Are you seeing CPU (audio load indicator in Unify2 is actually audio proecessing load) go high only when disabling effect plugins?, and does this happen for all the plugins you are using or just some specific ones (I've not been able to repeat with various effects/instruments on my machines - the bypass/power button toggle doesn't appear to make the load higher).
"such instances have to be manually toggled every session start (track comp OS setting) to get back some cpu. " - can you explain further - do you mean removed from Unify, or disabling the whole Unify instance in your DAW or?
The included crash report: in what scenario did that happen - is there anything specific you were doing with Unify2 when it happened? Is it repeatable?