50th anniversary edition is shipping to me today!!!!
50th anniversary edition is shipping to me today!!!!
Hi, never owned a Moog and have spent only a few short minutes tinkering on one in a music shop a few years ago. Finally I decided to bite the bullet and pick one up. I put a small payment down months ago, ran short of cash for a while and now have paid the remaining balance and so it ships today.
My questions, as a noob user of the Moog what kind of tips can anyone offer? Right now I am stuck with two little BX5 monitors. Is that enough to get started? If not what can you recommend for home studio use? Any good web sites out there that are worth using as reference material? Any general thoughts and so forth are appreciated.
My questions, as a noob user of the Moog what kind of tips can anyone offer? Right now I am stuck with two little BX5 monitors. Is that enough to get started? If not what can you recommend for home studio use? Any good web sites out there that are worth using as reference material? Any general thoughts and so forth are appreciated.
I’m pretty much in the same boat. New to analog synths (and synths in general). I picked up an AE last month and am starting to get the hang of it…already making insane new patches! These units are fairly intuitive. Can't imagine you not having a blast right out of the box.
I’ve found just messing around with knobs and listening to the results is the best way to learn (first use the edit menu to reset all controls to default positions so you can tell what each knob is doing). I’ve also read the manual about five times to get a technical understand of *why* when I turn knob “x”, sound “y” occurs. And the more you learn the more new ideas pop into your head to explore and etc, etc. Possibilities are near endless.
For monitoring I use a pair of AKG headphones and some Genelec monitors w/ sub. Moogs put out some insane low frequency content so something that can reproduce under 50hz is a good thing.
Have fun!
-solar
I’ve found just messing around with knobs and listening to the results is the best way to learn (first use the edit menu to reset all controls to default positions so you can tell what each knob is doing). I’ve also read the manual about five times to get a technical understand of *why* when I turn knob “x”, sound “y” occurs. And the more you learn the more new ideas pop into your head to explore and etc, etc. Possibilities are near endless.
For monitoring I use a pair of AKG headphones and some Genelec monitors w/ sub. Moogs put out some insane low frequency content so something that can reproduce under 50hz is a good thing.
Have fun!
-solar
Ticker -
Go to your local bookstore (or Amazon.com) and pick up a copy of "Power Tools for Synthesizer Programming" by Jim Aikin. The book was just published this year so it's up-to-date. It includes a CD-ROM that provides audio examples of all manner of synth basics and programming, and would be an excellent reference text for a synth novice like yourself. Highly recommended.
Oh, and congrats on the new Moog! I've had my MMV Performer for a year now and couldn't be happier!
Cheers!
Greg
Go to your local bookstore (or Amazon.com) and pick up a copy of "Power Tools for Synthesizer Programming" by Jim Aikin. The book was just published this year so it's up-to-date. It includes a CD-ROM that provides audio examples of all manner of synth basics and programming, and would be an excellent reference text for a synth novice like yourself. Highly recommended.
Oh, and congrats on the new Moog! I've had my MMV Performer for a year now and couldn't be happier!
Cheers!
Greg
A good way to work with patches is to set up your own default initialize patch setting. I didn't like the default one stored in ROM. For example, reserve 121-127 for your patch creation/progress. 120 is your default (starting patch) which doesn't get overwritten (unless you need more space to save patches in which you would fill up the bank, back-up and start fresh again).
I found this best because sometimes you'll discover a previous patch you did was better, if you keep overwriting then you'll have to remember all the steps you took before. And with the default int. patch, I usually like to disable the T.S. This forces you to think creatively in programming it's use and assign controls. Just some thoughts on how I work
I found this best because sometimes you'll discover a previous patch you did was better, if you keep overwriting then you'll have to remember all the steps you took before. And with the default int. patch, I usually like to disable the T.S. This forces you to think creatively in programming it's use and assign controls. Just some thoughts on how I work

-
- Posts: 275
- Joined: Wed Feb 11, 2004 5:22 pm
- Location: Kent, UK
- Contact: