Just goes to show what a bunch of fuckwits Apple are.
Of course, all the loyal Logic customers who had invested in AMT interfaces got sold down the river by Apple, who couldn't even be bothered to make MTS backward-compatible with AMT. Then Emagic got bought by Apple, who stopped supporting AMT under OSX as they were implementing MTS as part of core MIDI - why support two separate timestamping protocols? There was a family of AMT interfaces including the Unitor 8 and AMT8. It improved MIDI timing accuracy by pre-buffering the MIDI data in the interface, and then transmitting it against a timing clock from Logic - and it worked. But I have looked into it and have found the depressing truth.Įmagic introduced AMT in the 90s before being bought out by Apple. I found this post very perturbing, as I had believed the Unitor 8 mkII / Logic combo gave effectively the tightest timing in the business. PS i'm sure Fastlane does not have this but the others do support MTS with the latest Motu drivers. However you must have the right midi interface. The Atari being tighter than modern DAW's is a myth.
#UNITOR FAMILY DRIVER 2.5 MAC#
There would be the odd jitter amount of 2.5ms, but this was very few and far between.īTW I also tested my Atari+ Log3 and Unitor2, and found the Mac and Motu to be tighter.
However the Motu did address all midi out ports simultaneously, and with very low jitter. There was a 7ms delay between ports 1 + 8, and if you muted tracks 2-7 (ie ports 2 through to 7) the 7ms delay would decrease!!!
The Emagic was usless as it could not even send data to all ports simultaneously. My tests were 8 midi tracks of 16th notes in Logic, Ableton Live, Numerology etc each track sending to a midi out port on my tested USB interfaces of Emagic Unitor 8 and also a Motu Express 128. To cut a long story short, i've a device that routes a midi lead through to an audio jack, so that i could record pure midi data as audio into a DAW and then check timings etc in a sample editor.
0 kommentar(er)
