Closed dhilowitz closed 3 years ago
Thanks for reporting this! It was due to a change in macOS Catalina. The next release of ReaPack will be adjusted for this. In the meantime, here's a fixed build: https://ci.appveyor.com/api/buildjobs/cbjg3o4bvvjp8w4o/artifacts/build%2Freaper_reapack-x86_64.dylib.
Thanks so much for this!
On Tue, Mar 16, 2021 at 10:00 AM Christian Fillion @.***> wrote:
Thanks for reporting this! It was due to a change in macOS Catalina. The next release of ReaPack will be adjusted for this. In the meantime, here's a fixed build: https://ci.appveyor.com/api/buildjobs/cbjg3o4bvvjp8w4o/artifacts/build%2Freaper_reapack-x86_64.dylib .
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/cfillion/reapack/issues/34#issuecomment-800281764, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEN6HS5YOEB75B3SJI7TKDTD5QBFANCNFSM4ZGX55OQ .
I have a super niche problem. I use REAPER on two computer. I use Dropbox to share my REAPER settings directory between the two machines so that I can keep my settings in sync. The way that one does this on Mac is by symlinking the directory as follows
For years, this was working well for me, but sometime last year a message start popping up:
Is there any way that I can continue to use ReaPack with my special configuration?