It sounds like you did a very thorough walk through of the process
and I agree, it would be a monster to try to build the algorithm to
parse a patch to reconstruct the INS script for drum key maps.

--Steve

--- In XL-1@yahoogroups.com, "Keith Young" <emigr8@...> wrote:
>
> OK I have had a little think about this. What would be useful is
to
> have the keymaps for the patches in the INS file (along with the
> Beats trigger keys, etc.) However, there are a couple of problems.
>
> Firstly, standard keymap files are not published for all the Emu
> ROMs. I have the keymap files for about 9 of them (Phatt, TSCY,
ZR,
> AOrch, Cmpsr, Protozoa, World, XLead, Orch2) but many are missing.
> Its possible that some of the missing ones might not have any
> keymaps, but others, such as the Beat ROM, certainly do and yet
there
> is no keymap file. I have looked both on Emu's site and on Rob
> Papen's site.
>
> The second problem is that Emu specify keymaps on a per instrument
> basis not on a per patch basis, which is how Sonar understands it.
So
> what I would have to do is:
>
> a) work through each patch in turn
> b) download each layer
> c) Check each instrument to see if it has a key map.
> d) Check the layer transpose to see if the keymap is offset
> e) Check the split data to see what part of the new keymap are
> relevant
> e) Merge the new keymap with what I already have for the other
layers
> (since you could have two key maps in one preset)
> f) Merge in the beat trigger information
> g) dump it in the .NoteNames section in the INS file and append a
Key
> [] reference at the end.
>
> I think I now know why none of the standard Emu .INS files have
> keymaps in them. :-(
> Keith