Hi,
I'm an independent Web MIDI developer, and have been using the VirtualMIDISynth without any problem for some time now (maybe a year or two) in various versions of Chrome and Firefox. The VMS is a great piece of software! Thanks very much! :-) I need it, firstly because its latency is so much better than the Microsoft Synth, and secondly because it lets me load custom SoundFonts. :-))
I updated to Chrome 43 when it was published a couple of weeks ago, and since then my application has been crashing.
We are currently trying to find out why at:
https://code.google.com/p/chromium/issues/detail?id=493663
My system files are somehow getting corrupted, and it currently looks as if the VMS has something to do with the problem. I've had a similar problem before on Windows 8, but not on Windows 7. This time, both OSs are affected.
As part of trying to narrow the problem down, I uninstalled the VMS from the (64bit) Windows 8 machine (#27 in the above thread). In #29, I discovered FAQ 12 at your website, and in #31 did what it said there to check that the uninstall was okay. The only problem was that the
C:\Windows\system32\VirtualMIDISynth
folder had not been deleted. Everything else, including the registry settings, was as it should have been.
I'm currently trying to restore my system files (I need to contact Microsoft again about that).
Chrome have not yet said anything about the question I posed in #27: Could this be a conflict between Chrome and the VirtualMIDISynth?
They say that "Chrome just relies on Win32 MIDI services.". Does the VirtualMIDISynth rely on those services too?
I'm out of my depth when it comes to Win32 MIDI services, but is it possible that Chrome and the VMS are trying to access the same DLLs?
Best wishes,
James