Not that I need it but that is great!

This version and the beta do not work for me. It doesn't appear to actually create a midi device.

I am happy with my current set up. I use a custom Midi port via LoopMidi and PLWMidiMap to select it. Everything is working great with Midi Player VST's in DosBox, ScummVM,
GZDoom, and other programs.

Am I missing out on anything by not getting Coolsoft's to work?

brad86 wrote:

Am I missing out on anything by not getting Coolsoft's to work?

It's only a must-have for the small subset of games/apps that only use the default MIDI device and don't provide any way to pick a different device.

Why is the installer making my AV software go ape?! Maybe I should just stick with VirtualSynth as it can do the samething and doesn't seem to trigger my AV.

HunterZ wrote:

brad86 wrote:

Am I missing out on anything by not getting Coolsoft's to work?

It's only a must-have for the small subset of games/apps that only use the default MIDI device and don't provide any way to pick a different device.

It's a must have on Win8/10 since the default midi mapper is missing. As brad86 has written he is using 'PLWMidiMap to select it' so he is most likely using Win Vista/7 since PLWMidiMap.cpl only works on Win Vista/7 (but not on Win8/10).

CrossBow777 wrote:

Why is the installer making my AV software go ape?! Maybe I should just stick with VirtualSynth as it can do the samething and doesn't seem to trigger my AV.

Current versions of VirtualMidiSynth cannot do the same thing on Win8/10 as CoolSoft MIDIMapper because of the completely missing default midi mapper.
Regarding your AV problem: Nowadays AV solutions tend to be very paranoid and use so called 'reputation based' heuristics. This means programs are flagged as potentially malicious until many people use it. But it's not likely many people will use it since it's flagged... It's actually a catch 22 for small developers. More info:
http://blog.nirsoft.net/2009/05/17/antivirus- … all-developers/
https://coolsoft.altervista.org/en/blog/2017/ … mall-developers
So if you trust your software developer and use his products make him a favor and report the flagged software as a false positive to your AV vendor.

@Edit:
You must be using ESET/NOD32 since currently it's the only AV engine that detects the installer as malicious. So it's definitely a false positive:
https://virustotal.com/en/file/d62b3615b8e2b8 … 3b0fb/analysis/

@Falcosoft

I am using PLWMidiMap on the newest Windows 10 build.

Though DXX-Rebirth ( Descent Source port ) and Road Rash do not use my midi port even with overriding the selection.

This tells me that I probably do need to use Coolsoft's.

If it worked! 🙁

Falcosoft wrote:

Current versions of VirtualMidiSynth cannot do the same thing on Win8/10 as CoolSoft MIDIMapper because of the completely missing default midi mapper.

Not true, up until about a week ago, I still had virtualsynth installed and was using it on my Win10 - 64bit to select various soundfonts for use. I only eventually deleted it because I haven't been using the virtualsynth mapper much as I have my MT-200 connected up via a Roland UMONE. Additionally, I can choose the UMONE easily in the midiplayers I use and within ScummVM and Dosbox without issue. So virtualsynth wasn't needed anymore.

Could it be that Virtualsynth was working for me due to the fact that my win10 is in fact an upgraded win7? Virtualsynth was installed already when I upgraded and continued to work just fine.

Faclosoft wrote:

You must be using ESET/NOD32 since currently it's the only AV engine that detects the installer as malicious. So it's definitely a false positive:
https://virustotal.com/en/file/d62b3615b8e2b8 … 3b0fb/analysis/

Actually no...both the latest Windows defender and my latest update of Malware Bytes pro, both flagged the installer as malware. Once I allowed that to go through, then the actual midimapper configurator itself would get flagged by both and I had to add exclusions to the entire folder within Syswow64 where it installs.

@CrossBow777:

Not true, up until about a week ago, I still had virtualsynth installed and was using it on my Win10 - 64bit to select various soundfonts for use.

I don't think you fully understand the purpose of Coolsoft Midi Mapper. It's not to select various soundfonts. The purpose of midi mapper is to select different Midi Out ports as default. VirtualMidiSynth in itself is only one Midi Out port even if you can select different soundfonts in it. In Windows Vista/7 you could use VirtualMidiSynth in itself to select the default Midi Out port:

But on Windows 8/10 because of the missing default midi mapper you also need Coolsoft Midi Mapper to change the default midi out port. Without it you cannot even use the 'Midi mapper' tab of VirtualMidiSynth.

Actually no...both the latest Windows defender and my latest update of Malware Bytes pro, both flagged the installer as malware.

I suspected for a while that some AV vendors do not use the same engines when they scan files through VirusTotal. As you can see on the link I attached above both Microsoft and Malwarebytes say the installer itself is clean.
Yet they flagged it as malicious on your system. What I have said above still holds: it's definitely a false positive. Please report it to your AV vendors. Identifying something that is harmless to be malicious is a failure of the AV engine and it's not better than missing harmful files.

@brad86:

I am using PLWMidiMap on the newest Windows 10 build.

I think you have been simply lucky so far and the selected midi output with PLWMidiMap was accidentally the same one Win10 associated with Midi out port 0. Unfortunately Midi out port 0 is not definite anymore on Win8/10 (can change e.g. when you install another port). PLWMidiMap simply sets the registry key HKCU\Software\Microsoft\Windows\CurrentVersion\Multimedia\MIDIMap. But setting this key is not enough to change default midi out on Win 8/10 anymore.

I will uninstall MidiMapper tonight and put virtualsynth back in and see as you could be correct in that I only had the midi device selector and perhaps not the midi out option.

on the AV stuff, I believe a large update to Windows 10 came out over the weekend or at least I know my windows defender updated itself over the weekend or Monday night. Malware bytes just generically flagged it stating it contained malware while I recall windows defender actually stated what it was. When I researched that, I found the information about it being a false positive and that is when I eventually setup the exclusions for the installer and the folder it installs to. So could be recent updates to both of these products are flagging it again.

I will uninstall MidiMapper tonight and put virtualsynth back in and see as you could be correct in that I only had the midi device selector and perhaps not the midi out option.

You don't need to. That's how the 'Midi Mapper' tab of newer VirtualMidiSynths looks like without Coolsoft Midi Mapper installed on Win8/10:

@Edit: an older VirtualMidiSynth version may show a 'pesudo-working' Midi Mapper->Default Midi Out device section even without Coolsoft Midi Mapper installed (since it can predate the recognition of missing default midi mapper on Win8/10) but actually it cannot work for the same reason PLWMidiMap cannot work on Win8/10.