4 Replies Latest reply: Feb 12, 2013 11:44 AM by Blueberry
F~L~E~X~I~S Level 1 Level 1 (80 points)



Long time Unitor 8Mk2 user, with a few questions:


1. Can the Unitor take advantage of AMT (Active Midi Timing) in OSX, (or was this an OS9 feature only)?

2. Any ideas if the Unitor will be 64 Bit compatible now or in the future, & are the current 2.5 Unitor Drivers compatible with Mountain Lion?

3. I've read the Motu Midi Express is a lot tighter than the Unitor 8 - any Motu users care to chime in. (I know the Motus are USB2, compared to the Unitors USB1, but if you've a lot of USB2 connected, this could possibly negate any USB speed advantage - especially as the Unitor has it's own power supply).

4. I've also read that PCI-e audio cards (with a midi connection) are the tightest midi solution of all. The audio side would be redundant, as I'm already using Apogees, but could I run such a card alongside a Unitor?


All of the above might seem like overkill, but midi is very important to me - particularly for syncing my MPC3000. (I also have a lot hardware synths).


Any advice would greatly appreciated...



  • 1. Re: Unitor 8 Mk2 Advice...
    Blueberry Level 4 Level 4 (2,860 points)

    1. AMT

    No, it also is not really necessary, because you can connect several AMT/U8 via USB directly to your Mac, which will solve the delay between ports, too.


    2. Yes, the drivers are 64-bit for many years. Just plug the device into your Mac and Software Update will download the needed drivers automatically.


    3. I would not worry about the "tightest MIDI" so much. The delays are in so many other parts of the system, that the issues are typically not in MIDI anymore.

  • 2. Re: Unitor 8 Mk2 Advice...
    Jazzmaniac Level 2 Level 2 (425 points)

    CoreAudio has always been using AMT on OSX. And it's not just about daisy-chained devices, a single device can already have significant delays between the channels.


    Unlike audio, midi is not locked to a clock source but simply transmitted when available. The time stamped processing of AMT (or other similar systems) introduces a clock that makes sure that processing buffer granulation in audio hosts or scheduler time slices don't create timing jitter.


    This is why midi timestamping is essential for all modern DAW midi use. The default CoreMidi compliant USB driver even supports time stamping. But it's not realized in hardware but at a low granularity kernel level directly before the data goes out over USB.


    So these days midi timing is not as good as it could be, but time stamping is highly relevant for getting good results, *because* of the issues introduced by other parts of the system.

  • 3. Re: Unitor 8 Mk2 Advice...
    F~L~E~X~I~S Level 1 Level 1 (80 points)

    Thanks Jazzmaniac - good info (& good to know some still value good midi timing!)


    Ever since Logic removed the ability to sync my MPC via midi clock (with MPC as Master), this has been an issue for me. Slaving the MPC to Logic with midi clock never produces the same feel, & MTC has always been a bit hit & miss.


    In the past, I've mixed many a record with the MPC running live with Logic - & everything was supertight (though this was before the advent of softsynths & PDC). Now I like to print my MPC drums with no sync & line them up manually to preserve the feel of the MPC (though I'd still like better midi sync during the writing process).


    So any advantage using Motus over Unitors?

  • 4. Re: Unitor 8 Mk2 Advice...
    Blueberry Level 4 Level 4 (2,860 points)

    Sorry, but AMT was never used on OS X. That is a fact.


    It is also not time stamped based, but a mechanism to assure that many MIDI ports are sending out synchronized events at the same time. Today this is much less of an issue, because of the very fast USB connection (especially compared to MIDI) to the interface than it was in the past with serial ports.