Author Topic: unisyn 2.1 for osx (2003) for powermac g4/g5  (Read 793 times)

Offline chrisNova777

  • Administrator
  • Hero Member
  • Posts: 8615
  • "Vintage MIDI Sequencing + Audio Production"
    • www.oldschooldaw.com | vintage audio production software + hardware info
unisyn 2.1 for osx (2003) for powermac g4/g5
« on: January 06, 2019, 02:44:15 AM »


http://www.mediafire.com/file/sb7qn64zguuz7bg/Unisyn_2.1_CD_ROM.toast/file

Quote
Requirements:
Mac OS 9 and earlier: PowerPC G3 or faster
Mac OS X: at least Unisyn version 2.1, PowerPC G3/G4/G5, not compatible with Intel Macs.
Intel compatibility requires 2.11 update:
unisyn_2.11.zip
(linked/attached)


« Last Edit: January 06, 2019, 03:22:19 AM by chrisNova777 »

Offline chrisNova777

  • Administrator
  • Hero Member
  • Posts: 8615
  • "Vintage MIDI Sequencing + Audio Production"
    • www.oldschooldaw.com | vintage audio production software + hardware info
Re: unisyn 2.1 for osx (2003) for powermac g4/g5
« Reply #1 on: January 06, 2019, 03:25:07 AM »
http://www.motunation.com/forum/viewtopic.php?f=10&t=6409&start=45#p455229

Quote
A few Unisyn facts:

Unisyn 2.11 will run on Mac OS up to 10.6.8. Unisyn will not run on OS 10.7 or later.

The most common cause of Unisyn not being able to run on OS 10.6 is a corrupt preference. Go to the user directory>Library>Preferences folder. Find and trash the Unisyn prefs and Unisyn setup prefs. Unisyn will now run, but you'll need to set up the devices again.

Unisyn can get and send user banks for the supported synths. With a few specific exceptions , Unisyn does not get or send ROM banks. This means that for most synths that can use expansion ROM banks, Unisyn is of no use for getting those expansion bank patchlists. Therefore in terms of patch lists, Unisyn is only useful for customized user banks.

In order for Unisyn to publish any patch list under OSX, a series of specific conditions must be met. As far as I know, only MOTU and Digidesign ever took advantage of the OSX patch list system, and Apple doesn't provide any patch lists or patch list management tools. Because of all this, getting useable patchlists from Unisyn can be hit or miss. In a number of cases, I've been able to make modifications, either to the Unisyn profile or to OSX patch list documents that allow for proper publishing. If you have a Unisyn profile that is not publishing user banks to DP, let me know directly and I may be able to help with that.

magicd@motu.com

I am not in a position to comment on the future of Unisyn as a product. I can tell you that the last update for Unisyn was 2004. Even when Unisyn was current, it was a specialized product. Many people purchased Unisyn just for patch list management, and that made much more sense with older hardware synths that had primarily user editable memories.

Writing a device profile for Unisyn is fiendishly difficult. In the past, MOTU had sent out developer kits for Unisyn profiles. We never saw a single working profile come back as a result. From my own experience programming for Unisyn, I can tell you that there is very little standardization of sysex protocols, and even within the same device, I've seen different styles of sysex programming used. Documentation for a device is usually written before the device is fully developed, so a great deal of the documentation I've seen from manufacturers is inaccurate. Developing a Unisyn profile is typically a tedious process of reverse-engineering the device, parameter by parameter.

Several years ago I spent two weeks to write a device profile for my Korg MS2000 synth. I posted all over the Korg boards asking of anyone was interested in an editor for that device. I didn't get a single reply.

So, if you are running up to Mac OS 10.6.8, I may be able to help you with Unisyn questions regarding the included profiles. As far as future updates or new profiles go, I can't make any promises on that. I don't check in on this board regularly, but I'll post back if asked. Again, my direct email is magicd@motu.com

Dave