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: VirtualMIDIsynth config tools don't work, but driver works just fine

Thank you very much for your help in fixing this subtle bug.

Well, it's an unlucky combination of multiple factors:

  • you have some other software on your system already using the CTRL+ALT+M shortcut
  • at start VirtualMIDISynth configurator tries to show an error message (Windows popup message) to warn you that it's not able to create the Mixer hotkey (CTRL+ALT+M)
  • your Language is set to German
  • German translation has a long translation for that error message (see err.hotkeyCreation in file 1031.lang)
  • Windows popup messages are limited to 255 chars (hard limit), VMS cannot overcome that limit
  • VirtualMIDISynth is not limiting the translation to 255 and it reads it as is
  • ---> buffer overrun ---> crash

I've already fixed VMS to clip error messages to the maximum allowed length and avoid crash.
Now I'll notify German translator about this issue and ask him to give a shorter translation.

Meanwhile your options are:

  • change to another language (i.e. English) or
  • edit file lang\1031.lang and set a shorter translation to err.hotkeyCreation or
  • add a [Shortcuts] section to VirtualMIDISynth.conf and add ShowMixer=0 key to disable shortcut creation

Next version will have a fix for it.
Thanks again for your help.

Posts: 7
Joined: July 12, 2017 - 19:22
Re: VirtualMIDIsynth config tools don't work, but driver works just fine

Now this build seems to point us into the right direction:

This appears if I open either VirtualMIDIsynth.exe (without the configurator) or just the configurator, causing both to crash. However, if I first open it without the configurator to provoke this error message and then open the configurator while the message is being displayed, the configurator actually works and does not crash!

Here's a dump of it, encrypted using the same password that you used for the debug build: http://devbot.enterprises/share/VirtualMIDISynthDump.zip

Posts: 1972
Joined: March 25, 2012 - 01:19
Re: VirtualMIDIsynth config tools don't work, but driver works just fine

Please replace your VirtualMIDISynth.exe with the attached one that contains debug info, then generate another .DMP file at crash time.

NOTE: I'll send the ZIP password through email
NOTE2: please zip the generated .DMP file to greatly reduce its size (7-Zip format .7z is the best one, but .zip is good too)

Attachments
1 file(s) attached
Posts: 7
Joined: July 12, 2017 - 19:22
Re: VirtualMIDIsynth config tools don't work, but driver works just fine

Odd, when manually setting the correct tab in the config (that is, if I did it correctly) it now still crashes. So the only time it worked was by accessing it through the windows "update available!" message.

I have created a dump: http://devbot.enterprises/share/VirtualMIDISynth.DMP

I hope this helps resolve the issue. Thanks for your help!

Posts: 1972
Joined: March 25, 2012 - 01:19
Re: VirtualMIDIsynth config tools don't work, but driver works just fine

Thanks for being so active on this bug report.
The suggestion on opened tab is interesting and could lead to find what's causing the crash (maybe the crash is not related to video driver at all...).

Currently opened tab is stored into VirtualMIDISynth.conf file (usually in C:\Program files\VirtualMIDISynth folder), section [Windows], key Configurator.ActiveTab with values from 0 to 5 (SoundFonts = 0, MIDI Mapper = 1, Options = 2, Shortcuts = 3, Updates = 4, About = 5).
To start VirtualMIDIStart and automatically open configurator dialog, use the proper start menu shortcut key (or start it with VirtualMIDISynth.exe --configurator option).

Tyler (<a href="mailto:[email protected]">[email protected]</a>) wrote:
Windows event log also isn't very helpful as it just states an application error when it crashes. Would it be possible to create a debug build with log output so we could run it and send the log file back to you?

When the Windows crash report dialog appears (do not close it!), the crashed process should still be in memory so you could create a dump file.
See here for details: https://support.microsoft.com/en-us/help/931673/how-to-create-a-user-mod...

