Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER for macOS

Reply
 
Thread Tools Display Modes
Old 10-22-2018, 02:15 AM   #1
mikefloutier
Human being with feelings
 
mikefloutier's Avatar
 
Join Date: Dec 2007
Location: Cornwall, UK
Posts: 111
Default Plugins don't work after macOS change - help!

1. I'm a long time Reaper user on my late 2012 Mac mini. I always stuck with Mountain Lion ("if it ain't broke...") until recently as my browsers became unsupported and I decided to update my OS.

2. I installed High Sierra on a separate partition to test it and when I was happy decided to update my Mountain Lion partition - which contained all my Reaper projects and plugins etc.

3. BUT, when I tried to do this I found that High Sierra had been withdrawn and Mojave was being offered instead - Hmm

4. Stupidly I updated my Mountain Lion partition to Mojave and deleted my High Sierra partition - at least I had backups of everything.

5. Belatedly I discovered that my Audio Interface people (Tascam) only had drivers up to High Sierra and that my US-1800 (now a legacy product) was in a queue for Mojave driver development.

6. I won't bore you with the convoluted path but I finally managed to recover the Mac's original Mountain Lion OS which I was able to update to High Sierra. Naturally I restored my backed up files, including my Reaper project files (not including any added plugins)

7. I got the High Sierra drivers for my audio interface and downloaded a fresh Reaper64 which runs fine - ie when simply adding a sample wave file.

8. The trouble started when I tried to open a recent project:

a) The standard 32bit warning was ok; as I read on here so I ignored that,

b) I then got "Registry Error" warnings which I'm not sure about,

c) Then it would tell me about all the plugins that were missing. I still had my Mojave partition, which contained all my old folders, from when it was the original Mountain Lion, which included loads of the Reaper plugins that I was now missing. I copied as much of what looked relevant to similar folders on my new High Sierra, naively thinking this would satisfy my existing Reaper projects which had used these plugins in the past.

d) Now Reaper would simply crash during loading any project containing any non-native plugins,

e) Finally, I found that, at this point, it would still run fine by starting a new project BUT, if I tried to add any of the plugins I had "imported" from my old partition/OS, although "add FX to track" would happily LIST all these plugins, when I tried to LOAD them it reported that "the following effect plugin could NOT be loaded"

HELPPPPP!
mikefloutier is offline   Reply With Quote
Old 10-22-2018, 04:36 AM   #2
cyrano
Human being with feelings
 
cyrano's Avatar
 
Join Date: Jun 2011
Location: Belgium
Posts: 5,246
Default

Sounds like your plugins are being blocked by SIP?

I suppose you haver verified paths to plugins in Reaper's preferences. Maybe disable SIP as a test?

Keep in mind that if you have aliases to folders or files, the transition to APFS may have disabled those. And copying (system) files from an APFS disk to an older system might have unpredictable results.
__________________
In a time of deceit telling the truth is a revolutionary act.
George Orwell
cyrano is offline   Reply With Quote
Old 10-22-2018, 10:22 AM   #3
mikefloutier
Human being with feelings
 
mikefloutier's Avatar
 
Join Date: Dec 2007
Location: Cornwall, UK
Posts: 111
Default

Quote:
Originally Posted by cyrano View Post
Sounds like your plugins are being blocked by SIP?

I suppose you haver verified paths to plugins in Reaper's preferences. Maybe disable SIP as a test?

Keep in mind that if you have aliases to folders or files, the transition to APFS may have disabled those. And copying (system) files from an APFS disk to an older system might have unpredictable results.
Thanks Cyrano, what is SIP? I can't see it mentioned in the Reaper manual.
mikefloutier is offline   Reply With Quote
Old 10-22-2018, 11:55 AM   #4
CynicalDux
Human being with feelings
 
Join Date: May 2018
Posts: 5
Default

Quote:
Originally Posted by mikefloutier View Post
Thanks Cyrano, what is SIP? I can't see it mentioned in the Reaper manual.
https://support.apple.com/en-us/HT204899

Basically it’s a protection from apple to block unsigned/unknown-by-apple/32 bits apps.

You can disable and allow apps on the security pane of preferences. ‘cause sometimes apple block the app without any warning or the app just crash.

a check of the filesystem can help too, which can be done in the disk utility or with apps like disk warrior.

Hope that helps!

Cheers!
CynicalDux is offline   Reply With Quote
Old 10-22-2018, 03:48 PM   #5
cyrano
Human being with feelings
 
cyrano's Avatar
 
Join Date: Jun 2011
Location: Belgium
Posts: 5,246
Default

Like Cynicaldux explained, it's malware protection. "System Integrity Protection"...

And yes, a file system check could be a good suggestion too. Personally, I'd first try that while booted from the recovery partition, though.
__________________
In a time of deceit telling the truth is a revolutionary act.
George Orwell
cyrano is offline   Reply With Quote
Old 10-31-2018, 10:13 AM   #6
FriedaCalor
Human being with feelings
 
Join Date: Feb 2016
Posts: 19
Default

If all else fails Time Machine can save you. Always have it working. You might need to revert to High Sierra. New OS are always to be suspected until proven, especially if you're in the middle of a project.
FriedaCalor is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 09:01 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.