Old 12-13-2016, 04:59 PM   #1
Human being with feelings
Join Date: Dec 2016
Posts: 2
Default Plugin .ini files – skip plugin scanning


I administer Reaper in a managed macOS environment and have a quick query re the plugin .ini files that someone may be able to assist with...

Users have network home directories on the various Macs, which in many respects is great as it ensures their Reaper prefs travel with them. However, plugins are an issue because different systems have different plugins and I don't want students to have to go through the lengthy scan process each time they move between rooms. I've therefore written a script which runs at login (using Outset) that compares the various .ini plugin files in a user's ~/Library/Application Support/REAPER directory with the plugin file that they need for a particular system (using a SHA256 hash)... if the checksums don't match then it copies the relevant 'template' file into their directory. In principle I think that this should work but can anyone advise me as to the finer points of the plugin-initialisation scan? Is there anything else I need to consider?

orbsmiv is offline   Reply With Quote

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 02:28 PM.

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