Once created that .DMP file, zip it into an archive and upload somewhere (it shoud be several megabytes, so you can't attach it here.

PS: to further reduce its size, please remove all configured soundfonts by manually editing the VirtualMIDISynth.conf file.

Posts: 7
Joined: July 12, 2017 - 19:22
Re: VirtualMIDIsynth config tools don't work, but driver works just fine

So I have news. After installing version 2.2 it doesn't work again. It crashes while trying to draw the configurator window. Maybe the tab the configurator starts on simply fails to draw for some reason. This can hopefully help investigate further.

If there's some way to trigger the window to open on the update tab for example it works just fine, but I couldn't check what happens if I go to a different tab later on.

Maybe whatever crashes the configurator on the main page also crashes the base driver, so if it is the same reason that would narrow it down even further.

Posts: 7
Joined: July 12, 2017 - 19:22
Re: VirtualMIDIsynth config tools don't work, but driver works just fine

So I actually wanted to debug this issue a bit more, but today Windows gave me one of those typical Windows 10 update notifications for VirtualMIDIsynth and upon clicking on it I was greeted by this:

So for some reason just the fact that the update was available somehow managed to fix VirtualMIDIsynth temporarily. I will now install the update and see if it still works. But this info could already help finding a workaround, or even the cause for the crashes.

Anonymous user
Re: VirtualMIDIsynth config tools don't work, but driver works just fine

Can confirm exactly the same issue, persisted throughout the last recent nVidia driver updates (the configurator/GUIs haven't worked in quite some time). Currently there aren't any additional buttons or functions enabled via nVidia on my machine.

Windows event log also isn't very helpful as it just states an application error when it crashes. Would it be possible to create a debug build with log output so we could run it and send the log file back to you?

Posts: 1972
Joined: March 25, 2012 - 01:19
Re: VirtualMIDIsynth config tools don't work, but driver works just fine
Devin wrote:
Oh right, before I forget: Apparently now even the driver doesn't work properly anymore. Looks like the device shows up but the tray icon doesn't appear when launching VirtualMIDIsynth.

The systray icon is not related to the driver component, as it was in VMS1.
VMS2 driver only starts VirtualMIDISynth.exe synth component on demand (if not already started), which is in charge for the icon.
The icon appears also if you manually start VMS from the start menu.

Devin wrote:
Another idea I came up with: Is any part of the software supposed to be shown in the windows device manager?

No, it's not. VMS driver is an user-mode driver, none of the components appears in device manager.

Devin wrote:

The graphics driver I'm running is the same as on my desktop machine, where it works just fine. Have you ever heard of the graphics driver breaking it before? And would it also cause the entire software package not to work instead of just the configurator or just the synth application?

I've had some weird experience a long time ago with nVidia drivers; they had a function to add a button to each window title to let user quickly move the window to the other screen (in multiple display configurations).
Well, that feature made crash a lot of softwares I was using at that time.
It could be something wrong between VMS configurator dialog (which doesn't have anything special or "hacky" anyway) and graphics driver.

Not being able to reproduce and debug it on my side is "frustrating" ;)

Posts: 7
Joined: July 12, 2017 - 19:22
Re: VirtualMIDIsynth config tools don't work, but driver works just fine

Very sorry about that, I completely forgot about it!

I am running a GeForce GTX 1060. This device is actually an XMG P507 2017, in case you're interested in the details. It comes with SoundBlaster X-Fi MB5 software so at first I suspected that as the cause. But it worked just fine for a while.

The graphics driver I'm running is the same as on my desktop machine, where it works just fine. Have you ever heard of the graphics driver breaking it before? And would it also cause the entire software package not to work instead of just the configurator or just the synth application?

I really want to fix this issue because VirtualMIDIsynth is just so good and I can't find any good alternatives.

Oh right, before I forget: Apparently now even the driver doesn't work properly anymore. Looks like the device shows up but the tray icon doesn't appear when launching VirtualMIDIsynth. I think that's new, as it never happened before reinstalling Windows. Does it rely on any windows specific software libraries that could've possibly been upgraded to a different version by installing things like MS Build Tools?

Another idea I came up with: Is any part of the software supposed to be shown in the windows device manager? I can't find anything there so if that's indeed the case, Windows might just refuse to have the driver installed for some reason