hi cj,

the clock inputs that are tied together are simply receiving the same
clock signal. if you disconnect each and every one, you have an input
for each sound. well, for each pair of sounds (rim/cow, etc). cutting
traces would be the most structurally safe way to do it, the problem
is that some pins connect to traces that go underneath ic30. i've
been fantasizing about a piece of abrasive dental floss i could run
underneath the pins to cut through these traces. unfortunately, that
would disconnect the pins on that side that are not clock inputs as
well (if they also have traces that go underneath). i think what i
may have to do is sacrifice my non-working 707 and just rip ic30 off
of it to see what's going on under there.

i have a set of printed schematics i could try to scan. i think they
are photocopies, so they're probably better than the zipped ones, but
not much. i'll try to remember to bring them to work on monday.

greg

--- In tr-707@yahoogroups.com , "acousmatique" <acousmatique@y...>
wrote:

> Does this really yield a different clock for each drum sound

Looking at IC30

> on my 707, pins: 56+57, 59+60+61, 63+64 are all connected to each

other. If

> we include the lone pin 62, this would result in four clocks to

play with. I was

> hoping I could just gently lift those pins off of the PCB and use

the pads for

> new clock signal, but it seems that that won't work. Better to cut

the traces, but

> I am going to follow to see where they go first.
> Also, I am trying to devise a more versatile oscillator for this

mod.

> CJ