Emagic Mt4 Driver Mac Os X Download Updated

Emagic Mt4 Driver Mac Os X Download

Installing a MIDI interface to work with your Mac should be an easy job, but what happens if it doesn't want to play ball? Apple tree Notes is hither to help.

Over the years there have been many ways to work with MIDI interfaces on a Mac — from simple devices that plugged into the Mac's now-defunct serial ports, to more than advanced multi-port models requiring the user to tame the at present-even-more-defunct OMS, the late Opcode'south MIDI equivalent of a middle manager. (Come up to recall of information technology, how many years has information technology been since nosotros mentioned OMS in Apple Notes?)

These days, working with MIDI on a Mac is much simpler, cheers to one of Apple's many Core frameworks in Mac OS X, Core MIDI. This is the scheme that deals with how your MIDI interfaces communicate with the computer, and how the applications running on your reckoner communicate with the attached MIDI interfaces. For the about role, information technology'due south pretty easy. When you lot want to attach a new MIDI interface to your Mac, it'due south usually a question of installing the appropriate software and plugging in the interface. In fact, with some simple MIDI interfaces you might not fifty-fifty have to install software, thanks to Core MIDI'southward built-in support for USB-form MIDI devices. But what happens when your sequencer (or other MIDI awarding) doesn't recognise the interface?

Getting The Correct Driver

This month, I helped out a friend who was having difficulties getting a MIDI interface to work with a Mac Pro. The Mac Pro was running Pro Tools and the goal was to slave this system via MIDI Timecode (MTC), using the newly fastened interface, from a Power Mac running Logic Pro. The MIDI interface in question was an old Emagic AMT8 and the Power Mac had been happily running with another AMT8 for some time without any bug.

Here you can run into the Get Info windows of the Ability PC and Universal Binary versions of the Emagic USB MIDI driver for the AMT8, MT4 and Unitor 8 interfaces. Despite the Power PC version being incorrectly identified by Finder as a Pro Tools plug-in, notice how the 'Kind' value clearly shows what architecture a commuter supports.

The drivers for the AMT8 had been downloaded from Apple's Emagic Legacy Product Support folio (which can be accessed via the old Emagic web address, www.emagic.de) and installed in the correct style. However, the MIDI interface wouldn't show upward in Pro Tools, and we confirmed that the Mac was indeed not recognising the interface by running Audio MIDI Setup (from the 'Applications / Utilities' folder) and checking to run into if the interface showed upward in the MIDI Devices page, which information technology didn't.

A correctly installed and connected MIDI interface should show up in Sound MIDI Setup equally a rounded rectangle with a blueish title bar and arrows to correspond the MIDI ports along the bottom. If you lot don't meet your MIDI interface every bit such an object in this window (as nosotros couldn't), you lot can frequently kick it into life past clicking the Rescan MIDI push button in the toolbar. Another indicate to annotation is that if the MIDI interface has been correctly recognised once by the arrangement but is now having problems, the round rectangular object by which information technology's identified in the MIDI Devices folio will be translucent.

Since the AMT8 wasn't showing up at all, the first thing I checked was the USB cablevision. It's amazing how many times a dodgy cable is the cause of a problem — and, actually, in the case of USB and Firewire cables, quite often a trouble can exist traced to the cable being too long when used with certain devices. However, even after we'd tried another cable the MIDI interface still wasn't recognised.

Given that the AMT8 was connected to an Intel-based Mac, it occurred to me that mayhap my friend didn't take an Intel-compatible driver for the interface. Cadre MIDI drivers are installed into the 'Macintosh HD/Library/Audio/MIDI Drivers' folder on your computer, and when nosotros checked this folder on the Mac Pro nosotros plant the right EmagicUSBMIDIDriver.plugin file. However, by selecting this driver and pressing Apple+I to Get Info, we were able to encounter that under the Kind heading in the General department (run into screenshot above) the file was described as 'Plug-in (Ability PC)'.

Although my friend idea he had downloaded the correct drivers from Apple's web site, it turns out that only the Power PC drivers can be downloaded from the Emagic Legacy Production Support folio. Apple tree only supply the Universal Binary drivers for Emagic's interfaces with the Logic seven.2 installer. This ways that, so far as I can tell, if you don't have Logic 7.2 and you want to apply an sometime Emagic interface with an Intel Mac, you'd better find a friend who does accept Logic vii.2!

Once nosotros had the correct version of the driver installed, the interface showed upwards but fine in Audio MIDI Setup. This underlines that it'south crucial to check that you have the correct driver, and that you tin can't always rely on the manufacturer. Some other important affair to behave in mind is that it's usually not a skillful idea to install the driver software that comes with your MIDI interface — or any slice of hardware, for that matter. The reason is that driver software tends to be updated quite frequently, especially if the product was released within the concluding half-dozen months. When y'all buy a device, it might have been sitting on a shelf for a few months, meaning that the driver software supplied with it is of a similar vintage. Downloading the driver software from the manufacturers spider web site is always a good thought, although it'south worth checking the release notes (where manufacturers often include a compatibility guide), as it'south non uncommon to find that the latest version might not be the greatest version for your system.

