MOTM

I am a newbie to this group and still awaiting the delivery of my 
first batch of MOTMs.  Have never owned a modular synth so I am 
contemplating some of the gotchas in advance.

After discovering a number of sounds that one likes, how are the 
patches usually documented?  It is one thing to draw a CAD picture of 
your synth and then draw lines for knob settings and patch cord 
connections.  But it is quite another to "document" what manner of 
sound was created.  It would seem that in short order, hundreds of 
worthwhile patches would be identified.  Looking over past posts I 
was amused by some of the sound descriptions that were invented.  The 
trouble is, I might know what a "splufferoscitor" sounds like but 
nobody else will.  And six months later, I won't remember what it 
sounded like, either.

I'd be grateful to hear from all who have devised a workable approach!

Many thanks in advance.

Tom Farrand

I bought a copy of VISIO which allows custom templetes to be used. You can
easily draw
MOTM panels, save as a templete, then "darg and drop" a patch sheet.

Paul S.

----- Original Message -----

From: <mbedtom@...>
To: <motm@egroups.com>
Sent: Sunday, December 03, 2000 3:58 AM
Subject: [motm] Patch Documentation Query


> I am a newbie to this group and still awaiting the delivery of my
> first batch of MOTMs.  Have never owned a modular synth so I am
> contemplating some of the gotchas in advance.
>
> After discovering a number of sounds that one likes, how are the
> patches usually documented?  It is one thing to draw a CAD picture of
> your synth and then draw lines for knob settings and patch cord
> connections.  But it is quite another to "document" what manner of
> sound was created.  It would seem that in short order, hundreds of
> worthwhile patches would be identified.  Looking over past posts I
> was amused by some of the sound descriptions that were invented.  The
> trouble is, I might know what a "splufferoscitor" sounds like but
> nobody else will.  And six months later, I won't remember what it
> sounded like, either.
>
> I'd be grateful to hear from all who have devised a workable approach!
>
> Many thanks in advance.
>
> Tom Farrand
>
>
>
>
>
>

You can always do what recording studios did before automation, and take 
Polaroid (or digital) photos of your front panels.  Crude, but it works.

Ivan

You know, that is a pretty good idea.  And, my digital camera lets you
attach a sound clip to the photo too.  That might be fun.
Larry H

----- Original Message -----
From: <ivancu@...>
To: <motm@egroups.com>
Sent: Sunday, December 03, 2000 10:48 AM
Subject: Re: [motm] Patch Documentation Query


You can always do what recording studios did before automation, and take
Polaroid (or digital) photos of your front panels.  Crude, but it works.

Ivan

Something I did was go to the synthtech website, copied the jpegs of 
the modules, and pasted them into Microsuck Publisher (although any 
image editing program will work. I resized each pic so that they all 
came out to the same size, and laid them out exactly as I have them 
on my rack. As a final touch, I recolored all the modules as a medium 
grey color. This allowed me to take multiple colored markers to the 
paper after I print out the sheets, so I can whip one out easily.

BTW: Recently lost my job and was in a severe rut for a while. I had 
been so into work previous to this that I hadn't even touched my 
system in about two months. I sat down yesterday, and went at it.... 
MAN! did it relieve some tension! I had so many ideas for new sounds 
(amazing considering the few modules I have), I started budgeting to 
get a new oscillator. It's up next after I figure out how to fix the 
rent-money problem ;p

THANKS PAUL!!!!!!!!!!

--- In motm@egroups.com, "Paul Schreiber" <synth1@a...> wrote:
> I bought a copy of VISIO which allows custom templetes to be used. 
You can

> easily draw
> MOTM panels, save as a templete, then "darg and drop" a patch sheet.
> 
> Paul S.