my Yamaha MU100R suddenly ignores part Coarse Tuning

[Kevin]

I must be missing something simple, but it has me baffled: suddenly
sending my Yamaha 100r (in XG mode):

cc101 = 0
cc100 = 2
cc6 = 76

doesn't change that part's tuning up an octave like it used to.
There's no effect on the tuning of the part.

I'm sending XG reset sysex at the start, all my setup data is spaced
out sufficiently, but no effect. (All the other setup data before and
after is obeyed just fine.)

I usually use a MOTU MIDI Express interface, which could do some
filtering, but I get the same result when going through a simple Fastlane
interface, which does not filtering. I'm using Digital Performer 3.11,
and this should be very routine, but suddenly doesn't change the part key.

The instrument icon on the display flashes "Ex" in the lower right
corner of the icon as that Coarse Tuning data is received, but I see
no explanation of that in either the MU100r or MU50 manuals.

Has somebody seen this before?

Thanks in advance,

Kevin

[Peter]

On 19 Aug 2003 13:04:40 -0700, kevin@lumiere.net (Kevin) wrote:

>I must be missing something simple, but it has me baffled: suddenly
>sending my Yamaha 100r (in XG mode):
>
>cc101 = 0
>cc100 = 2
>cc6 = 76
>
>doesn't change that part's tuning up an octave like it used to.
>There's no effect on the tuning of the part.
>
>I'm sending XG reset sysex at the start, all my setup data is spaced
>out sufficiently, but no effect. (All the other setup data before and
>after is obeyed just fine.)
>
>I usually use a MOTU MIDI Express interface, which could do some
>filtering, but I get the same result when going through a simple Fastlane
>interface, which does not filtering. I'm using Digital Performer 3.11,
>and this should be very routine, but suddenly doesn't change the part key.
>
>The instrument icon on the display flashes "Ex" in the lower right
>corner of the icon as that Coarse Tuning data is received, but I see
>no explanation of that in either the MU100r or MU50 manuals.
>
>Has somebody seen this before?
>
>Thanks in advance,
>
>Kevin

Are you sending them in that order cc 101 first, cc 100 and cc 6 last.
Peter

[Kevin]

Peter <nomail@nowhere.com> wrote in message news:<8f15kv09n38uh3lkgrb9okmrnik3m5mvi5@4ax.com>...
> Are you sending them in that order cc 101 first, cc 100 and cc 6 last.
> Peter

Thanks for your interest.

Yes, in fact I am always careful to send the setup data in series.
I've even tried separating them further apart time-wise, and tried
slowing down the tempo of the setup bars to about 30 bpm in case it
was overload. Clearly not.

Can anyone confirm that the correct sequence to raise a part one
octave is in fact the following?

cc101 = 0
cc100 = 2
cc6 = 76

Tonight I tried initializing the MU100R (which I should have tried
earlier) but that did not help.

I tried using my XGedit Mac, but it will only send SYSEX for key
change.

Thanks,

Kevin

[Peter]

On 19 Aug 2003 21:04:24 -0700, kevin@lumiere.net (Kevin) wrote:


>Thanks for your interest.
>
>Yes, in fact I am always careful to send the setup data in series.
>I've even tried separating them further apart time-wise, and tried
>slowing down the tempo of the setup bars to about 30 bpm in case it
>was overload. Clearly not.
>
>Can anyone confirm that the correct sequence to raise a part one
>octave is in fact the following?
>
>cc101 = 0
>cc100 = 2
>cc6 = 76
>
>Tonight I tried initializing the MU100R (which I should have tried
>earlier) but that did not help.
>
>I tried using my XGedit Mac, but it will only send SYSEX for key
>change.
>
>Thanks,
>
>Kevin

Ihave a MU90R and it`s the right seqence to raise the part one octave.
Peter

[Jeffery S. Jones]

On 19 Aug 2003 21:04:24 -0700, kevin@lumiere.net (Kevin) wrote:

>Peter <nomail@nowhere.com> wrote in message news:<8f15kv09n38uh3lkgrb9okmrnik3m5mvi5@4ax.com>...
>> Are you sending them in that order cc 101 first, cc 100 and cc 6 last.
>> Peter
>
>Thanks for your interest.
>
>Yes, in fact I am always careful to send the setup data in series.
>I've even tried separating them further apart time-wise, and tried
>slowing down the tempo of the setup bars to about 30 bpm in case it
>was overload. Clearly not.
>
>Can anyone confirm that the correct sequence to raise a part one
>octave is in fact the following?
>
>cc101 = 0
>cc100 = 2
>cc6 = 76
>
>Tonight I tried initializing the MU100R (which I should have tried
>earlier) but that did not help.
>
>I tried using my XGedit Mac, but it will only send SYSEX for key
>change.

As long as we're thinking basic troubleshootings, does the RPN for
fine tuning or pitch bend sensitivity work?

Can you use the NPRNs to change things?

Now, the MU100 is an XG synth, and those allow a sysex message to
disable controllers, including RPNs. But that disable affects all
messages of that class, not just specific ones. It also should *not*
remain disabled past a reset -- GM, GS, or XG all should do that.

You could try sending a GS reset sysex, then use the RPNs.

You are using the right sequence. The timing between events is
supposed to be one tick, I think; most sequencers will do this
automatically if they have entry of RPN or NPRN via GUI rather than
single events.
--
*-__Jeffery Jones__________| *Starfire* |____________________-*
** Muskego WI Access Channel 14/25 <http://www.execpc.com/~jeffsj/mach7/>
*Starfire Design Studio* <http://www.starfiredesign.com/>