[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference napalm::commusic_v1

Title:* * Computer Music, MIDI, and Related Topics * *
Notice:Conference has been write-locked. Use new version.
Moderator:DYPSS1::SCHAFER
Created:Thu Feb 20 1986
Last Modified:Mon Aug 29 1994
Last Successful Update:Fri Jun 06 1997
Number of topics:2852
Total number of notes:33157

2255.0. "Midi Configuration Questions" by RUGRAT::POWELL (Dan Powell/221-5916) Mon Feb 05 1990 16:47

     I recently got a Macintosh to use in my studio and I'm trying to
     re-configure my midi data path using an interface with one IN and three
     OUTS. 

     Assume the following hardware:
     
     M1, ESQ, D110, Matrix 1000, S10, HR16, Quadraverb, Mac w/Vision
     
     Ideally the configuration would allow me to:
     
        o Use the M1 as the master keyboard controller.
        o Play the other SGUs by selecting the appropriate channel/program
          number on the M1. I assume I would have to set up a sequence 
          template to accomplish this (as is the case when using the ESQ
          as a controller).
        o Layer/Split
        o Use the HR16, M1 or Mac as the clock source.
        o Of course the Mac would be able to capture and control everything.
        o Channel Assigns
           Ch 1, 2, 3 - M1 (Global ch = 1, Ch 2 and 3 for multipart)
           Ch 4, 5, 6, 7 - D110
           Ch 8 ESQ
           Ch 9 S10
           Ch 10 Matrix 1000
           Ch 11 Q'verb
           Ch 16 HR16

     I've tried a couple of wiring configs but they haven't been able to do 
     everything I want. Any ideas on the best data path? Will I need
     additional hardware?
T.RTitleUserPersonal
Name
DateLines
2255.1But, You haven't spent enough money yet...CSC32::MOLLERNightmare on Sesame StreetMon Feb 05 1990 18:1917
	The problem with MIDI really shows up when you need to have multiple
	controllers, depending on what you are doing. MIDI Merge boxes
	can usually fix minor things, but I've found that total 
	re-configuration based on need is often required. You might find
	that you can get a bunch of DPDT switches & use them to re-allocate
	setups, or you might look into a MIDI patch bay (like the MX-8).
	
	When all I had was a CZ-101, MT-32 and MMT-8, things were really
	simple. I want to add a Macintosh to my set up this summer also
	(that makes 5 potential controllers for my 2 racks). 

	I would try to diagram the routes that you want to establish, then
	see if you can implement the set-up with a MIDI merge and/or Thru
	Box. Maybe a DPDT switch or 2. If the re-routing is major, then
	look into a MIDI patch bay.

							Jens
2255.2SALSA::MOELLERThela Hun GinjeetMon Feb 05 1990 18:2718
    Here's how I handle the two masters situation.  Remember, while
    recording into the MAC, it's set on 'patch thru' to pass the KX88's
    events thru to the SGU simultaneously with sending already-recorded
    events. 
    
                     YMC10
                    FSK box
                      |
                      v
                     KX88         MAC <------+
                      |            |         |
                      v            v         |
               +--------------------------+  |
               |   Sonus 2 in. 8 out      |  |
               +--------------------------+  |
                |           |          |     |  
                v           v          +-----+
              EMAX        1000PX
2255.3take the time ...RAINBO::MIYATAGaylord MiyataSun Feb 25 1990 07:4628
I would also recommend using any midi merge/patcher ins for providing a 
return path for your SGUs' midi outs to your mac.  This would be useful
for editor/librarian and sampling applications that may be mac driven.
Have special patcher "programs" for these paths;  when you're sequencing
or just playing, these SGU return path inputs are not assigned or merged.

My modem and printer midi outs on the Mac's midi interface go to separate
midi patchers; I have no reason to "link" the two patchers' ins/outs.
I don't daisy chain my SGUs via midi thrus - each SGU is 1 hop away from 
the midi patch bays.

I use my Mac (running Performer) as the midi clock source when my
sequence is playing.  I also have other machines capable of being the 
midi master, but since the mac is playing the sequence and I program
drum patterns/songs into Performer instead of the drum machines, Performer
drives everything.  The only time Performer is slaved to an external 
source is when I sync Performer to the multitrack via SMPTE.

As stated before, if you define your desired modes of operation then figure out
the paths/configurations, you should be all set.  The activities I had
to set up for are playing w/o sequencing from given controller(s), 
sequencing from whatever controller(s), editor/librarian applications, 
and sampling applications.  Define a program numbering convention when you
set up the "programs" on your midi patcher.  I've had to totally redesign the
network on two separate occasions - when I got the second patcher and when I
started using my Mac.  I also try to "load-balance" the two patchers. 

Have fun.