[6.73] JSFX not found when in a subdirectory of current project
A JSFX can be installed in the "Effects" subdirectory of a project.
My project uses different JS, each one using various import files, and these JS are in different subdirectory of the "Effects" project.
However, while the organisation is correctly working the first time I install the JS effects, these effects are not found when I reopen the project. The attached example project, "JSFX-in-Project.zip", uses a JS "A new JS FX" located in the "Subdir" directory of "Effects".
"Screen-1" shows the project working the first time the JS is inserted in a track.
After a save and a load of the project, the JS is not found anymore ("Screen-2").
I think the subdirectories are not supported for Project folder JSFX, so everything directly under the Effects folder.
(It was like that all the time, I found it years ago.)
I think the subdirectories are not supported for Project folder JSFX, so everything directly under the Effects folder.
(It was like that all the time, I found it years ago.)
May be.
But if something is NOT SUPPORTED it does not mean it is a Bug, well?
If support for Project folder JSFX Effects would be stated as "FULLY SUPPORTED" then for sure we can call it a BUG. (But I am not sure of the extend of support for this function).
May be.
But if something is NOT SUPPORTED it does not mean it is a Bug, well?
If support for Project folder JSFX Effects would be stated as "FULLY SUPPORTED" then for sure we can call it a BUG. (But I am not sure of the extend of support for this function).
Btw, I think it would be good if subfolders would be supported as now you can have two (or more) jsfx files with the same name because originally they are located each in its own folder, but when collecting them to project folder, you need to put them all in one folder which leads to problem with multiple files having the same name, thus requiring to rename them if possible...
Also I have feature request to add action to automatically compile (copy) JSFX effects to project folder for portability, so no need to do that manually.
Also another request is to add new feature - lets call it "In Project" JSFX Effect whih is the same as folder in project folder, but the JSFX codes would be included directly in RPP project file (absolutely my favorite option) - (Something like with external .MID files versus "in project" MIDI items)!
I think the subdirectories are not supported for Project folder JSFX, so everything directly under the Effects folder.
(It was like that all the time, I found it years ago.)
Well, the first time you insert the JSFX, the subdirectories are supported... My very complex project with independent subfolders and subsubfolders does work. Until I save and reload it. So it looks that it should not be so complex to obtain a consistent behaviour.
Having "Effects", "Data" and "Presets" folders inside the project folder is the best way to have independent projects you can easily use and suppress. As a teacher, I can provide students with projects they can test, even on USB keys, with no need to modify their personal libraries.
Now, it is also hard to know if something is fully supported or not. The people at REAPER do a lot of impressive work, but many existing features are not documented, and documentation is sometimes imprecise.
I add a remark which is relative to this thread, but could also appear in the "REAPER Feature Requests " or "Dstruct's Casa De Nitpicks".
While I can have almost "self contained" projects, with a subdirectory "Effects" where the JSFX of the project are placed, and a subdirectory "Data" where JSFX data are placed, I fail to manage a "presets" directory for my JSFX presets.
This is related to the way JSFX presets are handled by REAPER. When the JSFX plug-in "toto" is in the "sub" directory of "Effects" in the REAPER ressources directory (RRD), its presets are kept in the RRD as "effects/js-sub_toto_jsfx.ini". When the JSFX plug-in "toto" is in the directory "Effects" in a project "X", its presets are also kept in the RRD, but this time as "effects/js-_Project__toto_jsfx.ini". So clearly, REAPER makes a distinction between both cases. However, I fail to have these presets installed where they logically should be, inside an "effects" subfolder of the project itself. This prevents having completely self contained projects, and imply that independent projects, using the same JSFX plug-ins, should share common presets.
Could it be possible, in the case of plug-ins embedded in a project, to have the associated presets also located in the project directory, for example in a "presets" subdirectory ? When saving/loading a preset, REAPER would first search in this subdirectory, before using the preset in the RRD. This would be a much cleaner and secure approach.