- #Xmplay microsoft midi mapper how to#
- #Xmplay microsoft midi mapper driver#
- #Xmplay microsoft midi mapper full#
These files can be compatible with Extended and Base but unfortunately not with Full/GM because of channel 16 as a Drum channel. You put two versions of the same song in the file - one on channels 13-16, and another on channels 1-10.
#Xmplay microsoft midi mapper how to#
Microsoft had an idea and made an 'Authoring Guideline' how to make Midi files compatible with both the Extended and Basic setups: So it is not GM compatible since GM knows nothing about drum channels besides channel 10. Unfortunately Basic setup is a weird one since it uses channel 16 as Drum channel. Extended was reduced to channels 1-10 and Basic to channels 13-16.
#Xmplay microsoft midi mapper full#
I had always selected Full and never had a problem. Full was the usual 1-16 channel mode compatible with General Midi. You could find at least 3 installed channel 'presets' called Basic setup, Extended setup and Full. Many of us remember the old midi mapper of Win 3.1 (that was much more capable than any midi mapper versions of later Windows). Let me share with you all an interesting factoid about Microsoft's Basic/Extended/Full midi device 'standards'. Vogons is the best place to ask questions like this. If with Dune_init.mid you also get the erratic sound you should ask someone with a real MT-32 what the issue can be. Dune_init.mid uses about 90 ms latency between the SysEx messages so you can try to set the same value in the 'Select/Send custom SysEx' dialog of FSMP. If it sounds good this way the problem can be the timing/buffering of the SysEx messages. Then play Dune_init.mid and right after this play Victory Atreides.mid. Set the reset type in FSMP to 'No SysEx' by right clicking the Reset button and selecting it. To narrow down where the problem can be you can try the following:
You can also test with Munt VSTi since it is included in FSMP's package. Since I do not own a real MT-32 here is the result using Munt VSTi:Īccording to this there is really a problem on your side at about 15 sec since Munt does not produce the erratic sound. Since Directsound is more mature the default is still Directsound even on Vista/7/8/10.Ībout after sec.
#Xmplay microsoft midi mapper driver#
in WASAPI output mode the 'Speaker Fill' driver level effect of Realtek HW Audio does not work. Some other subtle differences can also be noticed. With WASAPI you can achieve lower latency output that can be useful if you use FSMP also as a real time soft synth. This setting is available in the Bass part of the Device Settings dialog. Added support for native WASAPI audio output on Windows Vista/7/8/10 besides Directsound (it applies to both Bassmidi and VSTi output modes). With the help of this you can save/extract the initialization SysEx data from midi files to a syx file that can be renamed and used as a Folder.syx file.ģ. To support the above feature a new option called 'Save SysEx data from Midi' can be found in the File menu of Event Viewer/Debugger.
In these situations it can be problematic to disable all kinds of resets when playing more midi files.Ģ. CM-32L-CM-64_Initial-SysEx.mid/Dune_init.mid) is provided for many files. It can be useful in situations when only one initialization file (e.g. It works similar to Folder.sf2 that is if you put a Folder.syx file into a folder all the midi files in that folder will load the syx file before playing.