Anderton
scook probably has a better way to do this, but...
 
1. Search on lfowaveform030 and then open the file location. This is where the LFOs live.
2. Download the waveforms from the link I'll be posting in this thread at some point in the very near future.
3. Now you have three options.

• Option 1: If like me you use the MM and EG expansion packs more than anything else, you don't care whoever else hijacked lfowaveform030-033 for their own nefarious purposes. So just replace them with mine.
• Option 2: Rename the existing lfowaveform030-033 to something Rapture won't recognize, like ufowaveform030-033. Then drag mine over.
• Option 3: Create a copy of the LFO waveforms folder. Have one with my LFO waveforms, the other with whatever waveforms you have in there. Rename the folder you want to use to the correct name (LFO Waveforms) and rename the other one to some bogus name, like UFO Waveforms. Rapture will recognize the one with the correct name.

4. Scratch your head, and wonder why LFO Waveforms aren't stored with patches. This won't actually solve anything, unless the place where you scratch your head itched, but it might make you feel better.
5. Enjoy the patches as they were intended to be heard.
 

does rapture pro improve on the handling of this?

http://forum.cakewalk.com/FindPost/3287877

Hi, guys. Sorry... I had "lofty" meatworld plans this morning so I didn't reply (and of course those plans, which were only getting some damned laundry done, failed due to feeling like complete garbage... more so than usual... I am not a well man). I've been watching and reading though.
 
@craig... Thank you very much for taking the time to post those and type up the manual install instructions. I will default to those concepts until I can figure out what Mr. scook is suggesting.
 
From this I am gleaning that no matter what I'm going to have sacrifice some LFOs in the default Rapture install which may (or may not) affect default Rapture patches. BUT if I encounter those patches or want to call up those default LFOs for a custom preset IF I create a copy of those files, rename them so they are not seen by Rapture then I can just revert back by swapping the names of the files back and forth as needed.
 
I pretty much just repeated what you said except in dumblefart Beepsterese but just trying to clarify it in my own head and hopefully in reality.
 
Sooooo that begs the question, does anyone know exactly WHICH default Rapture patches use the 30-33 slot LFO files? I'm guessing you (Craig) attempted to use the least intrusive LFO slots to the default package (or perhaps it was a surprise quirk only discovered later... matters not). Just wondering how destructive it will be to the default patches is all. When creating custom patches and calling up those LFO slots I'm pretty sure I'm going to rememember those numbers now (or remember the issue and just google this thread to reconfirm).
 
Heck... maybe those MM LFOs will make the Rapture patches sound better anyway. lulz...
 
I do kind of like what I THINK scook is suggesting some way to maybe circumnavigate the issue with some file path trickery so everything is available to the synth (which might allow for a/b comparisons of what's doing what to what) but really I think the "copy and rename the whole default folder" is likely the safest/easiest to understand method without losing the original Rapture library (or at least that tiny section of it).
 
That way if I suspect something is wrong in Rapture I just flip flop the names of the LFO folders and check it out... but more importantly I have a backup of the default folder just in case I want to switch back.
 
I would personally just add "OG Rapt" or some such to indicate it's the "original" (OG) folder. I cannot imagine that folder is very large but I guess I'll find out once I start poking around.
 
@scook... I'm a little too stupid to understand all that but thanks for tossing it out there. I'll try to figure it out. I of course am using 64bit whenever it's available so I don't have to worry about that I don't think unless there's some kind of weird crossover that occurs in the Rapture libraries.
 
Cheers.

The standard Rapture installation uses slots 20 through 26 and 99. The files Craig use slots 30 through 33 so there is no issue adding the Minimoog LFOs to a fresh Rapture install. I would still suggest copying the original "LFO Waveforms" directory to something like "LFO Waveforms - original." Then you will have a copy of the original directory should you ever want to compare to the working directory. The files in the "LFO Waveforms" directory are very small so multiple copies of the directory will not take up much space.

scook
The standard Rapture installation uses slots 20 through 26 and 99. The files Craig use slots 30 through 33 so there is no issue adding the Minimoog LFOs to a fresh Rapture install. I would still suggest copying the original "LFO Waveforms" directory to something like "LFO Waveforms - original." Then you will have a copy of the original directory should you ever want to compare to the working directory. The files in the "LFO Waveforms" directory are very small so multiple copies of the directory will not take up much space.

AHA!! Brilliant. So the assumption I made earlier that if I had
a) not populated those slots myself with custom LFOs nor
b) installed other patchbanks/expansion packs that may make use of those slots installing THESE (minimoog) patches...
 
