Page 1 of 1
Digital Performer not finding newly created Unisyn patch
Posted: Tue Jan 04, 2005 4:07 pm
by Thomboy
hey Guys,
Thanks for all your help getting me started with Unisyn. I've been able to get all of the patches from my synths into Unisyn. Digital Performer isn't finding these patches however. If I pull up a patch list in the tracks window, I always get the factory default list. The Unisyn manual seems to suggest that DP will get the Unisyn ones automatically. Anyone have any suggestions? Am I missing a step.
Thanks again,
- Thom
Re: Digital Performer not finding newly created Unisyn patch
Posted: Tue Jan 04, 2005 5:03 pm
by Shooshie
I can't really help you on that one. I don't work that way; I don't use patch lists in DP. But Cherrypicker might be of some help. I really haven't used it, but some say it's good for fixing patch lists. I think there are some discussions about it, and links, if you look around in this Unisyn forum. Also, check the DP forums here and at
OSX Audio. There have been many discussions about patch lists in DP. Just do a search on "patch list."
Shooshie
Re: Digital Performer not finding newly created Unisyn patch
Posted: Wed Jan 12, 2005 6:01 am
by trombone17
Sometimes DP will update, sometimes it will not. And it is not a bug in DP, but in Unisyn (specifically some of the profiles). Below I have detailed the path that DP looks for Unisyn patch lists. This requires going into the library folders, so if that makes you uncomfortable, then ignore the rest of this.
Unisyn puts the updated patch lists in this path: Users/account/Lobrary/Preferences/Unisyn/MIDINameDocuments/
In the conversion to OS X, some of the profiles publish this this directory (the Korg X5D, for example) and some do not (Alesis D4). Both of these devices worked absolutely fine under Unisyn 1.5 in OS 9, but the D4 has problems in OS X. It also did not help that the D4 did not ship with a .midnam from MOTU, and it had to be custom created. If any device does not put a file in this folder, there is no way that DP can update the patch lists, because CoreAudio implimentation uses xml format, a simple list (as needed in FreeMIDI) won't do. This is also very user centric: updating the patches in one account will not update them in another account (important to know if you have multiple user accounts). I have asked MOTU if they plan to release a profile developer kit so that I could fix some of these issues with devices at the place i used to teach and create new profiles for devices that were not natively supported (like the Roland XV-2020). I hope this helps.
jtp