Re: Craig Anderton's guitar for Rapture and Rapture LE
2015/09/27 12:57:00
(permalink)
Thanks Craig for the confidence. I have not seen a Rapture LE installation in some time and your Guitar package is one of the few Rapture packages I do not have. Both Rapture and Rapture LE rely on the registry to determine where samples are found. If the registry entries point to the same locations then they will work from the same data.
The 64bit Rapture registry entries are in HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\rp
I would guess there is a similar entry for LE, instead of rp probably rple (if it is similar to the DPro layout which I did find a reference to in another post).
By default the samples should be in the Multisamples folder in the path pointed to by the "Contents Folder" in the above registry entries. This can be overridden if there is a "Multisamples Folder" in the same registry entry. In that case the Multisamples folder would be under the path specified in it. For example, the default Rapture "Contents Folder" is C:\Program Files\Cakewalk\Rapture. This makes the default location for the samples C:\Program Files\Cakewalk\Rapture\Multisamples. If there is a "Multisamples Folder" entry in the registry, say D:\Cakewalk\Rapture; then the samples would be in the path D:\Cakewalk\Rapture\Multisamples. From there, most packages install their samples is a folder below the Multisamples folder.
The program location is hard-coded in Rapture and I would assume it is the same in Rapture LE. While I have found a post which suggests there might be a different path for LE, the instructions I found for free programs from Cakewalk indicate they both use C:\ProgramData\Cakewalk\Rapture\Programs as the program path. If they do use the same path, then they would share a common programs.lst file (the index used to create the program list in the Rapture and RaptureLE browser).
I know this is not much help, at least it does not provide a simple "there's the problem" answer. It is difficult without first hand knowledge of the package and where the plug-ins are looking for data.