Patch list repository?

[hardingray]

Hi all,
It seems to me that we might all benefit from having a place where we can share patch lists for devices that aren't in the core DP install. I sort of remember there being a website somewhere that had user posted device patch lists. But maybe that was in my old Opcode days.

I know enough about XML and with some big help from Cherry Picker, I was able to get all of my 39 devices set up. I'd be more than happy to post the ones that I've put together if someone were to set up such a site.

Hardin

[Jim]

That's a good idea... a patch list repository.

I'm curious that you've been able to get your 39 devices working with Cherry Picker and XML. I've got some older unsupported MIDI modules myself, and I can't get no satisfaction getting Patch Lists for my Yamaha TF1 modules, Roland JX3P, and other devices that were working great under OS9. MOTU doesn't care, pointing the finger at OSX. If you could spread the love on how you were able to do this, I'd be most grateful.

.

[hardingray]

I did more of it manually because I didn't have cherryPicker until near the end, but still a combo of the two worked well for me.

I don't have all this in front of me right now, so please excuse me if I miss something...

If you haven't found them, you'll find all the device lists and patch lists in the library/audio folder of your harddrive (not the library inside your user folder, but the top level one). Do a search for something like "motif" and you'll likely find the right area.

First, you need to add the device to the device list. For many manufacturers there's a whole folder (like Roland), but for some, there's just a single file. I think it has a .middev extension. Basically I just looked through there, if the device I have wasn't in there, I'd duplicate one of the entries and modify it for the new device.

Then you need to create a .midnam file. At this point I usually would start off by duplicating another similar device's .midnam file. The most important thing is that the name you enter in the model tag is exactly the same as what you entered in the .mididev file.

From there it's a lot of copying and pasting or typing. The cherryPicker manuals should tell you how to create banks and patches.

I did find a few oddities. Occasionally I'd copy my files somewhere else for backup. I found once or twice that DP would be looking at those files rather than the ones in my library folder. The only way to trace which one it was seeing was to change one of the patch names, launch DP and see which patch list showed up.

Hope that helps,
Hardin

[Big Red]

I'd love to see such a site. I'm trying to figure out Cherry Picker...

[hardingray]

I've emailed the suggestion to the admin of this site. We'll see what they think.

If not, I don't have the ability to set this up myself, so maybe someone else out there has a way to set this up on their site?

Hardin

[Harry]

Super idea!

[robMartin]

I'd be happy to put it up on the new CherryPicker site if you like - I was actually planning something along these lines anyway!

The only thing holding the new site from going up is that I haven't finished the documentation for the new 2.5 version (which has been ready for a couple of months). I just can't write! - anyone out there want to help me get it finished?

As soon as I finish it, I'll turn the site on...

[hardingray]

Originally posted by mountebank:
I'd be happy to put it up on the new CherryPicker site if you like - I was actually planning something along these lines anyway!

The only thing holding the new site from going up is that I haven't finished the documentation for the new 2.5 version (which has been ready for a couple of months). I just can't write! - anyone out there want to help me get it finished?

As soon as I finish it, I'll turn the site on...

That sounds like a great place for it. It might be easiest if it's broken down into directories by manufacturer.

I'll offer my hand on writing the manual. I can't say that I'm completely familiar with the app, but I'll give t a shot. Also, I'm pretty busy with "real" work, but send along what you've got.

Hardin