• Cakewalk Instruments
  • Can't seem to get Rapture Pro to install Multisamples where I want (already had) them.
2016/01/03 16:51:06
bamim2
I'm not sure what I'm doing wrong or not doing correctly, but I can NOT get the Rapture Pro Mulitisamples to install where the WERE installing. I have the "Cakewalk Content" folder defined in Sonar Platinum as "E:\Cakewalk Content" & the Multisamples were going to E:\Cakewalk Content\Cakewalk Sample Data\Rapture Pro\Multisamples". THAT was GREAT. Somehow (I'm guessing there was a loose nut behind the mouse ), I must have rushed through an update & used the default, because now they go to: "C:\Cakewalk Content\Cakewalk Sample Data\Rapture Pro\Multisamples". No matter what I do, that's where they go. I've tried looking through the registry for "Rapture Pro" & I can't figure out where the settings are.
 
Would somebody PLEASE be kind enough to list what I need to do to get Rapture Pro Multisamples to install to "E:\Cakewalk Content\Cakewalk Sample Data\Rapture Pro\Multisamples" & for Rapture Pro to actually LOOK there for them?
 
I've had a problem with this ever since the first installation with Command Center. I HAD it "fixed" so it would install where I waned, but I have NEVER been able to even use RP because only some of the presets will work (I'm guessing because it looked for samples in the wrong place). I'm stumped. Even if I have to uninstall Rapture Pro & reinstall it, THAT is much better than never being able to use the Synth. I hear it's nice this time of year....
 
THANK YOU for any assistance I can get here. OR is this one of those things I should open a ticket & get Support assistance?
 
 
2016/01/03 17:16:52
scook
RPro looks at
SampleDataDir
in
HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software
for the path to the "Rapture Pro" folder which contains the "LFO Waveforms", Multisamples and Tunings folders.
2016/01/03 18:14:51
abb
Hi scook,
 
Would you happen to know where Rapture Session looks for its data?
 
Like the OP, I wanted to keep the (large) sound data off my (relatively small) system SSD; but the installer does not allow you to specify a path.  I contacted Cakewalk support and they confirmed this was a problem but (as usual) I never heard back from them.
2016/01/03 18:18:39
scook
Rapture Session uses a subset of RPro and shares the same folders under the "Rapture Pro"  folder in the path set in SampleDataDir.
2016/01/03 18:23:32
abb
Thanks!
2016/01/03 18:37:59
Sheanes
hi, hope this helps...if not sorry I don't get it..
copy the Rapture folder and all it's subfolders to the destination you want, then add this new location to the VST san path (task bar, edit, preferences, file, VST settings, VST scan path).
Then rescan existing plugins, scan...
It then Rapture works ok, you could delete the Rapture stuff on C drive.
2016/01/03 18:44:43
abb
Sheanes
hi, hope this helps...if not sorry I don't get it..
copy the Rapture folder and all it's subfolders to the destination you want, then add this new location to the VST san path (task bar, edit, preferences, file, VST settings, VST scan path).
Then rescan existing plugins, scan...
It then Rapture works ok, you could delete the Rapture stuff on C drive.


Thank you for helping out...but my problem was solved by changing the registry path as described above by scook. 
 
What a great forum...


2016/01/04 06:51:47
ChristopherM
FYI, I noticed that my Rapture Pro install [2.0] had created several registry keys that all seemed to need to be altered to point to my shared multisamples folder. They are Dim Multisamples Path; Rap Multisamples Path and CSC Multisamples Path. FWIW, I don't have a registry key named SampleDataDir.
 
Rapture Session [2.0] has its own instances of these same keys, implying that they need to be set the same to share with Rap Pro (or set differently if for some unfathomable reason, you wish to have independent sample sets).
 
I also noticed that somewhere along the line, an earlier Rapture Pro installer had hoovered up all of my existing Rapture and Dim Pro samples and moved them into a new subfolder, named Rapture Pro, in the previous shared folder. Helpfully, it had amended the registry keys in rp and dp accordingly, so I didn't need to do anything here.
2016/01/04 12:13:30
scook
ChristopherM
FYI, I noticed that my Rapture Pro install [2.0] had created several registry keys that all seemed to need to be altered to point to my shared multisamples folder. They are Dim Multisamples Path; Rap Multisamples Path and CSC Multisamples Path.

These are set during RPro/ RSess installation by reading existing registry entries for the legacy synths.
 
ChristopherM
FWIW, I don't have a registry key named SampleDataDir.

Pretty sure it is required for RPro to work correctly. It is in
HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software
not
HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Rapture Pro\2.0

 
ChristopherM
Rapture Session [2.0] has its own instances of these same keys, implying that they need to be set the same to share with Rap Pro (or set differently if for some unfathomable reason, you wish to have independent sample sets).
 

The entries are not identical in RPro and RSes registry.
 
ChristopherM
I also noticed that somewhere along the line, an earlier Rapture Pro installer had hoovered up all of my existing Rapture and Dim Pro samples and moved them into a new subfolder, named Rapture Pro, in the previous shared folder. Helpfully, it had amended the registry keys in rp and dp accordingly, so I didn't need to do anything here.

The RPro and RSes installers do not copy or move multisamples from legacy locations. They do copy programs into legacy folders in the RPro/RSes program area. A full installation of RPro also installs legacy DPro and Rapture samples in the RPro multisample area with one subtle difference. Some of the legacy Rapture samples in the RPro multisamples folder are converted to flac files.
2016/01/04 12:17:51
pwalpwal
cake really should move away from these bonkers registry settings and use something simpler and more reliable, like subfolder or ini file... there's no reason to use the registry for these things, and best practice coding actually says to avoid such (is that a feature request?)
 
12
© 2024 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account