Anderton MiniMoog Rapture Expansion Pack: Any of you guys own it? Thoughts?

Not sure but I think I may be able to snag this while it's on sale. It was recommended to me ages ago because I do like that old squirrely analog synth bass sound.
 
Certainly a decent price if it delivers (I'm sure it does since it's Craig). Just wanted to what the owners of this pack think. There aren't any sound examples on the store page.
 
Got about a week I think before the special's over so yanno... not a rush.
 
Cheers.

Anderton
Well, to call the Minimoog Expansion Pack the greatest achievement in the history of Western civilization would be an understatement. 

 

First off, thanks to the host(s) who managed to track down and restore this thread. Not sure what happened there and of course not an emergency thread but the effort is appreciated.
 
@Paul... nope, haven't gotten around to picking it up but I think I've got a few bucks scraggling in my PP that I think should just cover this. Thanks for bringing up the LFO thing. Not sure exactly what the deal is on that (I'll check those threads) but if they round out the MM emulation I'm guessing I'll want them. Also you answered answered something else I was wondering about... the odd picture in the store. Wasn't sure was going on there and was making me wonder exactly what it's relation to the Guitars pack was. Apparently none so confusion begone. Cheers!
 
@Craig... Cool. The guitars one does sound cool too and looks pretty diverse but I have been aching for a true MM sound for a long time. Zeta gets me close but it just doesn't have the same "warmth" I find... if that makes sense. I notice that your example tune doesn't include the exact sound I'm really jonesing for (that really round, warm, funky porta bass sound) but if the pack includes all the appropriate waveforms and controls to emu an MM I'm guessing that sound is possible. I'm also sure that's not something you'd overlook either. The example does seem to show off how it can produce some modern sounding tones too so that's a good flexibility to have. Thanks and if I get it I'll definitely hit you up at some point for those LFO's. Cheeers!
 
@Sidroe... Thanks for the review. I trust your opinion on this (and all things to do with "real" sounding emus based on other review type posts you've made that definitely jibe with my own experiences with specific items). Very helpful and actually is making me think it's better than I initially expected. Awesome.
 
Alright, dudes. I'm sold. I just gotta make sure I'm not short something stupid like 50 cents or something... but I'd figure that out.
 
Thanks all.

Dan_E10
It sounds like a no-brainer if it's on sale for $10.  One thing to be aware of, if you are using it in Rapture Pro, at least one of the patches may sound a bit off.  I noticed that news_arpeggiator, one of my favorites from the pack, sounded strange in Rapture Pro after hearing it in Rapture.  It turned out that patch uses a blank LFO with the LFO on.  It doesn't have an effect in Rapture since the slot is empty.  However, in Rapture Pro that LFO slot is populated which makes the patch sound strange.  No problem to just disable the LFO, but if I hadn't heard it in Rapture first I would have thought the patch was meant to sound like that.
Dan

I of course cannot be certain but that sounds related to the missing LFO issue discussed earlier (but you may already be aware of that). I still need to research that more to see what the deal is but I actually am now a proud owner of the pack (I had JUST enough to make the buy... it was meant to be, lol).
 
Currently wrangling with some interface driver/firmware spazziness (I figured I'd hunt down any new releases for my 18i6 but am finding some not so nice reports about them so I'm a litttle verklemmt about it all).
 
Anyhoo... I have them now so expect a PM asking for those LFO's, Craig and I'll try to report back after I get to play around with it all.
 
Cheeeers!

Wait... so does this missing LFO thing only apply to Rapture Pro? I only have the Rapture that comes with Sonar.
 
Mayhaps I don't gotta worry my (un)pretty little head over it?
 
Either way... awesome you're looking out for us on that, Craig.
 
Cheers.

Cripes, I'm an idiot. The links Paul provided go to the old thread I myself posted (where this pack was recommended to me).
 
Still don't understand the issue (the LFOs for the pack don't get installed because Rapture has the LFO slots filled already? hrrrm... all Greek). Craig has a download link in that thread too (second link Paul posted). Haven't clicked to see if it's still active.
 
Have about a million things on my mind lately so yanno. I actually was looking at these a week or so ago and am just getting around to dealing with it (due to the million other things) so you'll have to forgive my derpiness.
 
The biggest question I guess... once the LFOs are available (if they aren't already) is where I put them. Sounds like a manual operation (like the weirdness I had to do with the freebie Gibson EB5 ones... the paid version installed fine with no fiddling AFAICT BTW).
 
Those answers are perhaps in that thread too. I'll look through it.

Alright... so I guess I need to understand this logically/mathematically. I can only work on assumption based on the factors provided so far.
 
This is 4 specific files that need to go into a specific spot in the Rapture preset area?
 
That area is LFO slots 30 to 33? (So 30=LFO1, 31=LFO2, 32=LFO3, 33=LFO4).
 
If this is correct... what normally exists in those 4 slots? User LFOs from user created presets? Factory defualt Rapture presets?
 
I don't believe I have ever created any Rapture presets. I've actually barely used Rapture on my system aside from just pecking at it a bit to check it out.
 
So if those are set aside for User Presets I should be fine.
 
That would bring me to whether, under those conditions (being someone who has never created a Rapture preset) whether the MM package actually COMES with those LFOs and whether the exe will drop them into those slots naturally (if they are available... which they should be on my system).
 
I am probably TOTALLY misunderstanding the issue (grasping at straws really because I have no idea how Rapture stores this type of info nor where) but maybe it'll knock loose some answers.
 
And I guess another important question is exactly WHICH patches are affected by this problem so I can do a proper test. I really would have no clue whether a MiniMoog sound was borked or not because I've never owned one or handled the banks yet (so no reference point).
 
Just trying to get my head wrapped around it all before I install. Sorry... I suxxorz at synth/VSTi/preset management stuff at this level. Trying to learn though.
 
Cheers.

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?

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.

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.

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

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.