Virtualmidisynth not closing when closing midi player

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 !!!
Posts: 2
Joined: 18 Dic 2014 - 20:15
Virtualmidisynth not closing when closing midi player

Dear Sirs,

I recently came across two issues when using the latest Virtualmidisynth
(awsome softwareby the way) with my Notation Composer (ver 3.0.1):

1. When closing down notation composer it looks like virtualmidisynth is not
closing down (It used to do so as far as I am aware). When I open my Notation
Composer again it starts up a new instance of virtualmidisynth. So eventually
I end up having several instances of virtualmidisynth running in parallel
taking up resources in my PC.

2. When using the virtualmidisynth as the midiplayer for Notation composer
there seems to be a resources issue (e en if only one instance is open, i.e.
when trying to open or save a file all folder icons are blacked out and
sometimes I can't even manage to safe a file. The issue disappears when I use
my default windows midiplayer.

Not entirely sure if this is related to the virtualmidisynth or Notation
Composer software, but it seems to have appeared with the latest
virtualmidisynth release 1.12.0

I'm using a Toshiba laptop P50t with a 4K resolution display
Windows 8.1 (64 bit)
8 GB of memory
Using a variety of soundfonts, Mainly ChoriumRevA, evanessence,
CrisisGeneralMidi30.1, GMR Basico 1.1 (usually one at the time)

Hope this is useful

Posts: 1972
Joined: 25 Mar 2012 - 01:19
Re: Virtualmidisynth not closing when closing midi player

I see there's a trial version of Notation Composer... will try it.

Posts: 1972
Joined: 25 Mar 2012 - 01:19
Re: Virtualmidisynth not closing when closing midi player

Could you please take a look here and test the attached beta version?
It seems that these 2 bugs are related.

Please confirm if it fixes the bug you reported.

Posts: 1972
Joined: 25 Mar 2012 - 01:19
Re: Virtualmidisynth not closing when closing midi player

I tried to reproduce the bug on my side using the latest trial version of Notation Composer 3.0.1.3 (NC from now on) but I failed, so I need further details.

Patrick Janssens wrote:
When closing down notation composer it looks like virtualmidisynth is not closing down.

What you mean? Do you still see VMS icon into systray area after closing NC?
VMS has no own process, it's a DLL loaded by an host application (NC): if composer.exe process is killed, then VMS is killed too.
Could you please check into Task Manager (CTRL+SHIFT+ESC) if that process was really closed?
If yes, and you still see VMS icon, please move your mouse over it and check if it disappears.
If yes, it means that NC unloaded the DLL improperly, without releasing the driver before... please let me know.

Patrick Janssens wrote:
When I open my Notation Composer again it starts up a new instance of virtualmidisynth. So eventually I end up having several instances of virtualmidisynth running in parallel

Again, check that you're really running a single composer.exe instance and not two (the current one and a "zombie" one).

Patrick Janssens wrote:
there seems to be a resources issue (e en if only one instance is open, i.e. when trying to open or save a file all folder icons are blacked out and sometimes I can't even manage to safe a file.
...it seems to have appeared with the latest virtualmidisynth release 1.12.0

Please check version 1.12.1 that fixes a (maybe) similar bug.

Posts: 2
Joined: 18 Dic 2014 - 20:15
Re: Virtualmidisynth not closing when closing midi player

Apologies for not reverting earlier. Was out of the running for some time.

I am presently in contact with the developers of Notation Composer as well. The issue may be on that end and they are now investigating.
So far I understand they have not been able to reproduce the problem on their side.
But waiting for further feedback.