MacOS 10.12 Sierra: App Translocation can cause issues with Reaper (SOLVED)

After updating to macOS 10.12 Sierra, I had a weird Reaper startup issue, as described in this thread: http://ift.tt/2ddFNWl

I FOUND A WORKAROUND - here's how:

I checked console during startup of Reaper:

default 13:27:49.552434 +0200 REAPER No Info.plist file in application bundle or no NSPrincipalClass in the Info.plist file, exiting
default 13:27:54.573758 +0200 lsd SecTranslocate: problem deleting translocation after app death: /private/var/folders/pj/12k8clzd41sfv1v84syvt_mw0000gn/T/AppTranslocation/1C9371A1-FE66-408A-9B6F-576A85CFF08C/d/REAPER64.app

So my initial hunch was right, there is an issue with macOS moving the app to another (random) place for security reasons, it's called App Translocation. Following this lead I found this article: http://ift.tt/2ddGsXx

Apparently when opening the Reaper DMG and moving both REAPER64.app and ReaMote64.app (using the macOS 64bit bundle here) using the provided Applications shortcut, this will for some reason trigger App Translocation and thus prevent Reaper from starting.

SOLUTION: create a new subfolder inside ~/Applications (any name will do) and move both Reaper binaries into it using Finder. This will disable App Translocation for Reaper and it will start up as usual.

MacOS 10.12 Sierra: App Translocation can cause issues with Reaper (SOLVED)