-----Original Message-----
From: N. Kent [mailto:
ndkent@...]
Sent: Thursday, January 11, 2001 5:08 AM
To:
analogue@...Subject: Re: [AH] MKS-80 w/PC-1600x ??
> On Wed, 10 Jan 2001, N. Kent wrote:
>
> > > Sounds like the 1600 is pushing stuff out too quick for the MKS to
> > > deal with it. If the 1600 has a delay parameter, try tweaking that.
> >
> > I don't believe it has a delay but I may be wrong, also just moving the
> > slider slower should achieve somthing like that. A delay parameter, if
>
> there ∗is∗ a delay parameter on there somewhere, but i can't recall where
> at the moment (the manual is downloadable from www.peavey.com if you don't
> have it).
I think someone would have encountered the problem by now since its a
reasonably popular combo. And as I said, while not impossible, its
unlikely its going to choke on a slowly moving slider, its not a whole
dump of a patch bank, a single slider shouldn't be choking it unless you
go crazy and adding delay I doubt is the answer. But who knows, the
person in question has a 1600x, I have a 1600
however, the problem might be that the pc1600 is sending 127
> increments to the mks instead of the 100 it wants. you can edit the max
> and min values per fader, so setting the max to 100 (and the min to 0 or
> 1, whatever the mks wants) should work...
>
> hope that helps!
>
> bleep.
> out.
Not quite, I've done that plenty of times by accident while programming
all the other parameters . If you slide past 100 to say 120 the MKS just
stays at 100, it doesn't loop around or bug out... but the advice of
checking out the range on any parameter that doesn't work is well worth
checking out, who knows maybe somehow it got set to 0-7 instead of 0-100.
> Er, no, bit/word delay is ∗NOT∗ the same as just "moving the slider
slower".
> Nice try though! ;))
no I did not say it was the same, I said "something like" because in
this case with about 7 bytes or whatever a strings length, is the
chances of just one of those coming out and making the unit malfunction
seems unlikely. Sorry if you misintrerpreted me but I was mentioning
that as almost proof that it wasn't an issue of spacing the MIDI stream.
(while of course it might if many sliders are moving at once and
certainly for bulk dumps that don't work out)
>1) You need to set the parameters to generate checksum (CS in your string)
Huh?? The MKS-80 doesn't utilize checksum for SYSEX control of
parameters. Say you generate it then what are you going use it for???
Throwing in extra bytes is a sure fire way to not get SYSEX to work.
> 2) You need to set a proper offset and/or range for the parameter.
there is no offset on MKS parameters. We've mentioned the range which we
all think is good advice to check out
> This comes down to really going over the values in the sysex
implementation
> and checking to see if what happens is what is "supposed" to happen.. I
had
> some parameters in the same piece of gear that require checksum, require
> offset, range or all three!! And the sysex chart doesn't neccesarily give
> you all the info you need all the time.. Some sysex charts are missing
info.
mmmm... you are guessing here much more than I am. The Sysex on the MKS
80 is very straight forward, no checksums and Peavy does give a sample
bank of about a third of the MKS-80 parameters when you buy the unit.
(Unless this changed for the 1600x) Its somewhat time consuming but
pretty troublefree to flesh out all of the others from the ones you get,
you don't necessarily need charts, nothing tricky is going on on
Roland's side of things. As mentioned, I did it and everything worked
you just need a plan for what slider you want doing what ans some
patience.
nick kent
(not the person with the PC-1600x problem)