Interesting - I had never tried that.
I do remember ages ago I had pushed for REAPER to look for an "effects" subfolder in current project directory as a source for JSFX, so you could easily include fx portably and without concerns that an updated version of a JSFX would break your project (eg. added sliders etc).
However with ReaScripts, since they have to be manually imported I can't see why the source path should make any difference.
Now, of course, if they didn't have to be manually imported and auto-loaded from your main script folder on launch + any project-specific ones auto-loaded from a script subfolder in project directory on project load, that would open up new possibilities. But.. is it also then a security risk, since an imported .py could delete & do other damage?
__________________
Proudly using REAPER exclusively for...
* Media and event music composition & production, sound design + auto-processing at Qsonics.com
* Broadcast branding, promos, education & training and narration voice-overs at DrewWhite.com
|