Date: Mon, 30 Mar 1998 09:51:10 -0800
From: Mike Kent <mikekent@pacificrim.net>
To: analogue@hyperreal.org
Subject: Juno-106S, HS-60, MKS-7, & Juno-106

>> i've just sold one a few months ago with the "106S" on it. Hmm...i suppose
>> it's rare huh? :)
>>

There are several variations on the Juno-106:
  Juno-106 was the first with this synth engine.
  Juno-106S, a Juno-106 with speakers.
  HS-60, also a Juno-106 with speakers.
  MKS-7BK, a multitimbral module with the same synth engine, black.
  MKS-7IV, a multitimbral module with the same synth engine, ivory.

The HS-50 and Juno-106S were the same instrument, but with differnet name
plates in different countries (depending on how the local distributor
wanted to market the synth). Their $ value now is probably not really
different from a Juno-106, but you find the speakers handy for your
particular needs if you don't mind the extra littel bit of weight.

The MKS-7 has the same synthesizer, uses the same sys.ex. for patches.
However, the MKS-7 does not have user memory locations, and as someone
pointed out in the last few days the presets generally suck. So ideally you
would want to store your own patches you are using within your sequence. A
Juno-106 makes a perfect programmer for the MKS-7, but MKS-7 should respond
to any Juno-106 editing software. If you like the sound of a Juno-106, the
MKS-7 is a lower budget way to get several Juno-106 sounds going at one
time.

Regards,
Mike.


 _________________________________===========___............................
 |                                  JUPITER-8  |PERSONAL:  .................
 |Roland ======================================|mikekent@pacificrim.net  ...
 | oo|-.||o||-|-|oo--oooo.|.||-|-|||.||||.||||.|HOME PAGE:  ................
 |---------------------------------------------|www.pacificrim.net/~mikekent
 | o oooo oooo ooo oo [8888] oooooooo oooooooo |............................
 |...xx o ___________________________________  |BUSINESS  ..................
 |||| == |UU|UUU|UU|UUU|UU|UUU|UU|UUU|UU|UUU|| |mikekent@compuserve.com  ...
 |_______|||||||||||||||||||||||||||||||||||||_|............................