I have those .sfz files in my D:\Dimension Pro\Multisamples folder as well after the update. I'm pretty sure they should be in a subfolder.
 
-Susan

Okay, I just got an email from Cakewalk. The problem is that's how my programs referenced the SFZs. I was keeping the SFZs separate because I was moving the Expansion Pack between two different computers (at home/on the road) and kept the multisamples, SFZs, and programs separate to make it easier to do transfers. The SFZs should have been in a folder that also had the multisamples. As you pointed out, the way it is now does "work," but it's messy.
 
I told Cakewalk if they could provide me the locations for where things are supposed to be, I could create a new set of programs that reference the correct locations and that could be done as an update to tidy up the multisamples folders.

Thanks Craig excellent feedback, let them know about boost11 and hardgrove if possible as well (#30) - thanks...

I so wish there was only one main thread for the Cambridge release! What was wrong with the sticky? I've been ping-ponging back and forth for the past few hours trying to keep current!
 
-Susan

That's how it got installed here. So 3 at least.

Doktor Avalanche
Do you not have .sfz files like this in your installation? Two confirmed so far.
 

Doktor Avalanche
Thanks Craig excellent feedback, let them know about boost11 and hardgrove if possible as well (#30) - thanks...

If you want bullet proof relocation for Multisample folders use a directory junction. It can be added to your current installation in addition to the registry edit even though it makes the registry edit redundant. For example, I have Rapture multisamples in N:\Cakewalk\Rapture\Multisamples so I added a junction by running cmd.exe as administrator an typing:
mklink /j "C:\Program Files\Cakewalk\Rapture\Multisamples" "N:\Cakewalk\Rapture\Multisamples"
 
The installers have no choice but to put that data on N:.

Welcome to the wonderful world of software development. Even if you're just doing content, you have to be aware of how it gets installed and cooperate with current practice. Part of the job description, basically it's an exercise in Kegels and holding your mouth correctly. It's all good, we'll cut you some slack... this time. :)

Anderton

Doktor Avalanche
Craig I know you mean well, but the workaround does not work as I stated a few posts ago, and other Dimension Pro installations work perfectly well, and the samples end up in the root of the multisamples folder, I suspect this happens for """standard""" installations as well...

Well I don't know about the installation aspect, I just do the content. But this is a workaround I've used before, and I tested it with the Gold Top, so not sure why it didn't work in your case.
 
The only thing I can think of it I made a mistake in documenting the workaround. I'll check.

Doktor Avalanche
Thanks Craig excellent feedback, let them know about boost11 and hardgrove if possible as well (#30) - thanks...

scook
If you want bullet proof relocation for Multisample folders use a directory junction. It can be added to your current installation in addition to the registry edit even though it makes the registry edit redundant. For example, I have Rapture multisamples in N:\Cakewalk\Rapture\Multisamples so I added a junction by running cmd.exe as administrator an typing:
mklink /j "C:\Program Files\Cakewalk\Rapture\Multisamples" "N:\Cakewalk\Rapture\Multisamples"
 
The installers have no choice but to put that data on N:.

Let us agree to disagree. I expect as a basic requirement that all software should look at existing file path registry entries when upgrading, or install to a known data folder stored in the registry. Up until now all samples have been installing to the correct locations just fine for rapture what we have here is clearly a bug or the logic was weirdly forgotten about.

I see the uses but I have never needed to use symbolic links, I would only use them when all other options are exhausted (very useful in Linux however or for people petrified of the registry).

Craig,
Ideally what you want to do is:
Goldtop Neck/
  patch1.sfz
  patch2.sfz
  ...
  readme.txt if appropriate
  Goldtop Neck Samples/
    sample1.wav
    sample2.wav
    ...
 
 

Doktor Avalanche

Let us agree to disagree. I expect as a basic requirement that all software should look at existing file path registry entries when upgrading, or install to a known data folder stored in the registry. Up until now all samples have been installing to the correct locations just fine for rapture what we have here is clearly a bug or the logic was weirdly forgotten about.

I see the uses but I have never needed to use symbolic links, I would only use them when all other options are exhausted (very useful in Linux however or for people petrified of the registry).

I don't know what you are disagreeing with, I only provided a way to insure the samples find their way into the correct folder. Use it, don't use it, does not matter to me. It is not true that samples have always installed in the directory referenced in the registry. Rapture has had a history going back many years of ignoring registry redirection.