![]() ![]() If you only have a few, three or less, and you chain "in's to out's" like you mention you are probably OK. You asked multiple complex question(s) I will mainly address the external MIDI gear situation. This is ALL just my opinion and how I do things #341069 - 03/20/16 11:43 AM Re: Finally connecting my studio up - what to do for MIDI ?īefore my long winded response pghboemike hit it on the head - better help will come to you if you LIST what you have and how you plan to use it Digital Synthesizers - should all 3 be on separate disk drives, or is it OK if BB/RB and Digital Synths are on the same drive ?Ĥ.) Any other gotchas or advice when connecting so many devices to your computer ?įeel free to answer one or as many points as you like - and as always, thanks to all of you who generously share your experience. Is there recommended software/hardware for controlling mulitple effects processors and synths during live performance ?Ģ.) I have about 4 boxes that accept USB connections to my computer.Ī.) Can I use a powered USB hub to control all 4 - or would that lower throughput so that each should be directly connected to the computerģ.) Where to install BB/RB vs. Are there other practical uses - or am I studying connectivity for no practical reason Are MIDI messages to effects boxes mainly for toggling effects for different songs and different parts of songs ? Can it all be done from BB/RB ? Is there even a reason to do this ? Having never used MIDI cables to connect and centrally control all devices:Ī.) Do I simply go from my Presonus Out to a first IN, then OUT to IN - until the last box with the IN only ? Is it worth buying a central MIDI interface box to simplify connections.ī.) With what software and from where would I want to control my Effects boxes and program changes ? I have a few questions I thought you might help me with:ġ.) I have a few different effects boxes - most have only MIDI IN and MIDI OUT, one has a THRU also, and one only a MIDI IN. ![]() My central rig will be a Presonus Firepod connected to my PC, with BB/RB as the main DAW. "JLCooper MIDI Line Amplifiers are in use by some of the greatest performers in the world including Cirque du Soleil, Cavalia, Depeche Mode, Blue Man Group, Los Angeles Philharmonic, Sidney Theatre Company, Queen, Ghost, Royal Caribbean Cruises and the Juilliard Academy.I have collected various studio items over the last few decades - played around with each for a short time - never got all to work together from my computer. MLA-XLR also provides a lower cost expansion option for interfacing with other MLA-1 and MLA- 10 units in a network application with custom wiring Since the MIDI signal is converted into a non-MIDI signal, an installation requires a MIDI Line Amplifier at each end of the cable. This combination lends itself to long distance, error free installations required in professional applications with absolutely no latency. At the other end, another MLA-XLR detects the signal using a sensitive receiver that has a high degree of noise immunity. MLA-XLR takes a MIDI input and converts it to a balanced, differential signal using the RS-422 specification. While the MIDI protocol specifies a maximum cable distance of about 50 feet (more or less, depending on the type of cable and other variables), more than 50 feet of MIDI transmission requires amplification. Then, connect your MIDI gear as you would normally. Just plug in the power supply and connect two MLA- XLRs together with a pair of standard mic cables. It extends the range of MIDI to over 1000 feet using standard balanced audio lines (audio snakes, mic cables, etc.). ![]() MLA-XLR is a single channel, bidirectional, long distance amplifier or driver for MIDI signals. Touring professionals also rely on JLCooper MIDI Line Amplifiers to carry MIDI signals long distances over standard audio snakes. The need to run MIDI signals over long distance is essential for use in recording facilities, theatres, arenas, churches, schools, cruise ships, casinos, nightclubs and other venues using simple twisted pair wiring. ![]()
0 Comments
Leave a Reply. |