hi folks ...1st post from me, as virtually everything ive ever needed to know was somewhere in this site...(ta).
anyway...problem is as follows..( and this is going to be a bit confusing to write, but i'lll try my best:)
i have a pulsar2 + pulsar XTC installed(acting as SRB).
Connected to the Pulsar midi-in connection, ive plugged my newley bought peavey1600 midi fader control, connected to the midi-in of the Peavey1600, is a roland PCxx mdi keyboard, with all keyboard messages being echo'ed without change.
The initial plan is simply to control the faders on the Bigmixer.
Peavey setup
----------------------
All midi note from the keyboard are passed thru.
no midi filtering/mapping is enabled on the peavey1600
each of the faders are setup-correctly, each having the own controller number, otherwise unused in the pulsar system.
Pulsar setup.
---------------------
pulsar midi output is connected to :- 1) pulsar sequencer input 2) midi-in on big mixer
controller on bigmixer see CC changes when i move the peaveys faders...
So..It works right ?....well yes..for a short while then suddenly with no deliberate configuration change, several different strange thing can happen
1) FADER1 movements will ALSO control FADER3's output. (regardless of where you make the change, via peavy or via the mouse)
2) FADER3's output cannot be heard if FADER1 is not also raised. (regardless of where you make the change, via peavy or via the mouse)
this can occur on serveral diffenrt mixing channels.
removing/changing control settings (eithe in pulsar or on the peavey) makes no difference .The midi monitor shows"good" midi messages, ie the correct midi channels, message id, for each fader are as configured...restarting pulsar temporarily fixes things.
anyone got any ideas ?
thanks
joe
strange goings on with bigmixer & external midi control (pea
Hi,
It seems that the MIDI interface was getting noise (invalid command), it could causes "Locked-up". When it is happened, try to press the RESET from either sequencer (Sonar/Cubase/Logic), MIDI-Controller or Keyboard-Ctrl. To prevent this, you might use the Pulsar/Scope MIDI filtering device serially with your remoted-MIDI-CTRL, which is being used ONLY (MIDI Channels, control CC).
Hope this helps,
LHong
<font size=-1>[ This Message was edited by: LHong on 2001-09-11 15:35 ]</font>
It seems that the MIDI interface was getting noise (invalid command), it could causes "Locked-up". When it is happened, try to press the RESET from either sequencer (Sonar/Cubase/Logic), MIDI-Controller or Keyboard-Ctrl. To prevent this, you might use the Pulsar/Scope MIDI filtering device serially with your remoted-MIDI-CTRL, which is being used ONLY (MIDI Channels, control CC).
Hope this helps,
LHong
<font size=-1>[ This Message was edited by: LHong on 2001-09-11 15:35 ]</font>