Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: $Revision: 1.6.2.16 $; site datacube.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!harvard!think!datacube!shep
From: shep@datacube.UUCP
Newsgroups: net.music.synth
Subject: Re: Juno 106: patch & parameter info wan
Message-ID: <22300013@datacube.UUCP>
Date: Tue, 6-Aug-85 13:02:00 EDT
Article-I.D.: datacube.22300013
Posted: Tue Aug  6 13:02:00 1985
Date-Received: Mon, 12-Aug-85 04:09:32 EDT
References: <991@mtgzz.UUCP>
Lines: 47
Nf-ID: #R:mtgzz:-99100:datacube:22300013:000:1282
Nf-From: datacube!shep    Aug  6 13:02:00 1985


If you write to Roland and ask for the "Juno-106 midi implementation"
sheet, you will get a piece of paper that tells all about the 106.
The factory presets may be dumped by sending the DUMP_PATCH sequence over
midi. The sheet clearly details the "I, II, III" midi switch function as
well. Until your sheet arrives, here is a header for juno106 defines:

/* juno106.h - all the great stuff I've figured out about the juno106.
 *	There is probably more. I'll find out, someday. shep 4/6/84
 */

/* 'third' byte field defines */
#define	CNTLCHANGE	0x32
#define	PATCHDUMP	0x30
#define	MANDUMP		0x31

/* 'fourth' byte field defines */
#define	J106NRM		0x00

struct j106patch {
	char lfo_rate;
	char lfo_delay;
	char dco_lfo;
	char dco_pwm;
	char dco_noise;
	char vcf_freq;
	char vcf_res;
	char vcf_env;
	char vcf_lfo;
	char vcf_kybd;
	char vca;
	char env_A;
	char env_D;
	char env_S;
	char env_R;
	char dco_sub;
	char modec1;
	char modec2;
	char name[80];
	char patchnum;
};

Shep Siegel                               ihnp4!datacube!shep
Datacube Inc.                  ima!inmet!mirror!datacube!shep
617-535-6644                  decvax!cca!mirror!datacube!shep
4 Dearborn Rd.       decvax!genrad!wjh12!mirror!datacube!shep
Peabody, Ma. 01960   {mit-eddie,cyb0vax}!mirror!datacube!shep