...would not replace anything was correct?
 
In other words on a fresh installation of Rapture LFO slots 30-33 are not populated and installing the MiniMoog patch LFOs provided by Craig disrupts/removes/replaces nothing?
 
I will still of course make a backup of the folder just in case. I do not recall installing any extra Rapture stuff but maybe because it was a Sonar installation (actually multiple Sonar Producer/Platinum installations dating back to X1 Production Suite) that maybe those versions of Sonar came with Rapture packs that DO occupy those slots... but I don't recall that ever being the case.
 
And I guess that leads to the question(s), have versions of Sonar during that time period (or ever) shipped with Rapture expansion packs that a clean install of Rapture (on its own) would not?
 
Have we received random freebies from things like the X2 Content club for Rapture I may have inadvertantly installed (that was a chaotic and derpy period for me as you may recall)?
 
I have a pretty solid understanding of this now and lots of great plans so I'm not twisted up about it at all but it might be good to document the answers for anyone looking for this info. It is a tad brain bending for anyone not familiar with this stuff.
 
Heck... I only learned what an LFO, in relation to synthesis, was a short time ago. lulz... ir dum
 
Thanks for all the help and info everyone.
 
Cheers.

Beepster
 
AHA!! Brilliant. So the assumption I made earlier that if I had
a) not populated those slots myself with custom LFOs nor
b) installed other patchbanks/expansion packs that may make use of those slots installing THESE (minimoog) patches...
 
...would not replace anything was correct?

Yes, the slots would be empty
 

Beepster 
In other words on a fresh installation of Rapture LFO slots 30-33 are not populated and installing the MiniMoog patch LFOs provided by Craig disrupts/removes/replaces nothing?

yes, the original installation does not use slots 30-33
 

Beepster
I will still of course make a backup of the folder just in case. I do not recall installing any extra Rapture stuff but maybe because it was a Sonar installation (actually multiple Sonar Producer/Platinum installations dating back to X1 Production Suite) that maybe those versions of Sonar came with Rapture packs that DO occupy those slots... but I don't recall that ever being the case.
 

it would be a good idea
 

Beepster
And I guess that leads to the question(s), have versions of Sonar during that time period (or ever) shipped with Rapture expansion packs that a clean install of Rapture (on its own) would not?
 
Have we received random freebies from things like the X2 Content club for Rapture I may have inadvertantly installed (that was a chaotic and derpy period for me as you may recall)?
 

To my knowledge all of this stuff relied on the default LFO files. There were no additions to the LFO Waveforms directory made by either of the expansion packs or free content supplied by Cakewalk. It is easy to verify though; look in the LFO Waveforms directory.
 
 
 
 

Thank you, Mr. scook.
 
With that last post you've certainly pounded out any lingering questions I had and I think that should pretty much round out the thread for anyone looking for info on this in the future.
 
Enormously useful thread, guys.
 
Thanks a bunch.
 
Now I just gotta actually install and play around with my new toy. Looking forward to it.
 
:-D

scook is right, I chose those slots because they didn't interfere with any of the existing libraries at the time. It's the expansion packs from third parties that went nuts in adding a zillion LFOs.
 
I presume the reasons the LFOs aren't included in the patch is because they're actual WAV files - you can bring them into SONAR and if you zoom in far enough, you'll see the waveform. 

Anderton
scook is right, I chose those slots because they didn't interfere with any of the existing libraries at the time. It's the expansion packs from third parties that went nuts in adding a zillion LFOs.

 
Guilty as charged.

Anderton
I presume the reasons the LFOs aren't included in the patch is because they're actual WAV files - you can bring them into SONAR and if you zoom in far enough, you'll see the waveform.

 
And, by extension, any user-defined LFO (2999 samples & under) can be loaded as a Multisample 'oscillator'.
With proper renaming, any of the shipping Rapture Multisamples (excluding *.sfz) can be loaded as a user-defined LFO.
 
Just to add a little fuel to the fire here.

Anderton
I presume the reasons the LFOs aren't included in the patch is because they're actual WAV files - you can bring them into SONAR and if you zoom in far enough, you'll see the waveform. 

But they should be included in the download, or one is not getting what is paid for.
 
The download is now an installer Craig_Anderton_Minimoog_Tribute.001.exe whereas it used to be a zip file Craig_Anderton_Minimoog_Tribute_(Win).zip (a bunch of stuff plus the RaptureExpansionInstaller.exe installer).  Obviously someone touched this product to bring about that change.
 
Does anyonel know if the LFO issue was fixed with the new installer ?