Conference napalm::commusic_v1

    
    I never said anything about the "reset" key. If you stop your sequence
    in the middle, you usually get lots of stuck notes. The "reset"
    key sends an all-notes-off message on all channels, then if you
    hold it down it starts cycling through the note range for each channel
    sending individual note-off messages. It does not send controller-off
    messages though so you still need to hit the hold switches once
    for each keyboard if you stop a sequence in the middle...
    
    /pjh

    I didn't understand your remark about the Octapad, as the Octapad
    already has a lower velocity limit.  I.e., no matter how soft you
    hit it, it will never send a velocity lower than the specified level.
    Did you mean the upper limit feature?
    
    len.
    

    
    Yeah, probably the upper limit *is* what I meant. I'm not a
    particularly good drummer and I tend to whap some things harder
    than others.
    
    /pjh
    

    o Patch-Chain. Allows sending of program change from the patcher
      to the MIDI outputs. So when you change the patch in the MX-8,
      all your other devices change too.

    This one has been puzzling me.  Maybe I am on MIDI overload so my
    brain is not processing things fast enough.

    Let's say I want to access a sound during a live performance which
    is created by layering 3 MIDI synths together.  Let's look at a
    concrete example:
    
    Synth #1: assigned to MIDI channel 1 - need patch 13
    Synth #2: assigned to MIDI channel 2 - need patch 23
    Synth #3: assigned to MIDI channel 3 - need patch 36
    
    Now, when I hit patch change 2 on my KX76, I'll have the MX-8 tell
    the other synths to move to the appropriate patches.  So far so
    good, right?
    
    But, how do the synths know what notes to play?  My keyboard can
    only broadcast on 2 MIDI channels simultaneously, so I can only
    address 2 different synths at once.  If I set the synths to OMNI
    mode, then I can no longer have them respond to different patch
    change requests.
    
    Am I missing something?  How can I use the switcher to send different
    patch changes to different modules, but also have them play notes
    coming from one MIDI channel?  Does the channel shifting feature
    help me out here at all?
    
    		Thanks,
    		Derek_proud_owner_of_a_one_day_old_KX76
    
   

    re: .5
    
    What they call "patch chain" sounds more like what's generally called
    system controller.  Basicly it allows you to push one button and
    have the entire MIDI system configured however you want it, both
    in terms of routine AND patches (sounds).
    
    It isn't clear from the description that the MX-8 allows you to setup
    the kind of layer in your example, however I'd be surprised if there
    wasn't a way to do it.   Perhaps it can be done on an OUTPUT plug
    basis rather than a "channel" basis.
    
    For example:
    
    	1) Keyboard controller sends on channel 1 into MX-8 input 1
    	2) Synth 1 receives on channel 1 from MX-8 output 1
    	3) Synth 2 receives on channel 2 from MX-8 output 2 which is
    	   channel reassigned from MX-8 input 1.
    	4) Synth 3 receives on channel 3 from MX-8 output 3 which is
    	   channel reassigned from MX-8 input 1.
    
    The disadvantage here is that you've gobbled up a few outputs.  My
    guess is that there's a way to do it and still have everything in
    series.
    
    	db

    Seems to me the way to do it is to echo channel 1 to channels 2
    and 3 with zero delay.
    
    							John.

    re a few back.. Derek, if you're xmitting on two channels from your
    KX__, and you set your SGU's in OMNI, half of the available voices
    go away. Or, put another way, they'll all play the same notes twice.
    
    Sounds like leaving the synths on separate MIDI channels, allowing
    discrete patch changes, then 'echoing' 1 channel's notes only to
    the other two channels, is the way to think about this one.
    
    karl

    
    re: .5 Derek
    
      You got the patch-chain part right. I tried it at lunch (it's
    great being 6 minutes away from the studio). Seems to tell everyone
    "go change". 
    
      Your other problem could be addressed numerous ways. Notably .-1's
    (Karl) has a good idea, i.e. using multiple channels. Since you
    can route one channel to another, that's an idea. You might also
    consider using the split function to split a note range (like bass,
    for instance) off to another channel.
    
    re: .8 Dave
    
      Thanks. Yes, I think I'm pretty gaga over it. It sure is useful,
    and  about the only other comments I could make are that the front
    panel buttons are a little bit cheap feeling (very pronounced
    calculator-type click). The LCD cannot be seen from any angle except
    straight on. Ah well, it's cheap, it's pretty fast, it's easy to
    use, so what if you can't see it work? 
    
    /pjh

    Of course, another way to do this might be to assign the same patch
    number to each patch in the overlay.
    
    Of course, not all MIDI stuff lets you do this, AND it may require that
    you to manually change the MIDI channel assignments when you do other
    things.  
    
    	db

    
    
    I tried some of this stuff last night. Boy this is a neat box.
    
    it's too bad the ESQ-1 only has eight voices. By creating a "sequence",
    and assigning multiple voices to different MIDI channels, you get
    a reasonable multi-timbral synth. 
    
    With that editorial out of the way, I set up an "echo" using the
    output of the KCS as input. I set it up so that the EPS got an
    unprocessed command stream, and I set up processor A to feed the
    ESQ-1 which was listening on two channels (4 and 1, in that order).
    Using the split/map, I took the bass notes out of the channel 1
    feed to the ESQ, then I delayed it by 10ms. The effect I was trying
    for was to get a celesta back behind the piano which was playing
    on the EPS, both on channel 1 (the EPS got the full keyboard range,
    but I don't really like "bass celesta"). The delay was to add some
    reality to the sound (perception being that a bell player won't
    play exactly the same time as a piano player). Well it works, and
    it took about 2 minutes to set up. 
    
    Now I need a couple more multi-timbral rack mounts. This, after
    spending $4K or so in the last three weeks for studio equipment...!
    
    Cheers.
    
    /pjh
    

The MX-8 looks like the box to go with, right now. I talked with Eddie at
Wurly's Worcester and he will sell them to us for $325. This is the DECMS
price, not the street price. Street price is $349. See DECMS topic for
further info.

I'm afraid that the trend towards "wall bugs" is going to continue. The
main reasons are:

1. rack mount space - it is much easier to develop a one-high rack mount unit
		      design if the power supply is external. The bulky
		      power transformer, heat dissipation, noise, etc. problems
		      are solved, and the unit actually ends up being cheaper.

2. noise - it is much easier and cheaper to avoid 60 cycle hum and ground loops
	   by feeding only DC to the unit.

I hate the things too, though. Crank up the production line on those wall
bug power strips!

    Paul,
    
    What is "echoed".  MIDI notes? patch changes? MIDI volume? Everything?
    
    If patches changes are echoed, you could have a slight problem doing
    that layering application that was mentioned earlier.
    
    	db

    
    No, it appears that only key/velocity/note-on-off seems to echo.
    Although I could just filter out the program changes anyway, but
    then that defeats the program-chain function.
    
    I might add that chaining hardware (like the fx boxes) kind of limits
    your ability to send program change commands anyway, since you probably
    want to send each box a different program.
    
    Anyway, to tell the truth, I didn't send any program change info
    out anyway, but the application as stated worked fine (as I stated
    .2 ago)... But I'll try it and let you know.
    
    /pjh
    
    

    You could send a mode message which to DISABLE omni mode, send program
    changes, and then send a mode message to ENABLE omni.
    
    I'm not sure if the MX8 would allow you to do this.  An Axxess Mapper
    would allow this, if you could ever figure out how to make it do
    anything at all.
    
    Steph

    
    re: Steph
    
      Well the MX-8 won't filter the mode messages unless you tell it
    to. Thankfully, it is quite a simple operation to allow it to pass
    messages through.
    
      I even figured out how to record the HR-16/Octapad combination
    without unwittingly merging the HR-16 tracks through anything. Just
    merge the Atari and Octapad outputs to the HR-16 in, and patch the
    Octapad output to the Atari instead of the HR-16. You record note
    on/note number info anyway...
    
     So far so good. I even have a song almost ready for Commusic V...
    
    /pjh

    
    Okay, so based on the reviews in this file, I went out and bought
    an MX-8....  everyone's right... a very nifty box.  The worst part
    about it was making up six more MIDI cables....  $325 at Wurly's
    in Worcester using the magic "DECMS" password...
    
    A very impressive unit...  can't imagine life without it anymore...
    except:
    
    I'd really like to route an output to NOWHERE.  That is, have NO
    INPUT assigned to an output.  When I play the keyboard on my ESQ,
    and it is set up as the master controller, I'd like it NOT to receive
    any input from itself, or any other device...
    What I do now is just assign it to an empty
    input port.  I haven't seen any references in the manual... does
    anyone suppose there is a way to do this when I someday have SIX
    midi devices on the box?
    
    
   

    Can you set the MX-8 to do the following:
    	
    6 devices;
    	
    whenever any of the devices talk, all 5 others hear it;
    	
    BUT
    
    no device hears itself talking?
    	
    	(this isn't an idle question- I need this)
    	
    	-Bill
    

    
    re: .-1
    
      well, not quite.
    
    I have gotten one device to do that with all others, but not any
    random device.
    
    case in point - using my EPS as a controller, although I got voices
    loaded in, I don't want to use 'em just yet. I want the EPS to control
    the ESQ-1. Yes, I can do that, just by disconnecting (in software)
    the EPS keyboard from the instruments, then setting the instruments
    for MIDI IN, then not completing the connection from the MX-8 (by
    not selecting that output, or assigning it to B or something I'm
    not using).
    
    But I gotta change the config every time I change controllers, i.e.
    it's not an 'actively sensed' configuration.
    
    /pjh
    
    p.s. what are you doing????
    

    I've got four controllers:
    	Octapad (controller only)
    	ESQ-1 (controller + sound generator)
    	DX-100 (sound generator + breath controller)
    	HR-16 (sound generator + VERY OCCASIONALLY controller ("filled
    		swing beats") )
    
    With the exception of the Octapad, _every device_ I have at some
    pair of points is both a sound generator and a controller for another
    device.
    
    By MIDI channel magic I can control that part.
    	
    But the every-to-every configuration will cause all my notes to
    be doubled if I connect the devices in the logical form (i.e. a
    ring).  That's where the "everybody-but-self" need comes from.
      
    Does this make sense?
    
    	-Bill

    I've found "LOCAL OFF" to be one of the most usefull features to
    come down the pike, allowing no device to talk to itself without
    going over the buss...
    
    3 things I'd like to see on all devices...
    
             1. Separate TX and RX selectors...
             2. Selectable OUT/THRU merge...
             3. Local OFF mode.
    
    Seems like it would make life tres easy...
    
    Edd

    
    re: .-2
    
      Yeah, now I understand. I shut off the HR-16 'echo in-out', for
    starters. Obviously the 8Pad only goes out. The ESQ-1, I use a 'muted'
    voice (real tough: just shut off all the DCAs), and then change
    channels for the voices in the sequencer (and I don't use the sequencer
    for songs; I use it as a poly-timbral instrument). That way the
    keyboard puts out 'base channel' and it's not necessarily what is
    expected by the voices. I do the same thing with the EPS, since
    you can create 'midi instruments' which have no real voice in the
    EPS, they just occupy a channel space.  
    
      This gets me the ability to disconnect the keyboards from the
    voices. I dunno how to get a DXmumble to do it, since I don;t have
    one anymore and didn't try it back when I had one, but I know you
    just don't use "MIDI THRU" for anything.
    
      Re: .-1
    
        Right on. Yeah, the ESQ-1 has 'local/midi/off' as choices in
    the sequencer map. By judicious use and diddling you can make the
    keyboard play out on one channel, merge/delay to another channel,
    and play it back in through the 'sequencer'. Pretty odd feeling.
    
      
    /pjh
     

I have a question for you MX-8 owners...

Here's what I'm considering.  Currently, I have everything except the MX-8.
All the machines are, possibly unwisely, chained MIDI-thru to MIDI-IN, etc.
Like Xk --> Mirage --> OB8 --> DX7.  Okay, so I lied, I don't have the ESQ
just yet, but I will soon...  The Xk does all of the patch changes and zones
it's keyboard for splits and/or layers for the three instruments. The challenge
now is that (1) with the addition of the ESQ, and assuming I don't dump the DX,
I now have 4 slaves (plus I'm getting other midi-controllable gear), and the
Xk has only 3 zones, which means I'll need at least two Xk patches to set up
each number, (2) I want to use the ESQ's sequencer to control everything else
and (3) I like the keyboard of the EsQ or the DX over the Xk, and would rather
play from either of those.  I'm considering this:

                    +----------<<<-----+
                    |                  |
                    |     +--> ESQ-1 --+
                    |     |
                    |     |
                    |     +--> Mirage
                    |     |
                    V     |
 Oberheim ----->  MX-8  --+--> OB-8
    Xk                    |
Controller                |
                          +--> DX-7


The Xk should still be able to send patch changes to up to 3 of the slaves.
THe ESQ should be able to send to up to 8.  My question is, can the MX-8 map
the ESQ's keyboard such that there is any combination of slaves on the
keyboard, in any zone?  That is, splits, layers, whatever? Then, the Xk becomes
a fairly unnecessary piece of equipment.  For example, with the Xk now, I can
have OB8 on notes 0 to 25, DX7 on notes 26 to 60, and Mirage on notes 0 to 60.
Could the MX8 be used in conjunction with a synth with local-off, as an 8-zone
Xk (with other features, of course, but the first step is to replace the Xk)?
Overlapping zones is the key here, as a big part of my sound is based on it.

Thanks for any suggestions,
andy

    Be careful there, I got "bit" by a very similar arrangement:
    	
    		---------
    		|	|
    		|in     |
    	       ESQ      |
        	|out    |
    		|       |
    		|in     |
    	      Octapad   |
    		|thru   |
    		|	|
    	      	|in	|
    	       HR16	|
    		|thru	|      
    		|       |
    		|in     |
    	       Xpander  |
    		|thru   |
    		|	|
    		---------
    	                 
    the problem was that everything worked fine UNTIL I tried to record
    a sequence into the ESQ from the ESQ keyboard; then every note was 
    doubled in memory.  Even now I have to disconnect the MIDI IN on
    the ESQ to record from ESQ keyboard, and reinsert it to record from
    the Octapad.
    
    Bleeahhhh!
                         

    No "Local Off"?
    
    Edd

    That doubling up due to the MIDI loop is why I can't use the Emax
    as both an SGU and a system sequencer for live use.. it plays itself!
    
    karl

< Note 1336.26 by JAWS::COTE "Need help? 296-4596" >

>    No "Local Off"?

Are you asking if the ESQ has local off or not?  I think it does...

andy

    Yeah, that's what I was asking. It looks like if you just enable
    LOCAL OFF and only feed the sequencer VIA MIDI you'll end that
    problem....
    
    Or do I misundertake the problem?
    
    Edd

    First, the ESQ does have the equivalent of local off but ONLY if
    you have a track selected with the MIDI status.
    
    There's this distinction between being in "straight synth mode" vs.
    track mode.  In straight synth mode, the ESQ works pretty much
    like any other synth.  It plays the internal program selected,
    and sends out MIDI data on the selected channel.
    
    In track mode, what's done with the keyboard is identical to what would
    be done if the notes played on the keyboard were being played from the
    sequencer's memory.  I.E. it does whatever the selected track would do.
    
    Thus if the track is driving an external device, whatever you play on
    the keyboard is sent out on the MIDI channel for the track which may
    be different from that of the "straight synth" and does NOT cause 
    the ESQ-1 to play the notes.
    
    This is all part of the track status page (MIDI subpage I think).
    
    There's a table in the manual that tells you what the keyboard does,
    and what the track data does for each of BOTH, MIDI, LOCAL and SEQ.
    It's worth a look.
    
    	db

    > ESQ sequencer records MIDI IN too?  Wunderbar
    
    Of course.  The ESQ sequencer is about as complete a LCD display
    type sequencer as I could ever imagine.
    
    But... there is one problem when recording from MIDI IN.
    
    Suppose I want to record a piano track to the ESQ by playing on
    my KX-88 and using an MKS-20.
    
    The problem is one of contention for the MKS-20's MIDI IN.
    
    The KX-88 output has to reach the ESQ (to record) AND the MKS
    (to hear what is being recorded).  The output of the ESQ also
    has to reach the MKS (for playback).
    
    Thus you have an ESQ 1 input that also has to be an output.
    
    The ESQ-1 does not have THRU (would help in a minor sort of way),
    nor does it having a merge function (merge-to-out should be REQUIRED
    in the next MIDI standard if you ask me).
    
    Bottom line: you can't record the way I've described above without
    switching connections.  This is where a DMC MX-8 comes in handy.
    
    But, GUESS WHAT the SQ-80 happens to have?  MIDI thru.  Well... that
    helps, but you still have to switch cables.  But at least your just
    moving one cable to the socket right next door.
    
    	db

    
    ...jeez, you guys never answered the question!
    
    re: .-a few
    
      I think, the answer is "yes", although there are other ways to
    go about it (so it would seem). I have an ESQ-1 and a DMC-8 and
    although I don't use the sequencer much (got an Atari), I use the
    sequencer tracks as multitimbral instruments.  
    
    /pjh

    
    
    Well. My MX-80 crapped out on me this week.
    
    Interesting problem. All of a sudden the Atari (w/Dr. T's) started
    freaking out in record mode. You'd start recording, the metronome
    would make it about 8 or 9 counts, then the whole thing would freeze.
    
    Leaving it alone for more than 2 minutes would crash the machine.
    
    Bizarre. So I started my usual troubleshooting technique, which
    was to try to first reconstruct the problem. Unplugging the MIDI
    IN to the Atari got my mouse pointer back. Got in and looked at
    the track, it had about 20000 MIDI ON events for note number F -1.
    F -1???? Huh?
    
    Okay. So it was definitely reproducable, and it seemed that all
    my synths exhibited the same behavior. This didn't make sense, since
    I hadn't done anything to their parameters. The Atari ran all it's
    other software fine, and Dr. T's played back tracks fine.
    
    So I tried bypassing the MX-80. Hmm. Problem went away. Subsequent
    tries with other cables, etc, kept coming back to it. So for some
    reason the MX-80 just decided to up and croak.
    
    I would be very interested to find out if anyone else has seen anything
    like this. I have sent the unit back (and got a loaned JLCooper
    patcher from my local music store) and await a verdict. 
    
    Two lessons. One, I'm glad I got it locally (I got two gigs this
    week that MUST have a midi patcher), and I'm also glad for one year
    warrantees....
    
    Whatever. FYI.
    
    /pjh

    Is it possible that it just got confused and needed "reset"?  I had an
    ESQ-M that became catatonic for unknown reasons.  A system reset (which
    blew away everything I'd done) fixed the problem. 

    Or are we talking little/no o/s on these switcher thingies?  I'm kinda
    curious now. 

-b

    
    re: .-1
    
      Not only is there nothing to reset (other than the "reset" key),
    there isn't even a sysex command to initialize it again. Changing
    programs didn't help. 
    
      There is not much of an os on it. That's both the beauty (simplistic
    = VERY easy to use) and a problem (no diagnostix).
    
    Well at least I tried. Shutting it off, turning it on, hitting the
    RESET key (which actually sends out MIDI note-offs to everybody)
    all did nothing.
    
    Go it soes.
    
    /pjh

    re: .8
    
    > Arrgghh!!!  Oh well, only a minor flaw easily worked around.  I may
    > soon start marketing my "wall bug extenders" which are very short 
    > extensions cords which allow me to plug all my wall bug powered
    > devices into one power strip (they normally wouldn't fit because the
    > wall bugs tend to cover up adjacent plugs).
    
    > Death to wall bugs!!!  Besides the flake who installed all the power
    > outlets in my house put them all in upside down (Yes, there is a
    > "correct" orientation.)
    
    Does this mean that there would be a market for a 'power distribution
    box' that would drop into the bottom of a rack (like the power
    controllers in our computers) and supply DC to all the wall-bug-powered
    devices? Maybe battery-backed up?
    
    	- HBM (who builds linear power supplies in his sleep)

    
    re: .-1
    
      Yes. However there are no perceptable standards for voltage, jack
    style, jack polarity, etc. 
    
      /pjh

    I don't know if there's a market for that kind of thing, but I do know
    there that kind of thing is being marketed.
    
    I've seen about 6 different kinds of rack-mounted power distribution
    devices.   They have various kinds of features that are useful
    such as:
    
    	o surge protection
    	o noise filtering
    	o Pilot lights (lets you know if power is coming in)
    	o Ground lifts (for eliminating ground loops which cause nosie)
    	o Common on/off switch
    
    I can think of one other feature I'd like to see that I never have
    which is a "staged" power on and power off sequencing.  In other words,
    when I tell it to cut power I'd like to be able to say turn off the
    amp first, then the effects, and then the SGU's.
    
    I've already fried several channels on my cheapo Kawai keyboard
    mixer by having the ESQ-1 send spikes thru when it was turned off
    (even if you turn it from using the power switch on the ESQ-1).
    
    Actually, something that just has "two" on/off buttons would probably
    be good enough.
    
    If you wanna build one of these for me (it doesn't have to have *all*
    the features I've mentioned), I'd gladly pay you for it, although it
    would have to be at a reasonable savings over what's already on the
    market.
    
    And while it's not something I state with any pride, I can also 
    tell you that I'd make a great "field test" site:  I've had lots 
    of problems with power supplies.
    
    	db

    re: "intelligent power down sequence"
    
    Oh baby, oh baby.... yeah!
    
    My Mirage often sends out a spike at poweroff time that, if the
    board gets a hold of it, has momentarily all but killed the 
    lights in the studio,,,
    
    Ya know how lights will blink a bit when you turn on a big amp??
    Worser.
    
    Edd

    
    Re: remote power supply
    
    Rane Corporation is trying to standardize this by producing a single
    rack space supply that powers the whole rack of effects. They are
    daisy-chained via a plug/jack system that looks a lot like a telephone
    modular system but has larger gauge wires. The rest of the industry 
    is neither coming or going.
    
    Re: timed powerup-powerdown
    
    I've designed these kind of systems for nightclubs, so that the dj
    doesn't blow the subwoofers if they switch off the board or the effects
    before letting the amps wind down. I'm sure Mr. Yerazunis could come up
    with a circuit. Or maybe Mr. Janzen.
    
    CdH
    

    Mr.  Mister?  MISTER!!!  HA!
        
        <<<insert mad scientist cackle here>>>
    	
    -----
                                             
    Circuit's simple- what you really want is something that crowbars
    the output signal before the circuitry can lose it's cookies on
    power loss.  Simply sequencing power up/down is inadequate as 
    the big spikes I see are due to some ape kicking a power cord out...
    
    Simple to do- but you'll need one at each input of every device.
    
    -----
    
    You can get halfway there by putting passive limiters on every input
    jack that you want to protect.  They look like this:
        
               1 Kohm
       -------\/\/\/\-----------------------------to where the jack
       |                   |    |                lead used to go...
       v                   |    |
    O     ...existing      V    _   ...silicon rectifiers
     \        jack         -    ^
      \                    |    |
       \------------------------------GROUND
    
                                     
    What the passive limiter does is clip any signal that is "hotter"
    than .65 volts to .65 volts or less.  That's all, it is always
    "on duty".  Any silicon rectifier will do just fine (try 1 amp,
    50 volt).  
    
    The .65 volt threshold is intrinsic with the nature of a silicon
    rectifier.  It'll be just fine for keyboards, but it's too insensitive
    for guitars and too sensitive for some pro (+4dB) equipment.  It
    also doesn't work for lo-Z (pro 3-pin cannon) connectors.
                                                             
    I'll think about how to do it in the general case...
    	
    	-Bill
    

    
    The passive limiter is nfg. We (at least I) spend big bux on equipment 
    with lots of dynamic range and headroom. I wouldn't give that up for
    protection. I might as well have bought DOD 8^)
    
    I don't see where the timed and sequenced power up/down won't prevent
    the synth spikes that Edd was talking about. It sure works great for
    club sound systems.
    
    If you're worried about someone kicking out the power plug, then tape
    them down. If all the individual power cords are inside a rack with a
    power distribution box of some sort, then I don't see any problem.
    Enlighten me.
    
    CdH
    
    

    The timed powerdown wouldn't prevent the spikes from being produced,
    but it would prevent my amp from faithfully trying to amplify it.
    
    I sometimes forget to shut the board/amp down first....
    
    Edd 

    
    
    I have all my studio powered by on 13 amp UK standard power socket.
    
    To power up I insert the plug in the socket.        
                                            
    To power down I uninsert it.            
                                            
    I have no problems with any of the above.
    
    Is U.K. power cleaner?
    
    Do I misunderstand.
    
    Am I very Lucky ?
    
    
    					Paul.

    Edd explained the need for for it.  Equipment is less likely to be
    damaged by those spikes if its powered down.
    
    > Is U.K. power cleaner?
    
    Has nothing to do with clean power.  Has to do with what equipment
    does when powered up or powered down.  Your probably just fortunate
    enough to have equipment that doesn't have these problems.
    
    Next time you go into a music store, turn on an ESQ-1, let it sit
    for awhile, and then turn it off while its still plugged into an
    amp.   Try it enough times and eventually you'll probably hear
    something like a shriek.  
    
    My SQ-80 sometimes makes a "kissing sound" when it's turned off.
    It's sorta nice to say goodbye that way.  Afterall, it is touted
    as a user friendly machine!  ;-)
    
    	db

    re .36 et seq.: Roland offers such a unit for its BOSS MicroRack
    series of effects units.  The power supply can handle some large
    number of units which are daisy chauned together.
    
    Uhm, just an observation about our intentions to clean up our act
    here in COMMUSIC - here we are talking about power supply issues
    in a note title "Review of MX-8" or some such...
    
    len.
    

    
    
    re: my dead MX-8
    
      I got a call from a guy from DMC in California. My hurt unit was
    sitting on his bench. He couldn't get it to do what it was doing
    to my network.
    
      Nice guy, though. We talked the whole problem through. He seemed
    to think it was a ground loop causing it to send (actually repeat)
    messages ad infinitum. He was going to try to reproduce it on the
    Atari sitting there.
    
      One piece he leaked (and BTW he authorized it to be said here,
    since I asked) was that DMC is developing some Atari software to
    diddle the MX-8. I'll be a beta test site for sure...
    
      /pjh

    Can any of you MX-8 guys tell me if it will solve the following
    problem?
    
    OK, I've got, like, *five* (count 'em: TR-707, TR-727, TR-909,
    LinnDrum, HR-16) drum machines now.  I want to use different ones
    for different voices.  My MC-500 assumes *all* voices on the rhythm
    track are on the same MIDI channel.  But sometimes I want to "double"
    voices (i.e., have a single "rhythm instrument" on the MC-500 trigger
    two drum machines at the same time) and because of the brain damaged
    way the TRs respond to velocity, I want them to only see the notes
    I want them to play.  Sometimes I may want the MC-500 to trigger
    a "note cluster" on a particular channel (e.g., for a gong strike
    on the MKS-80).
    
    So what I need to be able to do is remap notes on a particular channel
    (the MC-500 rhythm channel) on a note by note basis (i.e., each
    individual MC-500 rhythm instrument) to different channels (one
    for each drum machine) and possibly different note numbers (for
    the specific voice-to-note-number mapping on that machine).
    
    E.g.:
    
    	Incoming channel/note	Outgoing channel(s)/note(s)
    
    		  10/35			  11/35
       		  10/38			  10/38
       		  10/42			  12/42 + 13/42
     		  10/44			  12/41
      		  10/46			  13/43
     		  10/48			  14/44
                  10/50			  1/23 + 1/24 + 1/25 + 1/26
    etc.
    
    I may also want it to throw everything else on the floor.
    
    Can an MX-8 do this for me?  If it can, I'll run out and buy one
    this weekend.
          
    len.

    perhaps you'd consider buying an amiga len.
    Tom

    I already have one (as you well know, Tom), and there's no software
    that I'm aware of that does what I want.  And I'm not willing to
    write my own.  And finally, I really don't want to have to integrate
    the Amiga into my MIDI setup, because then it wouldn't be as convenient
    to use for games and graphics.
    
    len.
    

			< Note 1336.50 by DRUMS::FEHSKENS >

>    write my own.  And finally, I really don't want to have to integrate
>    the Amiga into my MIDI setup, because then it wouldn't be as convenient
>    to use for games and graphics.
    
	Len, why do you use your MIDI setup for games and graphics?

--mike

    Yuk yuk, I deserved that, I would have made the same clever reply
    myself.
    
    But won't somebody please tell me about the MX-8?
    
    len.
    

    
    Sure, Len. I think your answer is "Probably not completely".
    
    You may set up "keyboard map areas" using the processors, and they
    will filter out "unwanted" notes effectively zoning outputs. You
    may redirect output too, for instance to another channel. Either
    way, it looks like a LOT of channels and/or zones, and the MX-8
    only has two processors (total of four zones). So if your drumboxes
    have assignable keymaps, AND you can live within four zone/channel
    combinations, you can. Sounds like you need more though, so maybe
    you can't.
    
    I'll try a smaller version of your setup tonight when I go over
    to my studio. 
    
    BTW, mine is back. I'll report back if there are any more problems.
    
    /pjh

    Yeah, my impression from talking to rocking' Ron is I probably can't
    do what I want.  Maybe Roland made it possible to assign channels
    to individual rhythm instruments (instead of the same channel to
    all of them) in the MC-500 Mark II software; that would get me most
    of where I wanna go.  Also, I think the Axxess MIDImapper would
    do what I want.
    
    len.
    

    
    re: .-1
    
      Len, there is always the possibility of just mapping all the
    drumboxes to the same channel, but giving every 'instrument' it's
    own key number. You'll probably only use 60 of 'em...
    
    /pjh

    ...but then a snare hit could conceivably take 5 notes.
    
    Edd

    I just picked up an MX-8 (yesterday in fact), pretty cheaply. I
    understand that there is some sort of ROM chip update that you can get
    for $10.00 (or there abouts) to allow you to force the MX-8 to do
    a MIDI dump (from the front panel). Since I'd like to back up my
    settings onto my quick disk, this would be nice to have. Anyone know
    anymore about this??

    Also, Mine has a high pitched whistle (not real loud), which I suspect
    is the power supply inside the box. Is this common, or is it time to
    put some RTV on all of the coils in the MX-8????

    This unit works interestingly, but, I wish some of the specific MIDI
    settings were global (In particular, I want to send all my MIDI patch
    changes to channel 11 & have the MX-8 be the channel 11 device). I
    have to set this for all of the (up to) 50 control patches on the box!!

    So far I only use it to allow me to randomly merge devices together, as
    needed, but plan to use the splits feature to play games with a Yamaha
    SHS-10 keyboard's drum machine & transpose the 4 drum sounds to match
    my Roland MT-32. Weird stuff that you can do with this MX-8.

    Why did I buy one?? I needed a 4 in 1 out MIDI merge and the cost of
    adding 2 more 2 in 1 out units to my existing 2 in 1 out cost more than
    the used MX-8. I still wish that I could merge more together.

							Jens

    
    Congratulations. Hope you enjoy it.
    
    The whistle seems to be universal, the engineer I talked to said
    it's the V-V converter running the display. 
    
    There is software coming down the pike to drive the box from both
    Macs and STs.
    
    I'm still having a strange problem with mine, but I'm not convinced
    that it's not my fault.
    
    More later.
    

    Yes, I just bought an MX-8, and immediately noticed the high-pitched
    "whine".  Then, out of curiousity, I checked my other devices in
    the rack ... all but the MX-8 and the ProMIDIbass are quite (the
    bass unit makes a low-pitched hum) ... these noises seem NOT to
    make it to the AUDIO OUTs, luckily!
    
    	-Jim

RE < Note 1336.59 by FGVAXX::LAING "Soft-Core-Cuddler*Jim Laing*261-2194" >

	What has been the best price people have gotten on this unit?  I'm 
getting ready to buy one and have gotten $295 as the best price so far.  

	Dan

    I paid $329 for mine at Daddy's, Nashua.
    
    A question (also asked somewhere in Notes 1890) ... does the MX-8
    RESPOND to patch-change (program change) requests?  I.e, if I send
    a program change to the MX-8, can I get the MX-8 ITSELF to change
    to that patch, while NOT having any of my SGUs go to that patch?
    
    Reason ... so I can have a dedicated patch-changer control ONLY
    the MX-8 ...
    
    	-Jim

    I checked the manual, and tried it out ... seems that it DOES accept
    program-change commands, but the commands must be directed to the
    A or B processor, on a specific MIDI channel.  Further, it seems
    (from trying it out) that the device sending the program-change
    to the MX-8 *must* also be "connected" to that processor, and to
    an output.
    
    I'd like to, for example, send ALL my program-change requests (to
    control the MX-8's patch #, that is) via a specific input, on a
    specific MIDI channel.  If I have processors A and B in use for
    other purposes, I can't get the MX-8 to receive program-change
    commands.
    
    Or am I missing something?
    
    		-Jim

    You arn't missing anything. Either the A or B processor has to be
    assigned to an input device that will supply the MIDI patch change.

								Jens

    I called Digital Music (those that make the MX-8).  I asked if they
    had plans to allow for easier patch-change, or for allowing
    patch-change receive w/o using A or B...the guy said NO.  He was
    very helpful and talked to me for 15-20 minutes, but he seemed to
    make it clear that there wouldn't be such changes to the MX-8.
    
    Also, for those that have older MX-8;s ... the newer ones, version
    v3.0 and higher (mine's v3.1) allow GLOBAL setting for patch-change
    receive info (MIDI channel, Processor A or B, and ON/OFF for the
    feature).
    
    My idea - which I may mail in to Digital Music ... is this::
    
    Have a "Fast Load Mode" which you select from with the FUNCTION
    key.  When in FAST LOAD (which you'd use when gigging, for example),
    you'd select new patches by pressing the > and < button 'til you
    have the selected patch in view (perhaps the MX-8 would display
    your CURRENT patch steady and the SELECTED one blinking), then when
    you want to choose the new patch, hit YES once.  
    
    I think this would be useful in live settings where you want to
    change patches on the MX-8 QUICKLY ... more quickly than the current
    LOAD scheme ... hit FUNCTION twice to get to the LOAD page, hit
    < and > to get the patch you want, hit YES twice.
    
    Does anyone else think "Fast LOAD Mode" would be a good feature
    to have on the MX-8?
    
    				-Jim

    Re -.1
    
    As I re-read my note, I think I may have those version numbers wrong.
    It might be v1.30 and up that have GLOBAL setting for MX-8 receipt
    of patch change reqeuest...
    		
    		-Jim

re. < Note 1336.60 by NRPUR::DEATON >
                            -< Current best price? >-
Hi Dan,

>	What has been the best price people have gotten on this unit?  I'm 
>getting ready to buy one and have gotten $295 as the best price so far.  

	Where (if you don't mind me asking) did you get your best price?
With me on my KX88, Jill on her soon to arrive WX-7 and my Atari Mega ST2,
I've found that I need some kind of merge device and I may as well spring
for the MX-8 because I'm sure I'll need it even more in the future.

Thanks,
Dan	

RE < Note 1336.67 by SQUEKE::GOSSELIN "All things are possible" >

	I believe the $295 price was from Caruso's in CT.  But Sam Ash said
they'd match it without a hassle (or possibly go lower, can't remember).  It
seems to me that I heard Sam Sah or some big name store selling MX8's without
haggling around this price.  Maybe its in the 'Hot Price' note?

	Incidently, I ended up not needing the MX8 as soon as I got the MC500.
Now that it handles the merge function I needed, and I can program the 
redirecting of MIDI transmit channel on the DX100 via sysex, I was able to
eliminate the need for the patcher.

	Dan

    I found that I really didn't need the MX-8 until I started trying to
    share equipment between my sequencer and my keyboard player (I really
    only play guitar for the Live efforts, altho I was the one who put the
    sequences together). Everything is so much simper when there is a
    singular controller for everything. However, We are using an MMT-8 and
    the sequencer in an ESQ-1, and allowing a Yamaha SHS-10 (cheap, but
    quite functional) MIDI strap on keyboard to occasionally take control
    of the entire network (the SHS-10 plays all of the MIDI gear when it is
    in control). I used to have a single MERGE box, but found that my set
    up became way to complex to keep track of, especially in any form of
    Live situation.

    I bought mine used.
							    Jens

Digital Music Corp has come out with a couple of new units. The MX-28S MIDI 
patchbay and the MX-28M MIDI patchbay/merger. The MX-28S is simple 2 x 8 
routing device ($99). 

But the one I'm interested in is the MX-28M. According to Keyboard, "the 
MX-28M allows merging, transposing and keyboard mapping to be user-defined 
in real time". List price (apparently) is $149.

The difference between the MX-28M and the MX-8 *seems* to be this:

MX-8               MX-28M
----               ------
6 inputs           2 inputs
2 MIDI delays      No MIDI delays
$395 list          $149 list

My questions to MX-8 owners are: 

1) Are there more differences than this between the MX-8 and the MX-28M 
(based on the description of the MX-28M given here)?

2) If so, what are these differences?

Obviously, I am trying to determine if the extra functionality of the MX-8
is worth twice the price. (So far, for me, it isn't).

Mike D

	Though I'm not an owner of one (yet), I think the MX-8 also has
	'velocity compression'.

	Dan

	Yes, it does have velocity compression & 6 inputs/8 outputs.

	Since I have to reconfigure my MIDI set up each time I want
	my ESQ-1 to be a controller (rather than the MMT-8), or to
	have a Yamaha SHS-10 be a controller, It's handy to be able
	to randomly re-route things while at a gig, in only a few seconds.

	In general, I have a bunch of patches (set ups foe the MX-8) that
	are for recording & performance. When performing, the SEQUENCER
	(MMT-8) is placed so that It can be loaded from the MIDI disk
	unit while some other controller is driving my MIDI SGU's. It has
	MIDI selectable patches that allow me to send SYSEX to all controllers
	or to selected MIDI lines.

	For recording sequences, I have a number of set ups. Some pass MIDI 
	CLOCK, most suppress it. The routing of my inputs are totally different
	(as are the merges) when recording. I use the velocity compression
	to allow me to set the output velocity levels of my CZ-101 (which
	only transmits at a level of 64) to any level needed. I have all
	sorts of patches that select different levels above 64 & a few that
	don't mess with the velocity at all (In case I'm using my ESQ-1
	or copying some other sequence from aother sequencer). 

	It's nice to be able to totally reconfigure everything at a 
	moments notice & great that it only takes up one rack space. I find 
	that to go back & forth is handy when I get home & start recording
	more sequences & I don't have to worry about my performance set up.

	I spent around 3 hours trying to work up a map of how everything
	should be connected & what functions that I needed in each case.
	I have 15 general set ups that I use. The map is handy so that you 
	have some Idea of what you are doing, and when you need to make any
	changes down the road.

	If you buy one & put it in a rack with other MIDI gear, you'll
	probably need to make up a dozen or so MIDI cables, that are
	12 to 18 inches long. I color coded all of mine (colored tape
	at the end of each cable) so I could figure out which cable
	actually went to what. Radio Shack has the wire (2 conductor
	sheilded wire) and the connectors (5 connection DIN).

							Jens

    
    My MX8  seems to be doing some wierd things... similar to the problems
    that PAULJ::HARRIMAN was having int .33...
    
    I fired up my system the other day and I noticed my ESQ-1 wouldn't
    boot.  It just said "ENSON" in the display... I thought my ESQ was
    dead, but after a bit of tinkering I found that if I plugged the ESQ
    into the MX-8  output #1, the ESQ would crash immediately.  If I used
    coutput #2, everything worked fine...
    
    I haven't tried to sequence the stuff coming out of output #1, but I
    bet I'll see the 20,000 NOTE ON's that others have seen... but I only
    get this on one output... so far!
    
    Someone mentioned a firmware revision -- how do I find out what version
    I have?  Any combination of buttons, or do I just open it up and look
    at the ROMS?  I don't think my MX-8 is covered by its warrany anymore,
    so I wonder how much new ROMs or service will cost...
    
    /Mitch.
    
    
    

	Mine (not upgraded yet either) has locked up on occasion also.
	Usually, if you load a patch (using the buttons on the front    
	panel), it takes care of it. The ROM upgrade is supposed to allow
	SYSEX dumps, but it also changes the way the velocity is compressed.
	In general, I like the old velocity compression better, hence I've 
	not upgraded.

						Jens

    
    I figured out how to do the tests...
    
    It's easy -- hold down both the FUNCTION and RESET buttons while
    you turn the power on.  The screen will say "Test mode? (Y/N)"
    so you press YES, and it will display the ROM version and copyright
    notice.  Press FUNCTION to continue and it will test the display, then
    ask you to press each button.  Finally, it displays:
    
    	"Jump IN/OUT 1..6  Press FUNCTION".
    
    I assume it's trying to tell me to connect MIDI IN #1 to MIDI OUT #1,
    etc.... so I hooked them up, and wonder of wonders... port #1 failed.
    (somehow I knew that would happen!)  Press FUNCTION one more time
    and it will ask you if you want a destructive RAM test.  I pressed
    "Y" at this point to wipe out my RAM and reset the machine.  One
    more press of FUNCTION leads you to the manufacturing burn-in test.
    
    I used a scope and a meter to look at my misbehaving output #1... it
    looks like one of the pins is shorted to ground somewhere... it always
    has a low signal on it when everything else is high.  On the other side
    of the limiting resistors inside, it has continuity with ground, and
    none of the other ports are like that.  I haven't figured out where
    yet, but if I need to change a chip, it won't be much fun...
    everything's soldered down.
    
    What version is considered "new?"  I have version 1.22.
    
    /Mitch.
    

	maybe one of your opto-isolators is fried. 

	I never found the actual cause of my failure, since they replaced the
	entire board for me. I have never had the problem since, although I
	have had some other strange situations occur (I got a funny one the 
	other day - it went into an infinite sweep of the programs until I
	reset it).

	/pjh

    
    I thought the opto-isolators were used on the input sides... aren't
    they?  I have trouble with an output.  In any case, something's
    fried!
    
    Strangely, since I ran the diagnostics, my MX-8 doesn't seem to be
    switching itself to patch #33 on powerup anymore.  It used to do that
    about 60% of the time -- whenever I turned it on, it would change
    from whatever patch I left it at last time I used it and go to #33!
    
    Previously, I just got around that problem by programming #33 to be
    the patch I use most of the time.
    
    Yours was covered under the warranty, wasn't it?  I was kinda wondering
    how much it would cost to get it fixed... but since they're going
    to replace the whole board, I bet it isn't cheap...
    
    /Mitch.
    

If it's the output that's fried, you have a good chance of being able to 
replace the part yo'self.  That's because it is common practice to use
a standard (like, TTL) part as a driver.  Might be able to pick it up at
Radio Shack for a buck.

Steve

	...and it had nothing to do with usage. I'd bitch to the company, 
	and see what they say. Your warranty was a 1-year, right? How far out of
	warranty are you?

	Failing that, I second .-1.  I'd be willing to bet that the driver
	chips aren't custom.

	/pjh

    
    
    My unit was purchased in May '88.  I'm a little more than a year out!
    
    I'm positive I can fix it myself -- the outputs connect more or less
    directly to some mux/demux TTL chips (can't remember the numbers now,
    but similar to LS138's) -- they're quite common, and I think I probably
    have a few in my junk box(es).
    
    /Mitch.
    

	Hmph. They used LS series driver chips on a current driver circuit?
	Perchance had you ever shorted the outputs on the MX-8? Just curious,	
	it would make sense only in cases where the current exceeded the rating
	of the drivers, c'est possible on MIDI, especially if they aren't
	high current devices anyway... I should check my MIDI spec to be sure.

	Anyway, sounds like solder-sucker and sockets for the next time. If 
	that turns out to be the case, can you publish a do-it-yerself 
	instruction set for the rest of us?

	/pjh

    
    I haven't had a chance to map out the output circuit completely yet,
    but just from the looks of things, there's ten 74LS151 1-of-8
    multiplexors, a mess of LS174 D flip-flops, and a microprocessor (looks
    like some Z80 variant).  That sounds like the right amount of stuff to
    construct the crossbar, with the D's used to store the current
    settings.  I haven't figured out how the processors work yet --probably
    some serial I/O on one of the Z80 support chips that they use the extra
    inputs for (explains why there's six inputs and eight outputs).
    
    Now, as for shorting the outputs -- it's certainly possible, since I
    made most of my own MIDI cables.  I might have also zapped one with
    static.
    
    When I figure out what went wrong, of course I'll publish it here!
    (hey, I've got a prom blaster and some Z80 tools... maybe I should fix
    some MX-8 bugs while I'm at it! :-)
    
    /Mitch.
    

Can any of you MX8 owners answer a question or two?  In the latest rev,
have they upped the number of setup slots from the original 50?  Also,
have they added the concept of a chain, ie, chaining setups together
for a song?

Thanks!!

andy

Speaking of the newer incarnations of the MX-8... I saw one at Daddy's a 
while back that had the power supply built into it. No more wall bugs on the 
new ones I guess. Too bad I have an older one.

Mike D

Hi all,

	This MX8 is really great...

	I bought one a few weeks ago in order to allow my keyboards better talk 
to my drummer's SC40 and Octopad II. As stated by Paul (.10) it is rather cheap 
for what it does. (2990 French Francs at Piano Show in Paris).

	To begin with the overall shape, there is no more WallBug (as said by
Mike in .85). The LCD display is now totally silent: (Re: Jens .57) I would 
like having the one of my DDD1 do the same! 
	The front panel looks much better than I would have expected.
	From the operational standpoint, I do like the velocity crosswitch.

	Regarding Andy's questions (.84), the number of setups is still 50, and
there is a "Chain" facility that I did not investigate in details yet.
	
	Small problem though... This beast seems to be very sensitive to 
ground loops: Three weeks ago, we were playing in France at the Theater of 
Grenoble, which is well known as being "strangly" power-supplied. (i.e. there 
is a groundloop somewhere, but the technicians have never been able to suppress
it). We even had to disable the ground connection from our KB300 amplifiers... 
	While testing our installation, the MX8 went crazy and began to 
display some Japanese (Really!!) on the LCD. I tried and make "him" understand 
that my favorite language would have been French, but it looked stuck.

	These were the symptoms:
		1. Japanese display.
		2. No action from any key except the "Reset" button.
		3. Pressing the "Reset" button would bring "Midi Overflow" and
		   stuck the whole.

	We had to rent another merging device for the next day's concert.

	Following the good advice posted by Mitch (.76), I went through
the test mode (press "Function" and "Reset" keys while switching on).
	Each test was successful, and then came the famous "Destructive RAM
Test"... (Please insert here a wild female shout, a D110 "Soundtrack" & 
"Lonely Wolf" + three "Orchestra Hits". Feel free to complete with "Timpani").
	The question "Are you sure (Y/N)?" never seemed so hard to answer...

	My answer was "Yes". The MX8 began to count "Elapsed time", under 
the format: "Hours:00 Minutes:00 Seconds:00". I let it go for 5 minutes
or so, then swiched off. When I switched on again, everything seemed to be ok,
i.e. correct display, correct functinalities, etc. Except for one point: The 
"B" processor did not show anymore on the mapping: For each output, only 1-6 
then A and M could be displayed.

	Here come my three questions:
		1. Did one of you already go for the "Destructive RAM Test"?
		   If yes, which was the result?
		2. Does someone know (or is able to guess) how long such a test
		   might last? The prompt "Elapsed hours" worries me a bit.
		3. Why this time count? 
		   (What are the steps performed meanwhile?).
 
	Please HELP! I plan to go for this test again, and eventually let it 
run overnight if necessary. Is there a big risk in doing this?

Thanks in advance for any info or advice!

Best regards.
Krystian

	I play at some places that are quite a distance from power plants
	(up in the mountains), and have experianced problems where nearly
	all of my gear went totally crazy, or failed in some unexplainable
	manner, only to have it work fine once I tried it again at home.

	My solution (and this seems to be fairly inexpensive) was to add
	a line filter for EMI (Radio Shack used to sell these) and then
	add transient suppression to all of the AC power lines (3 suppressors
	in all). Then, I use a single power strip (also filtered and has
	suppression) to power all of the audio/midi gear so it's on the
	same circuit & all of the grounds are coming from a common place.
	You might not be able to do this if your P.A. is on it's own
	circuit, but my P.A. is currently only 200 watts, so power is not
	normally a problem. I make sure that the lighting system is totally
	out of a different outlet as well as non-musical stuff. 

	I carry a meter around with me, and find that the power in some of
	these places is as low as 90 volts (you should have heard the
	Hammond M3 at this place, sometimes it was in tune, other times
	it sounded quite bad, but only when they were making popcorn).
	Most synth gear doesn't care, but my ESQ-1 sure does & I get soft
	resets all over the place when this sort of thing happens (makes
	using the ESQ-1's sequencer substantially unreliable). The normal
	voltages around here are supposed to be 120 Volts AC at 60 HZ. I'm
	told that 60HZ is a goal that is rarely attained in these mountain
	places.
								Jens

Re: .87
==
	Jens, 

	Thanks for your useful reply: I will take some preventive action now: 
We have around here some Tandy shops that sell "Ratshack" devices. 
	I had as well a look to the note related to power supply: next time,
I'll be on the safe side...


Re: Andy's question in .84
==
	Andy, 

	The "Chain" as they call it is NOT a song chain play facility,
but a "Chain reaction"; i.e, Whenever you select one of the 50 setups, this 
automatically sends a series of program changes (pre-defined by yourself) to 
your gears. 

	I would guess this is not really what you are looking for.

Regards.
Krystian

PS: So, nobody ever tried the Ram Test?
==

	Hi,

	Got the answer from a very helpful and knoledgeable guy from 
	"SARO informatique" in Paris (they import the MX8)

		1. Destructive RAM test just resets the setups. 
		   NO danger at all, as long as you bulk saved them before.

		2. The "Hours/Minutes/Seconds" is just provided for testing  
		   the internal clock: nothing is running meanwhile.

Hope this might help...

Best regards.
Krystian

    My MX8 recently did the "Japanese Character" foul up as described in
    note .86.  The reset procedure in .76 worked in resetting the MX8 to
    original settings, but I lost all my patches.
    
    My users guide says the unit does SYSEX.  I tried to get it to dump
    SYSEX by programming an MC500 to send the appropriate message while 
    recording on another track, but this is not working.  The MX8 is
    sending nothing.
    
    Is anyone doing SYSEX dumps and loads succesfully with the MX8?
    
    Dave

	I got my MX-8 to dump it's contents using Bulkdump, so it must be
	possible. I never tried doing it via a sequencer though. 

	I think I finally figured out what makes it crash (in my case at least).
	I have a couple of sticky keys (the scroll keys). If they stick, and
	it's scrolling, and you start sending MIDI through it, it gets 
	confused (apparently), since all the keyboards crash and the sequencer
	hangs. Twiddle with the sticky keys, hit the reset button, reboot
	everybody, and load the patch I was trying to load in the first
	place, and it would work fine. 

	But if I persisted in trying to restart it after it crashed everything,
	without doing a reset and twiddling the scroll keys, it would then
	hang up and go into Japanese character mode, which requires going
	into diagnostic mode to clear. 

	I dunno if this is the same problem anybody else has had with it, but
	I guess this has happened maybe once a month for the past 10 months.
	I haven't tried reproducing it at will though.

	/pjh

Hi,

	As you know, the MX8 use batteries for setup storage.
	It is a flat round 3 volts , supposed to last 3 to 5 years. 

	When the battery dies, NOTHING tells you what happens, and the owner's 
manual (mine, at least) does not say anything about it: One day, you turn
your MX8 on, the display shows an illuminated first line, and nothing on the 
second line. 
	The worst is that even the reset procedure would not do anything. You 
just cannot use it AT ALL. You have to change the battery... 

	So in case this did not happen to you yet, rush to your nearest battery
'dealer' and buy a spare one!

	Hope this helps.

Christian