You are here

Home › Forum home › VirtualMIDISynth › Announcements & news › VirtualMIDISynth 2.x - Release Candidate 2 released ›

VirtualMIDISynth 2.x - Release Candidate 2 released

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 !!!

Pages

notator
Posts: 43
Joined: June 5, 2015 - 12:43
Re: VirtualMIDISynth 2.x - Release Candidate 2 released
by notator » February 7, 2017 - 13:20
Kaminari wrote:

I don't remember ever being able to change the MIDI device in FF/Chrome, how do you do that? The MIDI selection is supposed to be automatic in the browser, and it relies on your MIDI system settings (through CoolSoft MIDI Mapper for example).

Its done using the Web MIDI API and Javascript.  The Web MIDI API provides a list of the available input and output MIDI devices (including VMS if its installed) to Javascript programmers. The devices can then be added to ComboBoxes on the web page. Here's how that looks on my site: http://james-ingram-act-two.de/open-source/assistantPerformer/assistantP....

Chrome supports the Web MIDI API out of the box. FF's implementation is in the pipeline. FF + the Jazz plugin is supposed to work, but that's also currently a bit of a problem... -- Another reason why I suspect that Norton or Windows 10 is messing things up. FF+Jazz was working fine here a few weeks ago.

BTW: I reinstalled VMS again this morning, and it has survived quite a few restarts so far...

http://james-ingram-act-two.de/

Kaminari
Posts: 19
Joined: June 16, 2016 - 19:07
Re: VirtualMIDISynth 2.x - Release Candidate 2 released
by Kaminari » February 8, 2017 - 08:13

Ah, thanks for the heads up. I installed Jazz in Chrome and FF some years ago, but completely forgot about it as it's not particularly used (unfortunately). I tried your website implementation with Chrome and it works nice on my setup. VMS is recognized and functional. In FF however, none of my synths are detected. Of course the old Netscape plugin has become invalid...

notator
Posts: 43
Joined: June 5, 2015 - 12:43
Re: VirtualMIDISynth 2.x - Release Candidate 2 released
by notator » February 8, 2017 - 11:18

Great to hear that its working on your setup. Thanks for testing.

VMS was working fine here (in Chrome) all day yesterday, but it was gone again (in Chrome) this morning.

C:\Program Files\VirtualMIDISynth was still there, complete with VirtualMIDISynth.exe. VMS was also accessible from the Windows tray.

So I disabled Norton, ran the VMS installer again, restarted Windows 10 and Chrome... Lo and behold! VMS appears in Chrome's list of MIDI output devices.

With Norton definitely enabled, I rebooted Windows 10 again. Chrome is still finding VMS. Its very strange. Maybe I should file a bug with Chrome? Or Windows? or Norton?

FF is a separate problem. As I remember, the FF+Jazz requires the use of Chris Wilson's WebMIDIAPIShim, and I've stopped using that. I'm waiting for FF to finish their proper Web MIDI API implementation. That project is quite old but active, so I have hopes that it won't be too long before they go public with it. See https://bugzilla.mozilla.org/show_bug.cgi?id=836897

http://james-ingram-act-two.de/

coolsoft
Posts: 1978
Joined: March 25, 2012 - 01:19
Re: VirtualMIDISynth 2.x - Release Candidate 2 released
by coolsoft » February 8, 2017 - 11:33
notator wrote:
VMS was working fine here (in Chrome) all day yesterday, but it was gone again (in Chrome) this morning.

When VMS is not available you should check if:

  • file C:\Windows\System32\VirtualMIDISynth.dll exists
  • file C:\Windows\SysWOW64\VirtualMIDISynth.dll exists (only on x64 OS)
  • registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 contains a midi* key with value VirtualMIDISynth.dll
  • registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32 contains a midi* key with value VirtualMIDISynth.dll (only on x64 OS)

This is the requirement for VMS to appear as MIDI device on the system.

If one of these steps fails you could try to find who's removing it by changing file/regkey access permission and disallow delete/change to everyone... something will throw an error ;)

If all of the steps are successful (and VMS is still missing) open a MIDI player like VanBasco and check if VMS is listed in available output devices; if yes, then the bug relies to Chrome.

notator
Posts: 43
Joined: June 5, 2015 - 12:43
Re: VirtualMIDISynth 2.x - Release Candidate 2 released
by notator » February 8, 2017 - 11:46

Thanks, coolsoft, for the tips. I'll definitely follow your advice next time VMS disappears!

Will keep you posted here. :-)

http://james-ingram-act-two.de/

D.J.
Anonymous user
Re: VirtualMIDISynth 2.x - Release Candidate 2 released
by {D.J.} » February 9, 2017 - 00:16

When I opened the virus report, I saw that the file on the download page has a virus.  Will that be corrected?

coolsoft
Posts: 1978
Joined: March 25, 2012 - 01:19
Re: VirtualMIDISynth 2.x - Release Candidate 2 released
by coolsoft » February 9, 2017 - 08:37
D.J. wrote:
When I opened the virus report, I saw that the file on the download page has a virus.  Will that be corrected?

No, sorry. I mean, there's nothing I can do on my side, can't remove a non-existing virus.

That's a false positive: only Baidu marks it as infected out of 53 AV engines, and it's like that till Oct2016.
Since each AV has its own procedure to report false positives, and some of them requires registration, that's something I can't manage.

I also wrote a blog post about it here: http://coolsoft.altervista.org/blog/2017/02/false-positives-are-plague-s...

notator
Posts: 43
Joined: June 5, 2015 - 12:43
Re: VirtualMIDISynth 2.x - Release Candidate 2 released
by notator » February 9, 2017 - 10:03

I have now told Norton (my Anti-Virus app) to ignore both the VirtualMIDISynth.dlls.

I'll be very surprised if I have to report their disappearance again here. Thanks again for your help.

http://james-ingram-act-two.de/

retrue
Posts: 41
Joined: November 6, 2015 - 12:32
Re: VirtualMIDISynth 2.x - Release Candidate 2 released
by retrue » February 10, 2017 - 15:24

Hi.
Long time without posting but I still check this forum regularly.
I installed today the RC2 and so far it works without problems. But I have a doubt. Do I need to install Coolsoft Midimapper too? My OS is Windows 8.1.

Kaminari
Posts: 19
Joined: June 16, 2016 - 19:07
Re: VirtualMIDISynth 2.x - Release Candidate 2 released
by Kaminari » February 10, 2017 - 21:12

You should install CoolSoft MIDIMapper on every system ^^

On Windows 8+ where the whole MIDI mapper layer has been removed, CoolSoft MIDIMapper is required if you want to be able to manually choose your specific MIDI synth in your programs (in case you have several synths installed). Otherwise Windows will pick up one synth randomly.

Pages

Reply to existing threads: no
Edit own posts: no
Add attachments: no
Download attachments: no

Login

Support me

Click here if you want to support CoolSoft using PayPal

or Buy me a coffee