![]() ![]() MIDI track 1 sends to UM880 MIDI port 1, MIDI track 2 sends to UM880 port 2 etc. Each MIDI track sending MDI data to each of the UM880 MIDI ports i.e. In Logic X I set up 8 “external instrument” MIDI tracks, 16ths, for 84 bars, at 160 bpm. ![]() I’ve carried out the multi port test on the MIO 10, but first i’ll just recap how the Edirol UM880 behaves in the same test. So far the iConnectivity MIO 10 seems to be achieving the same "Atari STesque" tight MIDI timing as I found with the Edirol UM880 Hope this info is useful as the UM880 is only available second hand, and they don't come up too often. When time allows i'll run some further tests with the MIO 10, sending MIDI data to all 10 MIDI din ports at once, and checking to see if all note ons and offs line up with each other. (The slightly higher peak jitter when using lower buffer sizes is an issue with Logic X, and not down to the MIO 10, and this was also displayed when I tested the UM880.) I ran 6 tests of 16ths at 160 bpm, 84 bars with a buffer size of 512:Īverage RMS jitter of 0.04ms with average peak of 0.26msĪnd then 3 tests of 16ths, 160bpm, 84 bars with a buffer size of 32 samples:Īverage RMS jitter 0.04ms with average peak of 0.4 ms There is some iConnectivity software to set up the interface, and label ports etc but I didn't bother with that and just plugged it in, and it shows up fine in OSX Audio MIDI set-up, and the MIDI din ports also in Logic X 10.3.2 So I've just done some basic testing to see if it needs to go back within the 30 return period. Having added a few more synths to my set-up, I was in need of a couple more MIDI out ports, so I have picked up one of the iConnectivity MIO 10, 10 in x 10 out MIDI din port interfaces. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |