Notifications
Clear all
Topic starter
April 24, 2022 5:50 pm
I am doing some testing today in Reaper with multiple Unify instances in a project as I am planning to use multiple instances in my template.
Running 16 Unifys with 4 synths each (total 64 synths).
Able to run all of them with maximum ASIO buffer size (2048).
CPU used is around 76%.
I am just wondering how Unify handles CPU core/thread management when running multiple instances?
(Performance meter readings from Reaper are attached.)
April 24, 2022 6:44 pm
I am just wondering how Unify handles CPU core/thread management when running multiple instances?
It's not Unify that handles core/thread management; it's the operating system. All Unify does is run a separate thread for every layer. This allows the operating system to spread the load across available cores as close to optimally as it can.
Topic starter
April 24, 2022 6:46 pm
@getdunne OK...that is what I thought. That is awesome!
Very impressed that I can do that on a 4th gen Core i-5 from 2013...
Topic starter
May 9, 2022 7:26 am
Unify has been crashing Reaper intermittently. Latest version of Reaper Win 6.57 running on Windows 10. Unify 1.8 Standard.
Here is the crash log from Windows:
Fault bucket 2198510653685090536, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: reaper.exe
P2: 6.5.7.0
P3: 6276d867
P4: Unify.dll
P5: 1.8.0.0
P6: 620ea393
P7: c0000005
P8: 00000000000f7e50
P9:
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER556D.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER584C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER586C.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER586A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER588B.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_reaper.exe_1c973cf6e0d29c5331d9bbea78e9a76802d7942_f8ad0031_172637eb-7edb-4e0b-8249-c39376bf62e0
Analysis symbol:
Rechecking for solution: 0
Report Id: 307408fa-d5c4-4e9c-b57f-4e1973f69bee
Report Status: 268435456
Hashed bucket: 4cd7029b089f6bc2fe82adca93cfc8e8
Cab Guid: 0
Faulting application name: reaper.exe, version: 6.5.7.0, time stamp: 0x6276d867
Faulting module name: Unify.dll, version: 1.8.0.0, time stamp: 0x620ea393
Exception code: 0xc000041d
Fault offset: 0x00000000000f7e50
Faulting process id: 0x1a20
Faulting application start time: 0x01d8634d97ce63ee
Faulting application path: C:\Program Files\REAPER (x64)\reaper.exe
Faulting module path: C:\VSTPlugins\Synths\Plug In Guru\Unify.dll
Report Id: f9e11c91-2284-4067-ae52-5082e94e6eee
Faulting package full name:
Faulting package-relative application ID:
Topic starter
May 9, 2022 8:35 pm
I have found a way to Unify load in Reaper without crashing. Running as a dedicated process:
https://reaperblog.net/2012/02/run-plugin-as-dedicated-process/
Topic starter
May 9, 2022 8:50 pm
May 18, 2022 1:10 pm
Thanks for the report, Tony, and especially for reporting to Cockos too.
I think that exception code is related to Internet Explorer, and might be getting triggered when Unify attempts to prepare itself to display HTML content (a feature added in Unify 1.8). I have added a note about this to your bug report on the Cockos Reaper forum.
