Hardware: We have drivers for our FireWire audio interfaces, USB MIDI interfaces, and PCI-324 & PCI-424 cards to operate under Mac OS 10.4 ('Tiger'). The minimum drivers required under 10.4 are:. FireWire: 1.25. PCI-324 & 424: 1.08. USB MIDI: 1.31 Go to our for the latest drivers. Software: Digital Performer 4.52 and Unisyn 2.11 are already Tiger compatible - no updates are required.

1. Motu Unasyn 2 11 For Mac Download

However, please see if you are updating a Panther (10.3) or Jaguar (10.2) system to Tiger. MX4 requires, which is a free update for MX4 v1 users (a v2 download is available on our downloads page). AudioDesk 2.04 and MachFive 1.2.2 or higher are required for Tiger compatibility. Symphonic Instrument, Ethno Instrument, Electric Keys, BPM, and Volta are Tiger compatible as of their initial releases. Please see our for more info, and our for the latest updates.

Quote What are the system requirements for Unisyn 2? System Requirements for Unisyn 2 Unisyn version 2 has the following system requirements: For Mac OS 9 and earlier: PowerPC G3 CPU or faster 2 MB RAM or more Mac OS version 8.5 to 9.2.2 CD-ROM drive for installation and authorization For Mac OS X: Unisyn version 2.1 or later is required PowerPC G3 CPU 233 MHz or faster, including all PowerPC G4 and G5 CPUs.

Not supported on Intel-based Macs. 128 MB RAM or more Mac OS X version 10.2, 10.3, or 10.4; v10.2.4 or later is recommended. Mac OS X v10.5 or later is not supported CD-ROM drive for installation and authorization. Quote Unisyn 2.1.1 for OS X a review by M.G. (Shooshie) Roberts (edited June 3, 2005-see below) There was a time when MIDI synthesizer librarians were dedicated to individual synths, each one costing more than anyone wanted to spend, but the practicality and ease they brought to the programming of those old MIDI boxes made them essential to anyone who had tried programming through the awkward interfaces on the front panels.

Still, in a studio with many synths, the expense piled up rather quickly, as did the key-disks and the inconvenience of dealing with so many pieces of software which essentially did the same thing, just to different MIDI boxes. So, it was only natural that someone should come along and unify these applications into one librarian that could do it all. Mark of the Unicorn introduced Unisyn, their UNIversal SYNthesizer librarian, in the mid-1990s to high acclaim. While it did not fit any particular synth as smoothly as the dedicated apps that preceded it, the advantages of programming all of your synths in 'unison' greatly outweighed the minor, mostly cosmetically exposed seams in this amazing workhorse of an application.

Opcode introduced its all-in-one librarian called Galaxy around the same time. Sadly, Opcode and all its librarians are now history. Unlike its more famous MOTU cousins, Performer and Digital Performer, Unisyn did not go through a lot of revisions. During its entire tenure in the 'Classic' Macintosh era, up through OS 9, it only made it up to version 1.5. During the massive Mac-Exodus from OS 9 to OS X, Unisyn version 2.0 was first released for OS 9, as a Carbon app (cross platform), but its OS X counterpart took well over another year to be released. Happily, the wait was over in mid-February of 2004, when Unisyn for OS X began shipping with very little fanfare, 9 months after the release of Digital Performer version 4.0.

Motu Unasyn 2 11 For Mac Download

With a rack of synths, I was greatly relieved to get it, and I have been using it ever since. Fully Core-MIDI compatible, Unisyn filled a gaping hole in available music applications for OS X. Unisyn can handle hundreds of synths-theoretically an infinite number, since it has an interface framework in which an independent developer writes a 'Profile' of any given synthesizer which tells Unisyn how to talk to that device. Unisyn comes with over 250 profiles, which means you can run a lot of devices with one application. Each synth's profile operates on the same principle: download banks of patches/programs/setups etc., from your synth. Store them in editable files. Edit patches in a graphic editor that makes programming your synth at least tolerable and not a hair-pulling, nail-biting experience as is so common when attempted with those tiny windows on synthesizer front panels.

