Hmmm, Ive had this exact problem on so many version of macOSX and Reason that I have lost count.
Yes, that location is where Reason 'seems' to store and relate to Maps, but it does not register in Reason when you edit any of those, including the codecs.
What I found does work, is this:
- go the Reason.app in your applications folder, then right click on it and select the 'Show Package Contents' option.
- Now, Finder will open the app (which is a compressed file) and show a folder called 'Contents', open that
- Next, you will see various other folders, Frameworks, MacOS etc, but the one you want to open is 'Resources'
- Now, you will see lots of files, scroll down until you see a folder called 'Remote', open that
- You will now see 4 folders, BuiltInCodecs, BuiltInMaps, DefaultCodecs and DefaultMaps
- If you open DefaultMaps, you will see all the same folders as you saw in the /Library/App Support/....etc location.
Edit or copy in your map(s) to the correct folder then close that Finder window, or navigate your way back up to the Applications folder.
This, by the way, is the place where Reason is getting the maps from, even though you emptied the relevant folder in the Application Support location.....
Now, start up Reason and check your map changes, I bet they are referenced correctly.
Whenever I now customise my maps, I make them in the actual Reason app, pretty sure it's a bug.
I have also made custom controllers along with maps and codecs, and I just put them in there rather than bothering with the application support folder, it's always worked for me.
The only downside that I have found is that I have to keep copies elsewhere as if you update Reason, the Reason.app file is updated and the maps etc that you copied in will be lost. So, keeping them elsewhere means you just have to copy them in once more after the update.
I guess they will fix this one, one day
