How I got Unisyn to working G5 10.5 > MacPro 10.6
Posted: Mon May 31, 2010 10:53 pm
Just in case anybody else has any issues, a couple things that might help.
Recently I got a used Mac Pro 2.66 Quad and moved stuff over using Migration Assistant which was relatively painless for me despite the horror stories. A couple of hopefully helpful tips:
Install Rosetta with Snow Leopard
Just to get this issue out of the way, it's my understanding you must install Rosetta with the Snow Leopard in order for Unisyn to run at all.
Have latest version
I have version 2.1.1 which I believe was the last version. Earlier versions probably won't work.
Authorization
The first issue I encountered was not authorizing. That was purely user error on my part. I'm not even sure I remembered to put the original CD in the drive before I attempted to authorize. Once I did that, it still didn't authorize. Problem was I used the keycode on the inside back cover of the manual, but the keycode was out of date. I found the original sleeve for Unisyn 2.10 update CD and there was a label on it with a newer keycode which began with "US210-". Once I entered that keycode with the CD in the drive it authorized, the Unisyn splash screen came up, and then Unisyn crashed and quit! So... next...
Delete Prefs[/u]
I went here: [username]/Library/Preferences/ and found two files: "Unisyn Prefs" and "Unisyn Setup" and moved them both to the desktop. I was scared to delete them outright, but it ended up being okay. To get this working you just plain have to setup your devices again.
Next time I launched Unisyn, it got past the startup screen and didn't crash. I had to add devices again manually and pretty much all went well.
A couple of extra notes:
1) Be sure that the Device ID set on your MIDI module itself and the "System Exclusive ID" that you see at the lower right when you double click the device in Audio MIDI Setup match.
2) If you're using an MTP AV, launch Clockworks and check that you're not muting System Exclusive events on any MIDI ports for devices you wish to use with Unisyn. That was a real head-scratcher for me when for the life of me I was getting the "No Reply" error. Turns out, in a previous configuration of my studio, I had a different device on that port that I intentionally blocked Sysex messages on the output from the MTP/AV.
3) One bit of trivia. I found Unisyn doesn't care if you've connected up a device in AMS to the MTP for two way communication. It seems to work anyway. Just the same, I connected them up that way.
Hope this helps someone.
Recently I got a used Mac Pro 2.66 Quad and moved stuff over using Migration Assistant which was relatively painless for me despite the horror stories. A couple of hopefully helpful tips:
Install Rosetta with Snow Leopard
Just to get this issue out of the way, it's my understanding you must install Rosetta with the Snow Leopard in order for Unisyn to run at all.
Have latest version
I have version 2.1.1 which I believe was the last version. Earlier versions probably won't work.
Authorization
The first issue I encountered was not authorizing. That was purely user error on my part. I'm not even sure I remembered to put the original CD in the drive before I attempted to authorize. Once I did that, it still didn't authorize. Problem was I used the keycode on the inside back cover of the manual, but the keycode was out of date. I found the original sleeve for Unisyn 2.10 update CD and there was a label on it with a newer keycode which began with "US210-". Once I entered that keycode with the CD in the drive it authorized, the Unisyn splash screen came up, and then Unisyn crashed and quit! So... next...
Delete Prefs[/u]
I went here: [username]/Library/Preferences/ and found two files: "Unisyn Prefs" and "Unisyn Setup" and moved them both to the desktop. I was scared to delete them outright, but it ended up being okay. To get this working you just plain have to setup your devices again.
Next time I launched Unisyn, it got past the startup screen and didn't crash. I had to add devices again manually and pretty much all went well.
A couple of extra notes:
1) Be sure that the Device ID set on your MIDI module itself and the "System Exclusive ID" that you see at the lower right when you double click the device in Audio MIDI Setup match.
2) If you're using an MTP AV, launch Clockworks and check that you're not muting System Exclusive events on any MIDI ports for devices you wish to use with Unisyn. That was a real head-scratcher for me when for the life of me I was getting the "No Reply" error. Turns out, in a previous configuration of my studio, I had a different device on that port that I intentionally blocked Sysex messages on the output from the MTP/AV.
3) One bit of trivia. I found Unisyn doesn't care if you've connected up a device in AMS to the MTP for two way communication. It seems to work anyway. Just the same, I connected them up that way.
Hope this helps someone.