After 1.5 update, no longer able to open miniraze [even if i go back to 1.1.6] - on mac os x 13.7.8

Official support for: mok.com
RELATED
PRODUCTS
Miniraze$99.00Buy

Post

Can you let me know which email to contact you at? THANKS for your attention to this~ I'm just getting to enjoy Miniraze and really looking forward to the new update.

Post

Will go back to 1.1.6 for now...
You do not have the required permissions to view the files attached to this post.

Post

multitrackerZ wrote: Fri Jan 02, 2026 7:47 pm mok.zipHere are some kind of log files that I found. Not sure if this is helpful but here it is~
Thanks for that. The logs show you are running v1.1.6 (not v1.5.1), but these are just the logs for Miniraze installer and the runtime log. Oddly, the log shows that things startup and shutdown just fine (the errors at the end are just some DSP validation things, not crashes), so no idea what is going on.

Are you able to download and install v1.5.1?

And also, if you get a crash, there should be a window that pops up, and you can get more information (or a Report button) where you can see the crash log data. That specific info would be helpful. However, I would see about installing v1.5.1 first.

Another thing to try if v1.5.1 doesn't run... move the existing patch database and preferences, these are located in:
~/Library/Application Support/mok/miniraze. To keep your previous setup safe, you can just rename the miniraze folder to minirazeAlt (or whatever). Then running the Standalone app will recreate this data. If that allows you to launch, then it gives a clue to what might be happening. If this works, you can quite Miniraze, and copy the patch folder from minirazeAlt back to miniraze . Then try the standalone app that will rebuild the patch database, to get your custom patches back into place... It's a hacky step, but might shed some light on what is going on if other aspects fail.

You can reach us ( and message me) on Discord: https://discord.gg/QhbkKdfHJh
Or email is also fine: info [at] mok [dot] com

Post

Perfect. Yes, I'll try those steps. (I must have sent the logs that were from when I re-installed 1.1.6 but I think that there are some log entries that reference 1.5.1)

I have tried installing and re-installing 1.5.1 a few times now...

For context and general info I have already :

1: deleted all files MOK related that I can find (components, VST, VST3 and standalone) and installed 1.5.1 fresh (crashed)
2: deleted all files MOK related that I can find (components, VST, VST3 and standalone) and reinstalled 1.1.6 (works)
3: deleted all files MOK related that I can find (components, VST, VST3 and standalone), cleared plugin cache in Reaper, and then installed 1.5.1 (crashed)

Post

unfortunately none of the steps above worked... I sent you a crash report and videos to your general email box provided. Hopefully we can find a way to the bottom of this mystery (and I hope that I'm the only one who's having these issues)

Post

THANKS TO MOK AND THEIR EXCELLENT SUPPORT, I NOW CAN REPORT I HAVE A WORKING 1.5.1 MINIRAZE~

For any others who may run into the odd crashing behaviour I experienced here's what I did just in case it may help.

With 1.1.6 installed, but not running, I did the following:
- deleted the file “miniraze.patch2_db”

Then I :
- installed the 1.5.1 standalone app only.
- checked the directory " ~/Library/Application Support/mok/miniraze” and found that the “Miniraze.patch2_db” had been recreated.
- started the standalone app and it worked!
- installed 1.5.1 VST3 and opened DAW. plugin also worked now!!
- installed 1.5.1 AU and opened DAW. AU plugin also now works!!!

Post

Glad to hear that worked! In this case (and some other users), the problem was due to the way the startup patch was getting loaded. Deleting the miniraze.patch2_db is a way to get things reset to avoid that scenario.

I have not been able to reproduce this issue, but your crash log was very helpful, and I also had another crash log from a user that indicated the same source problem. I believe I have a fix for this now, but again, since I cannot reproduce it on my side, I am not 100% sure.

Miniraze v1.5.2 has been posted today, hopefully with the fix to avoid this issue in the first place.

Thanks again for sending the crash logs!

Post

Got it working again via mok creating the update patch for Intel macs. That worked for me, and got my lost user presets back again.

Thanks for your awesome support!

Post

FineSynth wrote: Wed Jan 07, 2026 5:41 pm Got it working again via mok creating the update patch for Intel macs. That worked for me, and got my lost user presets back again.

Thanks for your awesome support!
Really glad to hear! I saw your post on our Discord as well, thanks for sharing that things worked.

Cheers! - Rob

Post

trdmc wrote: Sat Dec 20, 2025 11:26 pm Same issues here with the 1.5 update. Does not work on my Intel Mac running Logic Pro 11.0.1.
I've been really excited about Miniraze in some of my new projects.
THe Miniraze v1.5.1 build fixed my Intel Mac issue in Logic Pro - thanks for the fix!

Post

I'm having th same issue with Minirazer and as others have reported the previous version worked fine.This crashes on cakewalk and Bitwig and the stand alone. Here is a crash log from Cakewalk.
You do not have the required permissions to view the files attached to this post.

Post Reply

Return to “Media Overkill (MOK)”