Vista Comes To Boot Camp

Apple recently released a ane.2 update to Boot Camp, the public beta that allows Intel-Mac users to run Windows on their Mac. This is actually a really significant update, partly because it now allows you to officially run Windows Vista natively on your Mac. Although information technology was possible to install Vista on a Mac before, it required having to hack around quite a fleck, and personally I never got a system to smoothly dual-kicking equally you can when using Boot Military camp. As with the previous version of Boot Camp, only 32-bit versions of Windows (including Vista) are currently supported, which is a bit of shame for those Mac users with 64-bit processors like the Core 2 or Xeon. But hopefully this volition be addressed in some other beta update, or in the final version of Kick Camp due to exist included in Mac Os Ten Leopard.

Filter Information technology Out

Getting dorsum to the story of trying to go the Mac Pro running Pro Tools to slave via MTC using the Emagic AMT8, we now had the interface attainable from inside Pro Tools. Still, when we started sending MTC from Logic to the Pro Tools computer via the MIDI interfaces, zilch happened. Later on checking to make sure the MIDI cables were correctly connected, the next terminate was to check that the MTC messages were being sent correctly and not filtered out along the way (meet the screenshot, right).

Here are Audio MIDI Setup (AMS) and Unitor eight Control running on a Mac Book Pro. Notice in the far-right window how the showtime four MIDI inputs are filtering MTC, stopping it from beingness received by the interface. Also notice in AMS that the Yard Box 2 is currently displayed with translucency because it's no longer connected to the computer.

Like many MIDI interfaces (specially the more expensive multi-port models), the AMT8 has the ability to filter sure types of MIDI messages. This can exist useful when you want to deliberately prevent certain devices from being flooded with unnecessary high-bandwidth MIDI information, such as timecode, but a real pain if you forget to disable such features when y'all use the interface for some other purpose. If your MIDI interface has such filtering features, the manufacturer will usually supply software to configure the filtering with your interface. As with the drivers, bank check the manufacturer'southward web site to meet if a newer version is bachelor before installing. In the example of the AMT8, Apple tree supply the Unitor 8 Command software on the legacy back up page, and although there is no Universal Binary version the Ability PC version will work fine for both Power PC and Intel Macs.

If this sounds confusing — why does the Ability PC version of Unitor viii Control piece of work on an Intel Mac when the PowerPC version of the driver doesn't? — there's really a good reason. Unitor 8 Command is a regular application and is able to run in the same way that whatsoever Power PC awarding can run on an Intel Mac, thanks to Rosetta, Apple's translation technology that converts Power PC code to Intel lawmaking. Put simply, while Rosetta works with applications, information technology doesn't work with hardware drivers.

The more complex reason (which you can feel gratuitous to skip) is that Cadre MIDI drivers aren't real hardware drivers at all. Instead, a Core MIDI driver is a blazon of plug-in that talks to a real hardware driver and and then deals with how Core MIDI sends and receives MIDI data to and from the hardware commuter. So a MIDI interface may sometimes require ii drivers: 1 hardware driver and ane Core MIDI driver. However, in practice Mac OS X and Cadre MIDI can provide a great deal of generic functionality, so that quite frequently a USB hardware device can be handled by OS X and a simple USB-class MIDI interface can exist handled by Core MIDI without requiring whatever drivers at all, equally mentioned at the beginning of this commodity.

You lot might remember from past columns nearly Rosetta and Intel Macs that if an application runs Intel-native, only Intel-native plug-ins can be used, whereas if an application runs with Ability PC code via Rosetta, that application will just see Power PC plug-ins. Considering Core MIDI runs natively on Intel systems, it can therefore only see Intel-native Cadre MIDI plug-ins. Withal, when a Power PC MIDI application is run under Rosetta (such as Unitor 8 Control), Rosetta is still able to let that application talk to Core MIDI thanks to a clever brainchild layer.

Getting back to the story, it turned out that both my friend's AMT8s had MTC filtered on the input and output ports, and one time nosotros'd disabled the filtering the Pro Tools Mac could finally be slaved to the Mac running Logic. While Core MIDI's performance is pretty transparent, hopefully this month's column volition give you a few ideas the next time you lot encounter a problem you tin't quite run into through.

The Core MIDI Troubleshooting Checklist

To summarise the steps given in the main text, if your MIDI interface isn't working correctly, acquit the following in mind.

* Attempt changing cables. If possible, effort using a shorter cable to connect your interface.

* Some MIDI interfaces are self-powered, but also have a power supply socket. If yous have a number of devices on the aforementioned USB port, you might want to try powering your MIDI interface externally, in case there isn't enough power on the USB bus to go around.

* Make sure you have the correct version of the driver required by your interface. Check for known problems from the manufacturer, and call back that the latest version may not always be the best ane to use.

* Bank check that the driver you accept is compatible with your system's architecture. For case, if you're on an Intel Mac, do yous accept an Intel-uniform driver? (And vice-versa for Power PC-based Macs.)

* Does your MIDI interface have the power to filter certain types of MIDI messages? If so, practise you have these features enabled when they shouldn't exist?