Archive of the former Yahoo!Groups mailing list: All about the Roland Jupiter-series

previous by date index next by date
previous in topic topic list next in topic

Subject: FW: [AH] MKS-80 w/PC-1600x ??

From: "Verschut, Ricardo" <ricardo.verschut@...>
Date: 2001-01-11

-----Original Message-----
From: Rob [mailto:cyborgzero@...]
Sent: Thursday, January 11, 2001 12:04 AM
To: analogue heaven
Subject: Re: [AH] MKS-80 w/PC-1600x ??

Er, no, bit/word delay is ∗NOT∗ the same as just "moving the slider slower".
Nice try though! ;))

Okay, what you have here sounds like either

1) You need to set the parameters to generate checksum (CS in your string)
OR 2) You need to set a proper offset and/or range for the parameter.

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.

----- Original Message -----
From: "N. Kent" <ndkent@...>
To: "analogue heaven" <analogue@...>; <media@...>
Sent: Wednesday, January 10, 2001 4:16 PM
Subject: Re: [AH] MKS-80 w/PC-1600x ??

> > 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 was one would seem kind of counterproductive for any kind of live
> tweaking, would it not. Sending one single parameter sysex string, even
> very quickly shouldn't choke anything. Sure you could space the 7 or
> whatever number of bytes the MKS uses out via a delay if there is one,
> but thats probably not the problem.