Rapture Pro doesn't find my Universal 120 expansion

I just bought the Rapture Pro upgrade on (OSX 10.9).  I was able to install and authorize it using Command Center no problem.  I accepted the default location for the two folders mentioned in Command center.  
 
/Users/Shared/Cakewalk Content/Cakewalk Sample Data/  (has multi samples, LFO's and tunings)
 
and
 
/Users/Shared/Cakewalk Content/Rapture Pro/      (has programs and everything else)
 
Rapture Pro works fine with all the standard Factory content that is included with Rapture Pro.   However my preexisting 3rd party expansions are not recognized.   For example, Universal 120 expansion, was installed previously with Rapture 1.x and is located under:
 
/Library/Audio/Plug-Ins/Rapture Content/
 
And under the old Rapture, the programs and multi samples are all contained under that one common folder, not split into two separate folders as they are in Rapture Pro.
 
I have tried to copy some of the files from the old location to the new locations, but it doesn't always work right, it seems often times the multi-samples can't be found.
 
Please advise, what is the proper procedure to get legacy expansion packs to be recognized by Rapture Pro?
 
I like that this is formally supported product finally and 64bit and I do l like some aspects of the new guy, even though its kind of "blurry" compared to the old one, its a better GUI no doubt and I like that DimPro content and Rapture content is all consolidated into one engine.  This is all nice stuff, but the fact that my expansions are not recognized is a big deal.  I may try to figure out how to install Rapture 1.x again.  Its definitely possible to do that, I had it working before on 10.9 using a 32bit bridge...the only reason I really paid to upgrade was to have a supported product and 64bit more than anything.  But if its not going to use my expansions that I paid money for, then its not of use to me.
 
Any advise for how to get Universal 120 working in here?   There is another freebie 3rd party expansion too, can't remember the name right now, but I really want that one working too.  
 

any insights you can provide, including the way it works on windows will be helpful.

That's good information, thanks for sharing.  Its possible that the installation requires Rapture 1.x to be presently installed in order to properly find, move or rename existing expansions I guess.  I did not have Rapture 1.x actually installed anymore, I just had the libraries present in the expected location where they were installed.  On OSX that kind of information is likely in the /Library/Preferences/com.cakewalk.Rapture.plist file, Assuming its still there.  So in theory, the OSX installer might have done something smart if that plist file was there ahead of time which it wasn't.
 
Universal 120 comes in a package installer and basically if I try to run that package installer it will install various related files under /Library/Audio/Plug-Ins/Rapture Content/.  So if I try to use their installer to a clean Rapture Pro installation with no traces of Rapture 1.x around..it isn't going to work.
 
Near as I can tell the installer did not copy over programs from the old place to the new place...it just installed all the new stuff and completely ignored the existing old data dir.
 
I didn't know the Universal 120 LFO waveforms were new, for some reason they are named the same as the ones that come with Rapture, so I assumed they are the same.  Sounds like they are drop in replacements for the factory LFO's?
 
I will look at this a little more tonight to see if I can figure it all out, but it sounds like manually moving my expansions is the right ticket, I just need to understand what to move where.  
 
thanks

I would guess if you manually copy the programs and samples/sfzs into the RPro paths, it should pick them up.

Chad thanks for the updated installer and thanks to both of you guys for explaining the way RPro works in terms of reading the directories.  Not too complicated I should be able to move stuff around.
 
So its fair to say that .prog files search for multisample files by the "base name" and not a full pathname, and it goes to the location specified in prefs or registry for the multi samples folder?  When things are nested inside subdirs of that folder, can the prog still find them or do the progs generally have the subdirs, when applicable, saved as part of the prog definition for each multisample?  In other words, if a multisample was located in a subdir of multi samples, will a prog expect it to be in that exact subdir, or does RPro find all multi samples under the root multi samples dir by base name in some way?  I'm guessing the sudirs matter, but just checking.

Muz3um is the only expansion I can't seem to get working.  Any suggestions about how to make that work would be appreciated.  I installed it into the old location.  Moved all the multi samples from there to the new location (they are not in a subdir in either place.  Moved all the programs.  The programs don't find the samples.
 
Anyone have any idea?

That helped a lot.  Thanks!