![]() this clearly takes up bandwidth, and effective ways to manage the filtering of different midi data types, can be important. the Motu seems to have a default whereby any midi clock data which is found on one or maybe (all) inputs (or) maybe a higher number priority physical input, is echoed to all outputs. also, there are questions about (what) kinds of data are routed where and under what conditions. It'll also have to be interfaced to a (modern) comp either via a separate USB MIDI interface or via the network port on a USB MTP AV.Īt one point I was looking for UM-880's but they were very hard to find and expensive whilst the market is awash in older MTP AV's atm.Ī lot of devices only do two way merging. The MOTU MTP II will work in a similar way to the Parallel / Serial MTP AV but it's older. Search the forum, there are discussions about it. Not all of them support Windows in which case they'll need to be upgraded with Windows compatible revision. (Shouldn't be more than U$50 or so)Īlternatively the USB MTP AV will interface straight to the computer but as Muser mentioned beware of a possible caveat with installed Eproms. It's also possible to interface it to to a comp over MIDI (assuming the comp is USB only) with something like a cheap Edirol or similar USB Midi Interface.Ĭan't go wrong at the prices Serial / Parallel MTP AV's go for on the s/h market. ![]() As mentioned the MTP AV (serial / parallel version) is a standalone programmable MIDI router & merger which can also interface to a serial port on a Mac or a Parallel Port on a PC OR be networked to a USB MTP AV for connectivity to a USB port on a comp.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |