MIDI Patch Names - From TDM Mac Forum
For information on using MIDI Patch Name files in Pro Tools, please read this document first:
Pro Tools and MIDI Patch Names There are 2 things that you will need to get a MIDI patch names file to work properly in Pro Tools - the patch name file itself (.midnam) and a MIDI Device file that includes information on the device itself (.middev). Once you have the MIDI patch name file, place it somewhere in the following folder: MacHD>Library>Audio>MIDI Patch Names> You can place it in the proper manufacturers folder inside the Digidesign folder located there or you can create a new folder - it won't matter which as long as it's in the MIDI Patch names folder it should work properly. Next, you will need to edit a MIDI Devices file to include information on the device itself. The easiest way is to copy and paste the data for a similar device within the current MIDI Devices file. This file is located at: MacHD>Library>Audio>MIDI Devices>Digidesign Device List.middev You can edit any .middev file located in this folder - you do not have to use the Digidesign file. If you open the .middev file with TextEdit, you will see a list of MIDI devices. Simply copy and paste the definition for one device, then edit the name of the copied section so that it reflects the EXACT name of your MIDI patch name file. Here is an example: <MIDIDeviceType Manufacturer="Access" Model="Virus" CanRoute="false" SupportsMMC="false" Image="OMS1039"> <DeviceID Min="1" Max="16" Default="1" Base="1" /> <Receives MaxChannels="16" MTC="false" Clock="false" /> <Transmits MaxChannels="0" MTC="false" Clock="true" /> </MIDIDeviceType> <!-- ADA --> <MIDIDeviceType Manufacturer="ADA" Model="MP-1" CanRoute="false" SupportsMMC="false" Image="OMS1026"> <DeviceID Min="1" Max="16" Default="1" Base="1" /> <Receives MaxChannels="1" MTC="false" Clock="false" /> </MIDIDeviceType> The above section is from the Digidesign Device List.middev file and shows 2 devices - the Access Virus and the ADA MP-1. Each device is enclosed by the definition tags <MIDIDeviceType> and </MIDIDeviceType> (notice the forward slash in the second, closing tag. You must copy and paste the text between and including those tags, then change the Manufacturer and Model to reflect the manufacturer and model of the midi device .midnam file you want to use. The manufacturer and model must be EXACTLY the same as what's used in the .midnam file. By copying and pasting the definition for a device that is similar to the device you're using - for instance, using the Roland JV-1080 definition for a JV-2080 - you will assure that at least most of the parameters will be set correctly in the definition. Once you've copied, pasted and altered the mfr/model, save the .middev document. You should now be able to use the patch name file properly in Pro Tools. |
Re: Using 3rd Party MIDI Patch Name files in Pro Tools
I still can't get any of the Motu patch names to work, I've followed these instructions to a tee, I've even copied and pasted all the Digi info in lieu of Motu's and still nothing.
Worse yet, not even the Digi patch names seem to work. Also, patch names that used to work have stopped working through various upgrades; I.E., the Triton Rack. This should be transparent and simple to the end user, the way it is now is just a major pain; I hope it's fixed in the next major upgrade. Ed |
Re: Using 3rd Party MIDI Patch Name files in Pro Tools
I have to agree with Ed. I've tried, several times, to get patch lists [including MOTU patch lists into ProTools]. Granted, I'm no programmer, but, I've yet to achieve success. I've called Digi Tech Support a few times regarding the issue, and have been directed to various documents available on the Digi website and elsewhere on the web. Long story short ... the workaround hardly seems clear and easy. Evidently, there aren't enough people making noise about this, for if there were, Digi would have rectified the situation by now. As a program touting advanced midi capabilities, ProTools should include more patchlists [for internal banks/expansion boards], and provide an easy method of import/conversion.
jep |
Re: Using 3rd Party MIDI Patch Name files in Pro T
I've been able to get my motif es and dx7II patch names to work. I must admit that the instructions in this thread were more of a confussion factor than a help. Are you guys using USB interface or regular midi cables?
One thing not mentioned in these instructions is that even after you have the .midinam file perfect you still have to draw a connection line in the Audio Midi setup from the midi device (keyboard) to the midi interface (002R). I had to do this to get my DX7 to work after going to the new Mac OS. If this is not done everything will work except the patchnames so it makes you think the midi setup is ok when it is not. The midi device file was already there for this unit. For my motif, the usb driver installation set everything up and all I had to do was get the manufacturer and model number corrected in the .midnam file (downloaded from digicake.com) to match exactly what was put in the audio midi setup by the driver installation program. They did not match ( of course). I never changed anything else in the .midnam file or added any midi device file. Maybe because the motif is both a midi device and a midi interface or maybe because it uses USB. Not sure which. After getting the patch names loaded PT started crashing when opening a second default program change window. You need 6.7cs2 at a minimum to fix this problem. I was able to find all of the info I needed to get the patch names to work however the info is spread out all over the place and not very easy to understand. hope this helps you guys get it working... randy |
Re: Using 3rd Party MIDI Patch Name files in Pro T
Can you explain what, exactly, is happening when you attempt to use a MOTU patch name file in Pro Tools? What steps are you taking to enable them?
After downloading the MOTU patch names, you should have a folder called "MOTU" - inside that folder are 'midnam' and 'middev' files. To enable a particular patch name document in Pro Tools, place the device or manufacturers 'middev' file in MacHD>Library>Audio>Midi Devices. Then place the 'midnam' file in MacHD>Library>Audio>Midi Patch names folder for the same device. As an example, let's take the ART Multiverb Alpha 2.0. In the MOTU folder is a folder name 'ART' - inside that folder is the ART.middev file. Put that file in the Midi Devices folder, then take the rest of the folder, which contains the Multiverb Alpha 2.0.midnam file and put that into the Midi Patch Names folder. You should now be able to use that patch name document in Pro Tools. The instructions given in the first post are ONLY used if you have ONLY the patch name document, but no 'middev' file. If you have both, as in the ART case above, there is no need to alter a middev file to indicate the new device that you have the patch name for. Keep in mind that the MOTU folder has some 'middev' files, but no patch name documents for those devices, which could possibly cause a bit of confusion. |
Re: Using 3rd Party MIDI Patch Name files in Pro T
Hi Digi,
No need to download the patchnames, they're included on the DP installer. All the patchnames are in their proper folders, the AMS has all devices enabled and patch cords connect, yet nothing works in terms of PT (although they all come up fine in DP 4.1). I've even moved the Motu folders containing the midi device and patchname files to within the Digi folders and nothing, nada. For example, I took the korg triton rack device and patchname files out of the motu folder and put them in the digi folders, alas, nothing. Again, the Korg Triton rack patchnames did work at one time, I believe it was during PT 6.2 era. Ed |
Re: Using 3rd Party MIDI Patch Name files in Pro T
Does the treatise you mentioned entitled "ProTools and MIDI Patch Names" - specifically: "Creating Custom MIDI Patch Name Files" apply to Roland JV-series Expansion cards?
I want to make sure before I begin the process of hand-typing all 751 patches from our three Expansion Cards... (I'm sure there are thousands and thousands of patch names out there from other companies, but I thought that's why we spent thousands and thousands of dollars buying the ProTools HD system from DigiDesign - so their programmers could tackle this - not us...) Thank you for your time |
Re: Using 3rd Party MIDI Patch Name files in Pro T
Having gone throught the motu/digi ringer a few times I will tell what I know- The syntax in the midi patch files is different between the two- Infact, the syntax between the patch files between PT 6.4 and 6.7 is different as well. If you take the Yamaha DX7II file and open the motu version and the digi version this will be quite clear. The only way I have been able to manage is to copy the name info from the motu document into the digi document.
charles maynes |
Re: Using 3rd Party MIDI Patch Name files in Pro T
Hi Charles,
Since you mentioned that you've been through this particular 'ringer', would you have a relatively concise, step-by-step, approach for converting MOTU patchlists to Digi patchlists, that you would be willing to impart? thanks, jep |
Re: Using 3rd Party MIDI Patch Name files in Pro T
It took me 16 hours of the most frustrating work imaginable to get device files working for all the synths in my studio. If I was not already familiar with HTML I don't think I could ever have possibly done it.
It's supposed to be a standard but once I started going back and forth between the MOTU and the Digi MIDNAM files I immediately saw that there was a very different style of formatting from each company, and of course, they are not cross-platform as they should be. I have no idea if either company is actually sticking to the "standard" but I do know that MOTU includes WAY more MIDNAM files with their software, and I know that PRoTools is incredibly unforgiving as to how the MIDNAM files are formatted, and incredibly inexact when providing feedback about errors. In my opinion this is a fiasco on the part of the music gear industry and I am amazed that they're foisting it off on the consumer. The synth manufacturers are equally at blame here. I can't understand their failure to provide MIDNAM files in light of new competition from soft-synths. |
Re: Using 3rd Party MIDI Patch Name files in Pro T
Quote:
I can't explain how disgusted I felt about the whole process as I was grinding through it. As implemented it is an absolute step backward from OMS, which is how old now? |
Re: Using 3rd Party MIDI Patch Name files in Pro T
Quote:
|
Re: Using 3rd Party MIDI Patch Name files in Pro T
MOTU sometimes inserts code into the midnam files that Pro Tools doesn't recognize. If you are having trouble using a midnam file, open the file in a text editor and ook for any NoteNameList data (including any tags) in the .midnam file and delete it.
If you have patch lists from FreeMIDI/Galaxy or other editor librarians, you may be able to use an application called 'CherryPicker' to convert them to midnam files. CherryPicker |
Re: Using 3rd Party MIDI Patch Name files in Pro T
Having changed back to softsynths due to the patch names obstacle course i would add the following wish. Digi, can you guys write a Utility that either checks the code or creates the document? DP does a pretty good job at having many instruments already created - PLEASE PLEASE PLEASE step up to the plate and simplify this process.
PLEASE! You have made inroads toward sequencing and midi but you will not win the market over (i don't think) until items like this are addressed. And this is NOT to take anything away from digisupport trying to help in the forum. Unfortunately, getting these dev files and midnams to work is like manually setting printer codes - (anyone remember those days?) best scott |
Re: Using 3rd Party MIDI Patch Name files in Pro T
It appears the situation is no different than it's been for some time. Unless there's some great, hidden, untapped source of information on the subject, it seems there is no clear method for getting third party patch lists into ProTools. I admire much of Digidesign't product development, but Pro Tools could use a little more attention from a midi perspective. In this matter, I wish that Digi had a CLEAR patchlist conversion scheme and/or provided many more ProTools compatible patchlsts. Unfortunately, I believe this thread shows that editing 3rd party lists is a task which is far from straightforward. Further, and unfortunately still, there musn't be too many people clamoring about this issue, for the situation doesn't seem to be any better.
I was anticipating a concise fix when I first saw this thread posted Could the original Digi poster let us know if anything is being done to help the patchlist situation in ProTools, or is this area of development/improvement "closed"? thanks, jep |
Re: Using 3rd Party MIDI Patch Name files in Pro T
I am amazed that this is still an issue. There are resources on the DUC that have links to sites where the user has already converted many items into Pro Tools friendly formats, but it still amazes me that in this day and age we do not have a simple utility that can read and convert from various files into a pro tools friendly format without having to actually dig in and write the tags ourselves.
Many Pro Tools updates flush your hard earned adjustments so you better make a back up now! In an ideal world there would be a simple Patch Reader perferably built into Pro Tools that would go out and read the patch name and location on your device and transmit that info to you host. This could be perhaps triggered as an update by the user so if you are over changing patches on your device, you could then hit an update button on your track in Pro Tools and update the patch list. It does not need all the bells and whistles of the old Universal Patch Librarians but it should allow updating the patch name. It behooves the manufacturers to standardize the way they transmit this info so it is easy to program the reader from within the host. |
Re: Using 3rd Party MIDI Patch Name files in Pro T
I see you detailed discuss the problem, but i got this message:
"MIDIServer patch file, bank or mode information not available for this instrument" when i try to change the patches on my XL-7 midi track. No way to find why it happens, do i have to correct the device name on the Digidesign Device List.middev or change the midnam file name or change the names into it? Is it connect to the midi configuration? any help? All i do with wavestation and Micro Q works fine and so i can't understand where is the problem. Ciao to all |
Re: Using 3rd Party MIDI Patch Name files in Pro T
edemunari - It's not quite clear where your problem is occurring. The .middev file must contain a description of your instrument, while the .midnam file contains all the patch name info. The names of the devices in both the middev and midnam files must match EXACTLY. Most likely this is the issue - check that the names in both documents match, then try again.
If you are still having problems, please describe the exact steps you're taking before you get this error. Also, where did you get the middev and midnam files from? |
Re: Using 3rd Party MIDI Patch Name files in Pro T
In library/audio/midi devices Digidesign Device List.middev file contain:
<MIDIDeviceType Manufacturer="E-mu" Model="XL-7" CanRoute="false" SupportsMMC="false" Image="OMS1027"> <DeviceID Min="0" Max="15" Default="0" Base="0" /> <Receives MaxChannels="16" MTC="false" Clock="true" /> </MIDIDeviceType> In Library/audio/midipatch names/digidesign/E-mu, my XL-7. Midnam file contain: <MIDINameDocument> <Author>File generated with CherryPicker by Rob Martin 2003</Author> <MasterDeviceNames> <Manufacturer>E-mu</Manufacturer> <Model>XL-7</Model> <CustomDeviceMode Name="Mode 1" > <ChannelNameSetAssignments> ,,, Where do the names have to match? I do the same with Wavestation but it correctly work, maybe i forgot something... Thanks |
Re: Using 3rd Party MIDI Patch Name files in Pro T
Hey edemunari,
did you try the sometimes-works-magic-but-not-often: <CustomDeviceMode Name="" > (instead of <CustomDeviceMode Name="Mode 1" >) |
Re: Using 3rd Party MIDI Patch Name files in Pro T
Mode 1 or mode "" doesn't hage the problem. It doesen't work.
But on my opinion it is related to a midev problem because PT says it can't find a patch server for my device. Have midi audio core configuration any implication with this? Please, any help would be appreciate. |
Re: Using 3rd Party MIDI Patch Name files in Pro Tools
"MIDI server patch file, bank, mode information not available for this MIDI instrument."
Ever seen this before when trying to assign MIDI Patch names? Ever wasted an hour and a half trying to fix it? Don't bother, do this. Make a note of all your Devices, their connection, settings etc... in Audio MIDI Setup because you are about to lose them by trashing the pref files Delete these two Audio MIDI Setup preference files "User"/Library/Preference/ByHost/com.apple.MIDI.000a95732738.plist "User"/Library/Preference/com.apple.audio.AudioMIDISetup.plist Rebuild your Audio MIDI Setup config. OK we're in the home stretch. 1 - Be certain that the device name and model match it's respective xml file and it's listing in the Digidesign Device List.middev 2 - Because a New PT install/update will write over your User/Library/Audio/MIDI Patch Names/Digidesign/ folder (thus losing your custom .midnam's) put the .midnam files you use in your Digi Application folder, and open THEM from PT, instead of the .midnam's in the User/Library/Audio/MIDI Patch Names/Digidesign/. |
Re: Using 3rd Party MIDI Patch Name files in Pro Tools
WOWW.... at the end i win!!!
The problem is that: YOU CAN'T CHANGE THE DEVICE, THE MODEL AND MANUFACTURER IN APPLE MIDI AUDIO CONFIGURATION, WITHOUT CANCELLING THE PATCH CORD TO MIDI INTERFACE AND YOUR MIDI DEVICE... I think you can change the device the model and so on continusly without having to cancel the patch cord and remake the connection... So much time wasted, my midnam and mididevice probably were ok many triel before i got them really work... Happy to end this work, now i can use Cherry Picker to configure avery part i need of my midnam... |
Re: Using 3rd Party MIDI Patch Name files in Pro Tools
I just posted an update to CherryPicker (2.5) at: <http://www.alterspective.com/cherrypicker> which might help with some of the problems I've seen in this thread. (it's a freeware MIDI Patchfile Editor).
It now includes a middev editor, and automatically adds entries if they are missing - and it has a "ProTools Compatible" switch that you can set in the preferences. This reformats and filters the midnam XML to ProTools implementation - so you can open up any MOTU midnam (or Cubase or OMS) patchfile, and just hit 'Save'. As with anything new, there may be a couple of glitches - so please back everything up first if you want to give it a whirl! And let me know of any problems or suggestions... (there's a feedback link on the site) Cheers, Rob |
Re: Using 3rd Party MIDI Patch Name files in Pro Tools
I just wrote a little stand-alone app that basically converts the entire MOTU folder to a ProTools compatible one in one shot, and also constructs a Digidesign middev file for all the models it finds along the way.
Trouble is, I don't have ProTools to make sure everything's working properly! The files look alright, but I'd like to make sure they run properly before I put the app out there. (I plan to put it inside the CherryPicker download). So, does anyone here have a little time available and interest in trying it out? Send me a mail if you are! Cheers, Rob |
Re: Using 3rd Party MIDI Patch Name files in Pro Tools
I have to say to Digi, considering the cost of our HD systems , it would seem you should provide a much more thorough MIDI patching, and hardware list in a future CS upgrade. I'm not complaining, i'm just bitc*ing.
|
Re: Using 3rd Party MIDI Patch Name files in Pro Tools
For those of you that use protools to make music and don't want to spend the time to create xml .midnam
files, you can probably find all the .midnam file you need at So Now you can go back and create music again. .midnam |
Re: Using 3rd Party MIDI Patch Name files in Pro Tools
Quote:
DIGI, this is an absolutely MADDENING AND APPALLING SITUATION!! WHY ARE MIDI NAMES SO GOLL DARN DIFFICULT IN YOUR APPLICATION??? you have to be a seasoned programmer to figure this stuff out!!! i recently lost my midnams that worked before and now, even i am not ALL TOGETHER stupid, i am having trouble. SONOSPHERE doesn't work, Cherry Picker doesn't work. and you provide us with midnam's from circa 1822! back in the day, i could use galaxy librarian, hook up my midi modules, select "GET PROGRAMS" what a few minutes and there they were. but that was OS7! can you please explain to us why you cannot provide us with a simple librarian that doesn't require an advanced degree in C++? can you please put a downloadable database at your site with manufacturers midnams that are UP TO DATE? surely someone at DIGI can do this for us. the instructions are at your site, just follow them. thank you for listening. sorry for the tone. now, back to work. |
Re: Using 3rd Party MIDI Patch Name files in Pro T
Could anyone here direct me to a workable midnam for a Roland srx-06 expansion board. I found one for DP but Pro Tools just doesn't want to work with it.
Any advice appreciated. JH |
Re: Using 3rd Party MIDI Patch Name files in Pro T
I got these digidesign device list which had already edited, that you need to make your expansion board accessible through PT , but my expansion boards are only srx 01/02/04/10 and some old srjv module(orchestral2, hiphop, bass n drums), i got my 06 but not using it right now so i don't make the list for it. But all of theme are use on my XV-5080. If you have the same module, just take the list from DP instrument list and follow the pattern that i made in my XV.midnam. If you want the files, or any body want it, i got instrument def for Triton Extreme (Tom Morgan-thx) also, just let me know. Thx
Music is all that you need [email protected] |
Re: Using 3rd Party MIDI Patch Name files in Pro Tools
Is there somewhere on this site or out on the web where the tags and attributes in the device list file are defined? In other words, is there somewhere where I can find out how attributes like IsSampler="true" or CanRoute="true" are interpreted and where I might find other attributes. Surely someone has a list of these somewhere...
|
Re: Using 3rd Party MIDI Patch Name files in Pro Tools
The midnam and middev specs were put together by the MIDI Manufacturers Association, so you might want to check their site; but, the last time I looked, there was no info.
I wrote a middev editor as part of CherryPicker (2.62) and basically used all the tags I'd come across in looking at whatever files I could find put out by MOTU, Digi, and others. My gut tells me that none of the apps that use midnam/middev actually respond to 99% of the values in a middev file - all they really care about is that the file exists, and that its name/manufacturer correspond to the midnam - which contains the name info. They might also respond to the bank select switches. The basic problem with all the midnam/middev stuff is that each DAW implements a different subset - and none (AFIK) uses all of the available tags. MOTU files are not always compatible with Digi etc. I wrote an app called CherryMangler that converts an entire MOTU folder into a Digi compatible one - it also generates a Digi middev file. If you use this, you can use CherryPicker to add expansion patch names to just about all synths, since MOTU includes them in their distribution - and there are many sites where you can download the MOTU folder. I'm not trying to plug CherryPicker, since I put it out as basically freeware - but you might find it useful to look at the documentation (which is on-line) where I try to explain some of the nuances of midnams/middevs. (www.alterspective.com/cherrypicker) Cheers, Rob |
Re: Using 3rd Party MIDI Patch Name files in Pro Tools
Rob, your applications are so great and usefull that DIGI should consider them very highly.
DIGI, I have just a regret, no more synt editor on the market, and the very few that are, support only librarian function for some grat synt and with just only interaction with prootools. Thanks Rob for helping us a lot. |
Re: MIDI Patch Names - From TDM Mac Forum
I have been many hours typing the name patch names of my Kurzweil K2600, because the system don´t have the expansion ROM names. Now the file don´t run. P
Please could somebody send to me the file ¨Kurzweil K2600.midnam¨ I forgot to make a copy and now I have nothing to control my synth names. [email protected] Thank you!! |
Re: MIDI Patch Names - From TDM Mac Forum
I found a much needed Midi patch name file for my Korg TR Workstation here.
Thanks to the site and Hugo for working on this. JRPJazz http://www.digicake.com/midnam/ |
All times are GMT -7. The time now is 07:04 AM. |
Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com