I recently condensed all my midi hardware to my Evolution UC 33 Controller. I feed my Fatar Controller to the UC 33 Midi IN. I come OUT of the UC 33 and Feed 4 sound modules by using a 1x4 THRU Box.
I have been having issues with the UC 33 and with Cubase(sending out unwanted messages etc.) I use the UC 33 as a Control Surface as well. COuld there be Too many messages coming from one device?
I have thought of purchasing a MidiMan 2x2 interface to handle my Fatar, and sound modules. Therefore, relieving the UC 33 to only be a control surface and not a Midi interface. Is it a wise choice?
Also what's the best way to setup my Midi system?
This is how I have my setup now. Let me know if you agree or if there’s a better way:
I have my Fatar Midi Keyboard connected to my Evolution UC 33(Midi Control Surface/Interface)which is connected to my PC via USB.
I then go OUT of the UC 33 into a Thru Box(1x4) Out of the Thru box into 4 sound modules.
My Fatar has 2 Midi Outputs and 1 In…I thought of having one OUT of the Fatar going to the Thru Box then the 4 modules. The other OUT of the Fatar going to the IN of the UC33..Then the OUT of the UC33 back into the IN of the Fatar.
What do you think?
Topic Tags
Comments
I only use 3 sound modules. I used to have a MOTU. I was told th
I only use 3 sound modules. I used to have a MOTU. I was told that rather than Daisy Chain the modules to get a Thru BOx. It worked great with my Tascam 428.
I did buy the MidiSport 2x2, so far it works well. I went back to Daisy Chaining the modules. Apparently going OUT of the MidiSport into the Thru box doesn't supply enough power. The Tascam and UC 33 had enough to power the thru box.
Thanks for the info!
PS. I never thought of the "Keyboards/MIdi" section of the forum. I have a direct link to this one.
Hey Munkee, About the overload in MIDI messages... I think you
Hey Munkee,
About the overload in MIDI messages... I think you should check out the documentation of your controller and find out what types of MIDI messages it is capable of sending. Then go into your MIDI filter (in SX) and turn off anything that you don't need to recieve or record. I've found in the past (esp. using older gear) that all sorts of MIDI messages can be sent from outboard gear, into my sequencer program even though I have no intention of sending the additional info. thus overloading Cubase.
Hope this helps,
mIchAEl
Hey Munkee, About the overload in MIDI messages... I think you
Hey Munkee,
About the overload in MIDI messages... I think you should check out the documentation of your controller and find out what types of MIDI messages it is capable of sending. Then go into your MIDI filter (in SX) and turn off anything that you don't need to recieve or record. I've found in the past (esp. using older gear) that all sorts of MIDI messages can be sent from outboard gear, into my sequencer program even though I have no intention of sending the additional info. thus overloading Cubase.
Hope this helps,
mIchAEl
Hey Munkee , this is more of a keyboards & midi question , but I
Hey Munkee , this is more of a keyboards & midi question , but I'll answer it the best way I can. Let me ask you , why do you feed everything off of your 1x4 midi patch bay? As far as I'm concerned , this won't work if your feeding a slew of sound modules/sources. The best way to overcome the issues that plague your setup is to invest in a multi-port "I/O" midi-interface. This will enable you to gain access to each individual midi channel & perameter base on your DAW s/w midi setup. Most programs have full midi capabilities and do an excellent job of allowing you to edit , cut , paste & etc. on the various midi tracks recorded. I would recomend looking some of the entry-level interfaces made by MOTU , MIDIMAN , OPCODE , & EMAGIC. Your choice.
[ September 14, 2003, 01:19 PM: Message edited by: dabmeister17 ]