Bob Katz needs help with MIDI patches that are offset

[MartinBaird]

Bob Katz posted what I've quoted below over on the MOTU-MAC board. I ask if he had posted here and when he said he hadn't i agreed to post it for him hoping someone could help him out. Here are the two sections he wrote:

It all started so innocently. I discovered last week that the patches for my Weiss and TC processors are offset by 1 in DP. In other words, Patch 1 actually recalls Patch 0 in the device.

Neither the Weiss nor the TC have (had) actual Manufacturer folders, .midiname or .middev files, so I must have conquered the offset thing differently in some different manner, perhaps DP defaulted to the generic default names file and perhaps I offset them in there. It's all a dim memory. I hardly ever touch this stuff and wouldn't have if I hadn't upgraded to Mavericks.

I couldn't psych that part out so I decided to copy the generic name file into a Weiss folder.

Fortunately I didn't make a TC folder yet because I broke the Weiss and haven't found a way around it. After much struggle trying to create a Weiss midnam file and a middev file I gave up. So I deleted the Weiss Folder entirely and just manually typed in "Weiss" and "DS-1" in the Apple audio MIDI setup. This has worked for me with Snow Leopard, but not today with Mavericks.

Yes, I've gone through all permutations including force quitting the midiserver process at the right time, deleting and re-establishing the MIDI device(s) in apple MIDI setup. I even time machine restored DP's prefs to this morning before I started. All to no avail. DP keeps on insisting that Weiss processor A has "no patches" and processor B has patches all with names that I never gave it that are appropriate to some synthesizer.

I'm at wit's end. If someone could help me produce a .middev file for a simple effects box and a .midnam file that will allow a program offset by 1 I will be eternally grateful. The Weiss doesn't use any

Ironically there are no manuals for this stuff. I think I used Cherry Picker once upon a time, but this has been an Intel Mac Mini for several years and whatever files I inherited from Cherry Picker were stable and peachy until Mavericks came along! And apparently Cherry Picker is not available for Intel. Is there any patch librarian I can use which will generate these files for Intel?

Sorry for the long post. I'm desperate. I have to work today and tomorrow and I'm really stuck.

He also wrote:

I would be satisfied with a generic name file with just patch names from "patch 0" through "patch 127", no banks, no control voltages, just program changes 0 through 127 that'll work. When I try to remove the bank selects, etc. from other existing XML files, it all breaks down and Audio MIDI setup does not recognize the file pair. And I'm not a novice with XML, I know how to pair up < xyx > and </xyz> and I've done that correctly as far as I can see. But somewhere obviously I've generated a syntax error, no matter how hard I try, and it's been 8 hours today! MIDI files are very complicated and delicate, it seems.

The only progress I've made has been learning that I have to define the patch list within DP's bundles. But if the patch list doesn't show up, it won't help me. There doesn't seem to be any librarian that'll work. I just paid over $150 for MIDI Quest 11 Essentials but it doesn't have the ability to create simple instruments from scratch, only to make instruments it knows from its library, and I hesitate to pay another $200 for the high end version just to create a simple XML file!!!!!

So sorry that Cherrypicker has died, no Intel version.

So sorry, any help will be appreciated,

Bob Katz

Thanks to anyone who can give him a hand.

Martin Baird

[NazRat]

There's a 'Default Names.midnam' file that he may have edited or copied it to another device name and then edited. If you create a .middev file and copy the Default Names file to something with the same name as the entry in the middev file and edit it for the patch offset, that might get you there.

[damiensalancon]

Hi, this reminds me of a similar problem i had, long long ago, on mac os9 and free MIDI. There was some kinf of tricky protocol from roland i think, that would actually call patch 1 "patch 0" and so forth.

I ve seena lso some weird apple devices lists in the audi/MIDI setup, where things got straigntened up updating the mac os.......

Don't know If these considerations can help............

Damien