Unisyn stores these banks in groups organized by device. (K2600, Proteus 2000, DX-7II, etc.) These stored banks or 'snapshots' become your reference points.

Create a new document, which is generic for all devices, and you can drag & drop banks from your snapshots to your new document in order to create searchable meta-libraries containing all your patches/programs/setups. Unisyn knows what they are, where they go, how to catalogue them, how to keyword them, and in cases where a program or patch has dependencies, Unisyn automatically finds those and keeps track of them, too. You can create a library of instruments for certain projects. Or make one for each instrument type (guitars, basses, brass, etc.). Or, you can just put them all in one big library and use the search command to find individual instruments as needed for upload. 'Upload,' meaning, send them to your device and load into an available slot.

Unisyn makes it easy. With Unisyn 2, prior experience is not necessarily an advantage. In version 2, I learned that MOTU had combined some of the windows of past versions, greatly simplifying the storage and retrieval of files.

Expecting the learning curve for the new version to be steep, I found that it's really not. I kept trying to make it more complicated than it was, looking for things that were no longer there. Where did they go?

Simplified & consolidated. The change really wasn't all that much, I guess, but it made Unisyn much friendlier. For example, the old version had separate filetypes for banks, libraries, patches, performances, and setups; those are just the ones I can remember. There may have been others. There seemed to be some redundancy back in those days, along with folders full of files that were hard to identify. The new Unisyn only has one filetype, and it seems to use fewer files in general. The windows are more context-sensitive, and people who know the arcane complexity of MIDI will respect all that goes on 'under the hood.'

It's very transparent to the user, leaving you free to think about your sounds and music, rather than file management and complexities. Nevertheless, if you need to edit your patch in hexadecimal, there is a built-in hex editor in Unisyn, and you can watch your MIDI transfers through a MIDI in or MIDI out monitor window. The effectiveness of Unisyn's Synth Profile method varies from device to device. For my Yamaha gear the model works beautifully. I can get or send individual patches in one (or two) click(s) at any location in a Yamaha device like the TG-77. On the other hand, the developer of the Kurzweil 2600's Unisyn profile programmed it such that individual programs (patches) can only be loaded to the K2600 via Program #600.

He had his reasons, due to the 2600's design, but I'd like to be able to send/receive individual programs to any slot. Other operations (sending and receiving banks, for example) work normally for the K2600, and entire banks download or upload in a short time. While every synth may have its own peculiarities, they all still work pretty much the same way. To guide you through the process, each Synthesizer has a help-file (accessible under the 'Help' menu) which explains the peculiarities and procedures for that particular instrument. Unisyn is not merely a librarian, but also a patch/program editor. You can access most or all of the programmable functions of a patch within the editor, create whole new libraries of brand-new sounds-even generate 'random' patches, then upload them back to the device as banks or patches. Very handy, of course, as anyone knows who ever spent days hacking through the little window on a synth, navigating button menus and sliders or dials.

A graphic interface on a computer monitor is unbeatable for editing synths! The era of powerful processors has brought with it a new era of software sound modules, but the support for external MIDI boxes has not diminished very much at this point. If you still believe in rack-mounted instruments and large quantities of outboard sound modules, as I do, you need Unisyn. It's not just a convenience; it fulfills a MIDI studio. In addition to organizing, naming and editing your sound patches/programs, Unisyn will also help you manage your patchlists in Digital Performer, audition sounds (even play them with mouse keys), and search for patches using a powerful search feature that uses multiple criteria to find specifically what you want. Unisyn also provides keywords that greatly assist in this process, and of course you can create your own keywords.

