Hi everyone, never had an issue with melodyne but since I updated to MacOS 26.4 I keep receiving this error and Melodyne doesn't load properly.

Do you know how to resolve?

I tried removing the celemony preferences. Removing the plugin by using the melodyne "uninstall". And also by removing the component and vsts by hand. Still not working after reinstall.




Thank you

 

I have been having the same issue. Have tried everything you mentioned to try and fix it but haven't succeeded.

 

+1

 

Up

 

Up
@MORiA help

 

Last edited: Apr 10, 2026

Celemony haven't updated Melodyne with "official" suppoort for Tahoe. Maybe some of us can learn to not update MacOS chasing version numbers and checking that all needed audio software actually works on the new version of MacOS. Yeah,right...who am I kidding here?

If the ARM slice of the binary is broken on Tahoe and you really have to force it to run via Rosetta, use the command lipo in Terminal to strip the ARM slice.

People seem to be recommending using Vovious instead, but I do not see that as a viable replacement for Melodyne. But you could try it.

 

any news about this problem...

 

Do you have their website blocked by your firewall or hosts file? If this was fixable by any of the releasers, it's a safe bet they would have already done so.

This is the Terminal commands people have been sharing as a "workaround", but really all you are doing is stripping the broken ARM slice of the binary out and forcing it to only run via Rosetta so ymmv:

cd /Library/Audio/Plug-Ins/Components

sudo find . -name "Melodyne.component" -execdir lipo -extract x86_64 {}/Contents/MacOS/Melodyne -o {}/Contents/MacOS/Melodyne.1 \;

sudo find . -name "Melodyne.component" -execdir mv {}/Contents/MacOS/Melodyne.1 {}/Contents/MacOS/Melodyne \;


A cleaner version might be like this:

cd /Library/Audio/Plug-Ins/Components

sudo find . -name "Melodyne.component" -type d | while IFS= read -r comp; do
bin="$comp/Contents/MacOS/Melodyne"
tmp="$bin.tmp"

[ -f "$bin" ] || continue

cp "$bin" "$bin.universal" 2>/dev/null

lipo -extract x86_64 "$bin" -o "$tmp" && mv "$tmp" "$bin"
done

 

Last edited: Apr 15, 2026

I have a legit version of Melodyne which is on a single computer where Tahoe is 24.6.1 and everything works as it should. I have a MORIA version that works on a Lap Top, the same Tahoe but 26.3.1. That's why I installed Tahoe 26.4.1 because it works on 26.3.1, that's on a third computer and it doesn't work there.

 

+1
vst3 doesn't work anymore after update to 26.4

 

/end thread.

Unless you bought a new computer shipped with Tahoe, it doesn't make any sense if you use these products to update your os.

Especially since the developer doesn't state "official" support, and either most or a lot of them actively warn off it.

Let alone possibly using k's of it.

 

I have their domain blocked both ways, so I can't go look for anything from them. But I can look elsewhere, and someone reported that Moria's 5.2 version works in Tahoe. "UPDATE: I've now managed to get Melodyne 5.2 standalone working. So I have VST3, AU (checked with Bluecat Patchwork) and ARA working with Cubase 15, plus the standalone. Not tested extensively but all seems well.

The terminal commands with the 5.2 release all work plus I added:

sudo -s chmod 775 /Applications/Melodyne\ 5/Melodyne.app/Contents/MacOS/Melodyne
sudo codesign -fs - /Applications/Melodyne\ 5/Melodyne.app
This fixed the standalone."

I'm apprehensive to just post something I can't test myself. Re-codesigning plugins after using Lipo on them is not always necessary, but it can be depending on how the signature may be broken. So that part makes sense.

 

Last edited: Apr 15, 2026

standalone working but ARA not work