Rapture - bug report and question

First, the question: I have both DimPro and Rapture. Where is the best place to put multisamples (for example Viral Outbreak) so they can be found by both? DimPro has a registry key that it looks like can be tweaked to point to another location, but I don't see one for Rapture. Can we have this please?

Second, the bug report: I put the multisamples in another directory (ie C:\Program Files\Cakewalk\Rapture\Multisamples\). I expected an errror message on this, and sure enough, a "Multisample not found" error message with an OK button popped up.

BUT, it was obscured by the "Loading" bar.



Doug

Thanks for the Regkey tip. I should have thought to try it and see what happens. Now my Rapture sounds are cohabitating with my DimPro sounds just fine.

In an ideal world, I would not have had the problem I described above (I expected it) so "next release" is a perfectly fine answer for me.

Thanks Rene!

Doug

ORIGINAL: René

If you have both DP and RP, I suggest to place any new samples inside DP Multisamples folder. My rationale is that it's cleaner to have only one of both growing, easier to backup, transport, etc.

The 'Multisamples Folder' registry entry works in Rapture as well. The installer doesn't create it, basically because Rapture factory multisample set is tiny (about 1MB), but you can create it yourself and in this way relocate Rapture multisamples folder anywhere in your system (I have it relocated *inside* DP multisamples folder myself). It's HKLM\Software\Cakewalk Music Software\Rapture\Multisamples Folder (szstring).


The 'progress bar covering MessageBox' issue in some hosts has already been fixed in DP 1.2 IIRC. The fix will surely be included in some future Rapture release.



-René

Rene,

Forgive me for butting in here, however, my question is apropos to the discussion.

Is there a switch I can change Rapture's (and Dim Pro's) behavior of recalculating the Program Browser hierarchy every time I save a new Program?

I'd much rather this timely process happen on command or maybe on program open or close. Definitely not in the middle of my workflow. Being a Windows disk-based operation, the process essentially disables any UI activity for the 20 seconds or so required to complete, and is always unpleasant and unexpected interruption to my work.

Sorry to be so negative--let me finish with the sincere remark that I simply love your envelope editors and wish all patch editing software used your model based on linear time instead of whatever arbitary scale they currently use.

Thanks.

--Kurt

Thanks Rene,

I'll keep the browser closed.