Unisyn isn't without its flaws, though most of them are just annoying rather than seriously troubling. Its windows seem to have a propensity to get stuck underneath the menubar at the top of your screen, and there is no place from which to grab them to pull them back down again. It is very frustrating until you discover the 'zoom' command under the Window menu. (First, resize the window by dragging the bottom-right corner. Then click 'Command- ' and the window pops right back into place.) Windows do not respond to scroll wheels, making them only scrollable with the mouse. Even the page-up and page-down keys are not operable. It's amazing how little oversights like that can cheapen an otherwise amazing application.

A useful additional feature, for future versions, would be a counter which could count the number of patches or other objects in a selection or in a window. When creating new banks, it can be tedious to count your patches. We can hope for improvements; I've asked for some, as I'm sure others have.

So far, Unisyn 2.1.1 has been completely stable in OS X. (10.3.5-Panther, as of this writing) No crashes, no freezes, just 100% reliability.

THAT is a beautiful feature! Unisyn lists for $295, but the street price is closer to $195, and while that may seem steep, don't forget that it is a universal librarian, replacing what in the old days would have been dozens of individual librarians.

Given the time-saving functionality, reliability, and back-up facility it adds to any MIDI studio, the price seems almost negligible. Out of five stars, I'll take one off for the niggling little details mentioned above, but I have no qualms giving Unisyn my highest recommendation. EDIT It's now June of 2005, and I feel compelled to alter my review a bit. One thing I never used in Unisyn was the ability to manage patch-lists in Digital Performer. The way I work, it's not necessary.

But I've been trying to help others do this, and I've learned that Unisyn simply does not do a good job of this. Hit or miss, there's no consistency to it. MOTU has only hinted that they may be aware of the problem. It is certainly not high on MOTU's priority list to fix it.

Other things also need fixing: scrolling with the scroll wheel does not work at all. There are many interface shortcomings; I won't list them now, but Unisyn could use an overhaul.

One particularly annoying bug causes the windows to get stuck under the menubar. Most windows can be retrieved by resizing them, and then using the 'Zoom' command in the Windows menu. But the Search window is permanently stuck on my copy. I guess I could reinstall. I'm finding that most people who use Unisyn do so for the patch-list management feature (which doesn't work), so MOTU has acquired a group of unhappy customers. I wish to convey my apologies for recommending Unisyn without having covered that aspect of it, but having apologized, I also should add that it's just not something I use.

I load 'custom banks' for each type of musical work that I do. Hp drivers for apple mac. The patch choices in my Digital Performer files never change. That is, a given track will always output to the same patch number. So, when I experiment with different instruments for the same tracks, I don't change patches in Digital Performer.

Instead, I load a whole new bank into my synth, with the desired patches inserted into the desired slots. Because of this method of working, I never used the Patchlist Manager. You may find this method of working satisfactory, but most people probably won't. Consequently, I encourage everyone to write or call MOTU and ask them to fix patchlist management in Unisyn.

I am revising my rating for Unisyn, knocking it down from 4 stars to 3 stars out of 5. I'll raise it if and when MOTU releases an improved version.

(Hear that huge sucking silence coming from Cambridge? That's the sound of Unisyn being ignored.

) -Shooshie (June 3, 2005) /EDIT Product: Unisyn Rating:. 째 째 (3 out of 5 stars) List Price: $295 Street Price: about $195 Platform: Macintosh Operating Systems: OS 9 and OS X Maker: Mark of the Unicorn (MOTU) 1280 Massachusetts Avenue Cambridge, MA 02138 Reviewer: M.G. (Shooshie) Roberts Dallas, Texas October 21, 2004 Feel free to quote from this review as needed, or to use it in its entirety for commercial or any other uses, under the condition that you properly credit the author (just 'Shooshie' will do in most cases), including city and date.

Thank you. June 03, 2005, 09:14 PM: Message edited by: Shooshie. Quote List of Supported Instruments in Unisyn as of February, 2004. (others may have been added since then; contact MOTU if you need one not listed, and they probably won't help, but if they get enough requests, they might.