[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

1414.0. "ESQ-Octapad-DX100-HR16 Weird Interaction" by CTHULU::YERAZUNIS (You're walking along the beach and you find a tortise...) Wed May 25 1988 11:46

    Here's a true MIDI weirdness, reproducible at will.  This bug came
    up while I was building a piece for Commusic V (VI?)
    	
    	
    The Network:
    	
    		ESQ-1   (multi-channel SEQ outs on ch 2,3)
    		  |
    		  V
    		Octapad (Merge/transmit on channel 2 or 3)
    		  |
    		  V
    		DX-100  (Recieve on channel 3)
    		  |
    		  V
    		HR-16   (Recieve on channel 2)
    			
                                
    The Weirdness:
    	If the ESQ sequencer is stopped, then everything works as you
    would expect (Octapad and ESQ can both control both DX-100 and HR-16).
    	
    	However, if the sequencer is running, then occasional Octapad
    hits will generate extraneous HR-16 note-on #69 (which is mapped
    to PERC 4, which is mapped to a wood block).
    
    	If I change pad PERC4 to MIDI note #70, the extraneous hits
    go away!
    
    	None of the Octapad pads are programmed to transmit note #69.
                                                          
    	Any ideas as to the cause?
    
    	
    	  
T.RTitleUserPersonal
Name
DateLines
1414.1Why do you do it like that??JAWS::COTERead it and weep...Wed May 25 1988 11:5512
    ..no idea why the random 69s, but it seems like you'd have
    a more functional set-up if you put the 8pad before the
    ESQ (assuming the ESQ will merge data from it's IN port
    and it's sequencer. Will it???)
    
    Then you could sequence your 8pad....
    
    No? Go away Edd? Stop giving advise???
    
    ...just a thought.
    
    Edd
1414.2Another ESQ-1 gotchaDREGS::BLICKSTEINThe height of MIDIocrityWed May 25 1988 13:0216
    Edd,
    
    The ESQ-1 does not have THRU or merge (a severe oversight IMHO).
    
    Thus if he were to put the Octapad before the ESQ-1, you couldn't
    "hear" the notes you were programming into the sequencer unless
    you either also put the HR in front as well, or set up the ESQ-1
    to play "something" in response to the Octapads inputs.
    
    The solution: get an MX-8  (I'm workin on it)
    
    Have no idea what's causing the problem though.  Also, like Edd can't
    imagine why you have the Octapad where it is unless the idea is to
    "play along" with the sequencer.
    
    	db
1414.3Dont doubt Rap Master EddCIMNET::DEBARROSWed May 25 1988 16:5612
< Note 1414.2 by DREGS::BLICKSTEIN "The height of MIDIocrity" >
                           -< Another ESQ-1 gotcha >-

    I had a similar problem with my TOM drum machine... no pad involved.
    The Tom had specific midi parameters assigned with each drum.. (snare,
    bass,hihat.. etc.  I was able to solve the problem by changing them.
    I dont know off the top of my head what they were but I can look into
    it.  I guess it was used for assigning for examp.. the bass drum to
    play everytime the bass was played on the keyboard.  But, Edd knows
    what he's taking about, trust me...

Eric
1414.4Thanks Eric...JAWS::COTERead it and weep...Wed May 25 1988 17:035
    Your check is in the mail...
    
    ;^)
    
    Whatword
1414.5MIDI Star Coup=ler...CTHULU::YERAZUNISYou&#039;re walking along the beach and you find a tortise...Wed May 25 1988 17:4923
    Reason:  Well, I _want_ to play along with the sequencer, and when
    I have a drum line that I like, I'll play it into the HR-16 pattern
    memory.  Then stop/start/tempo commands from the ESQ will (and do!)
    slave the HR-16 to the right speed.
    
    Why the DX-100 is where it is?  Because I like to play the Nuclear
    Bells DX patch from the Octapad.
    	
    	-Bill
    
    ------
    
    (I'm looking at a MIDI thru box to stick onto the ESQ....  But I
    think that what I want is more of a "MIDI Star Coupler".  Any keyboard
    transmitting is broadcast to every other keyboard- except itself.
    I could make a crappy one (no data buffering) with four CD4000 quad
    bilateral switches, two dual timers, and four op amps, but it would
    smash data any time two devices broadcast at the same time.  Yuccka.
    
    Time to sweat brain cells...
    	
    	-Bill
    
1414.6PAULJ::HARRIMANZero Tolerance = Total NonsenseThu May 26 1988 10:1113
    
    
>    (I'm looking at a MIDI thru box to stick onto the ESQ....  But I
>    think that what I want is more of a "MIDI Star Coupler".  Any keyboard
>    transmitting is broadcast to every other keyboard- except itself.
>    I could make a crappy one (no data buffering) with four CD4000 quad
>    bilateral switches, two dual timers, and four op amps, but it would
>    smash data any time two devices broadcast at the same time.  Yuccka.
 
    Why not just bite the big one and buy an MX-8????? you wouldn't
    have any of these problems and you could do all these things!!!
    
    /pjh   
1414.7LFO's don't work quite rightCTHULU::YERAZUNISSmurf _Terminator_Wed Jul 20 1988 13:4310
    Another ESQ bug (may be software rev. dependent)
    
    	Use an LFO at maximum depth to modulate DCO's frequency.
    For the lower frequencies (<30) this works fine.  Above that it
    goes into a "staircaseing" sort of effect that, although musically
    interesting, is not correct.
    
    	I know it happens on V3.5 of the ESQ software.  I don't recall
    it happening on V2.3 or V2.7  .  Can anyone out there verify this
    version dependency of the bug?