Error message

Access denied. You may need to login below or register to access this page.

Access Denied / User log in

Please let our ADS show!

This sites offers only FREE software and it's supported by a few advertisement boxes (no intrusive popups).
Please:

  • disable your AdBlocker by adding CoolSoft website to whitelist
  • give the proper cookie consent
  • enable JavaScript for this website

This seconds wait is to let you update your browser configuration...

Ok, I've done the required changes... now show me your content!
!!! Please enable JavaScript !!!

Quick login

Use your existing social account to login without registration: no confirmation mail to wait for, no new password to remember, quick, easy, safe.

...or use your CoolSoft account

Enter your CoolSoft username.
Enter the password that accompanies your username.
Add reply | CoolSoft

Add reply

Please let our ADS show!

This sites offers only FREE software and it's supported by a few advertisement boxes (no intrusive popups).
Please:

  • disable your AdBlocker by adding CoolSoft website to whitelist
  • give the proper cookie consent
  • enable JavaScript for this website

This seconds wait is to let you update your browser configuration...

Ok, I've done the required changes... now show me your content!
!!! Please enable JavaScript !!!
(If you're a human, don't change the following field)
Your first name.
(If you're a human, don't change the following field)
Your first name.

Warning!

You're posting your message as anonymous user.

By registering you'll be allowed to receive notifications of post replies and new threads.
Registration is really quick and only requires you to choose an username and provide a valid email address.

Click here to to register.

A confirmation mail will be sent to this address.
Your email address won't be published.

More information about text formats

Filtered HTML

  • Allowed HTML tags: <a> <blockquote> <br> <cite> <code> <dd> <del> <dl> <dt> <em> <img> <li> <ol> <p> <pre> <s> <span> <strike> <strong> <ul>
    Allowed Style properties: background-color, color, font-size, font-style, height, text-align, text-decoration, text-transform, width
  • You can enable syntax highlighting of source code with the following tags: <code>, <blockcode>, <pre>, <c>, <cpp>, <csharp>, <drupal5>, <drupal6>, <javascript>, <php>. The supported tag styles are: <foo>, [foo].
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
CAPTCHA
This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.
Cancel
Posts: 1972
Joined: March 25, 2012 - 01:19
Re: virtual midi synth won't appear in the midi output session

Just released version 2.7.0.

It adds a new feature that will check driver installation at startup and allows the user to fix it if needed.

New version can be found here.

Posts: 2
Joined: January 3, 2018 - 22:42
Re: virtual midi synth won't appear in the midi output session

Sorry to bump an old thread, but I think it would be a good idea to make VirtualMidiSynth restore the registry entries if they're not found on startup. The constant windows 10 updates are making me have to re-install this nearly every second week, sometimes more.

Posts: 1972
Joined: March 25, 2012 - 01:19
Re: virtual midi synth won't appear in the midi output session

Thanks for reporting it, it will help other users having the same issue.

Posts: 2
Joined: December 29, 2017 - 11:34
Re: virtual midi synth won't appear in the midi output session

Thanks, that pointed me in the right direction. There some hidden settings in Synthesia if you hold your Shift key while launching it. And in this hidden settings so is there one called "Midi.UseWinRTMidi" which I disabled, and Virtual Midi is once again available in Synthesia 10.4.

Posts: 1972
Joined: March 25, 2012 - 01:19
Re: virtual midi synth won't appear in the midi output session
Ragowit wrote:
I just uninstalled, rebooted, and installed VirtualMIDISynth 2.2.1 and still it doesn't show up in Synthesia as an output device. Tried to install the MIDIMapper as well, didn't help. Checked the regedit for the keys specified in this thread, and VirtualMIDI entries are there.

This is a known issue of latest Synthesia versions, checkout this thread for further details: https://coolsoft.altervista.org/en/forum/thread/581

Posts: 2
Joined: December 29, 2017 - 11:34
Re: virtual midi synth won't appear in the midi output session

I just uninstalled, rebooted, and installed VirtualMIDISynth 2.2.1 and still it doesn't show up in Synthesia as an output device. Tried to install the MIDIMapper as well, didn't help. Checked the regedit for the keys specified in this thread, and VirtualMIDI entries are there.

Running Windows 10 Home, Version    10.0.16299 Build 16299

Posts: 25
Joined: May 17, 2017 - 14:12
Re: virtual midi synth won't appear in the midi output session

Agree. Would be nice to have it documented. or perhaps even a version check on Windows each run so that upon a new version a little "ding" message like so:

VMSynth detects new Window version. If midi is not functional in any way please re-install.

A re-install over_the_top is superior to the jazz of uninstall/reboot/re-install/reboot etc.

Posts: 1972
Joined: March 25, 2012 - 01:19
Re: virtual midi synth won't appear in the midi output session
ALEX BALCANQUALL wrote:
This is usualy caused by apps not following the windows vista era+ guidlines of where store registry settings and taking advantage of registry virtualization etc as such they are not migrated by the windows migration, however I have no clue what you can you do to ensure a build to build upgrade doesn't break the HKLM items. Hopefully there is something in MSDN that says how...

VirtualMIDISynth must be registered in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 and HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32 registry keys; there's no other possible key (and it can't be registered in HKCU hive).
Sadly those keys refers to the old (but still much efficient ;)) WinMM multimedia layer that still works in Win10... I suppose they're going to dismiss it in the future.

What I think it's happening is that, after an upgrade, all of the devices are resetted (or removed) and re-installed thanks to plug&play.
But ...\Drivers32 devices are not Plug&Play so they won't survive to reset and must be manually reinstalled.

I could add a scheduled task that checks for VMS removal at each reboot and reinstalls it, but - being windows upgrades not so frequent - it seems to me like "using a sledgehammer to crack a nut".
It could become more urgent if this "reset" will happen on regular updates too and not only on upgrades; nobody reported it yet.

Anonymous user
Re: virtual midi synth won't appear in the midi output session

I am confident (though not certain) this is caused by the build to build upgrades of windows via windows update.
I am on the fast ring of insider builds and we get a new build every few days. Virtual synth no longer appears in the coolsoft midi mapper when it is running.

Running the virtual midi installation files fixes this - so perfectly viable workaround.

This is usualy caused by apps not following the windows vista era+ guidlines of where store registry settings and taking advantage of registry virtualization etc as such they are not migrated by the windows migration, however I have no clue what you can you do to ensure a build to build upgrade doesn't break the HKLM items. Hopefully there is something in MSDN that says how...

Posts: 1972
Joined: March 25, 2012 - 01:19
Re: virtual midi synth won't appear in the midi output session
lmstearn wrote:
The device order may have changed.

VirtualMIDISynth saves the selected output device with its numeric ID; it's supposed that it won't change.

It should be possible to store the whole device name instead of ID, but what if we have two devices with the same name (i.e. two external USB devices?).
Don't know if Windows will rename the second one to "deviceName #2" like it does with network adapters. Will check it out...