Page 1 of 1

AVL Drum Maps

Posted: Fri Nov 01, 2019 5:40 pm
by kybos

I would like to use the AVL Drum kits in MusE. They don't quite comply with the GM standard, so I created my own drum map for them in MusE instrument editor (as MusE apparently does not support the midnam format files provided with the AVL drums). But now I have no idea how to use my drum map, it seems that it can only be used for external MIDI devices. Is there a way to do that?


Re: AVL Drum Maps

Posted: Sat Nov 02, 2019 7:36 am
by Tim E. Real
Oh, now I get it. No wonder I couldn't find any AVL midnam files.
It doesn't have any. It communicates the midnam XML data directly through LV2.
Via an extension from Ardour.
I did not know that. I have been asking if such a thing existed. Yay.

Re: AVL Drum Maps

Posted: Sun Nov 03, 2019 9:23 pm
by Tim E. Real
OK now I consider midnam support to be a high priority.

Our drum editor is sooo very important, and having automatic notes names is a must in my view.
This was already done with our fluidsynth MESS synth, thanks to libinstpatch from the swami camp.
Now we can take it to the next level.

Goal: Full support, such as:
Automatic LV2 note names, patches etc.
At least: In the Instrument Editor: New button 'Import MIDNAM file'.
At best: Direct loading of midnam files that user places in home MusE instrument folder.
Usage of any midnam file, as well as our existing map files, as a drum map.
(Our drum maps can be loaded and changed 'on the fly' without requiring creation of a new instrument.)
Upon inspection I see that midnam is pretty thorough (I thought it was not before),
it is already similar to our Instrument Definition Files.

Well, first and most important is making an XML parser. If time permits.
Interesting reading posts about the authoring of the extension.
Everyone including the author agrees using midnam XML is an ugly way, but that it's a solution for the moment.
Meanwhile the LV2 author drobilla is pondering solutions in the native LV2 way.
Stay tooned...

Re: AVL Drum Maps

Posted: Sun Nov 03, 2019 10:26 pm
by Tim E. Real
Sorry, to answer your question sort of, loading drum maps on the fly is done by
right clicking a drum track name in the track list. There is found load and save and reset etc.
Unfortunately they only work with our .map files (we have some of those), not the drum maps found in instruments.

And instruments cannot be selected for synths. (The synths define all their own instrument parameters).

I found a workaround. You say you created an instrument?
Create a drum track. In the mixer strip, select your own new instrument (where it usually says GM).
Verify: If you open a part on that track it should show all your custom drum note names you entered in the Instrument Editor.
[ Edit: ] Remember to select the appropriate patch since our instrument editor drum maps are per-patch.
That's what makes them incompatible with our older .map files.

Now create your desired synth track and drum track to drive it, if not already done.
Now select that drum track in the track list.
Now right-click on the other drum track and click "Copy track's drum list to all selected tracks".

Seems to (still) work here.

Re: AVL Drum Maps

Posted: Mon Nov 04, 2019 6:00 am
by kybos
Thank you, that helps a lot. I hadn't noticed the additional entries when right-clicking on drum tracks, I think the maps will serve the purpose well. I will also try the workaround when I am at home.
Support for midnam would be nice. They seem to be kind of semi-standard for instrument definitions (apparently they are supported by Ardour and QTractor, originally coming from FL Studio, from what I understand).

Re: AVL Drum Maps

Posted: Thu Nov 07, 2019 12:10 am
by Tim E. Real
Don't throw away that instrument you took the time to create.
Got some help for you. Please see announcement here:


Re: AVL Drum Maps

Posted: Thu Nov 07, 2019 5:28 am
by kybos
That sounds fantastic, thank you!