Some suggestions!
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!- frogblender
- Anonymous user
- frogblender
- Anonymous user
Upon further reading.... I see your DLL is at the mercy of the midi app... which throws a monkey wrench into my rant/suggestion "Midi Mixer: STOP DISAPPEARING!!!" above. A possible workaround: have an exe which is always-resident in the notification area, and is the displayer of the gui: when the user twiddles the mixing levels, the levels get passed to the DLL in almost-real-time. Similarly, the DLL will pass the instrument names and whatnot to the exe. The DLL is still the sole keeper of the actual midi stream - the midi stream never gets passed back and forth between the dll and the exe. Hope this makes sense...
- coolsoft
- Posts: 1972
- Joined: March 25, 2012 - 01:19
As you already said, VMS is a DLL so its lifetime is strictly related on the application using it (MIDI software).
The bad behaviour you're experiencing is due to a too-conservative software that closes (and unload) its output MIDI devices when they're not needed anymore: this is usually sign of good programming, but here is the main cause of this "malfunction". Maybe your MIDI application has an option to keep the MIDI out device open...?
Your suggestion of an additional exe is a good idea, and it's the way I'm following with next 2.x version of VMS.
It will try to solve much more issues, like the DLL versioning hell (think about a MIDI client using a different BASS.dll version as the one VMS needs) and soundfont preloading (actually it's done each time the virtul device is started). See the FAQ page for further details.
Sadly its release is a little delayed due to some bad real-life events (take a look at my blog and you'll see what I mean); anyway I'm still working on it and I hope to release an alpha version soon.
I've added the "solo" suggestion to my TODO list. Anyway I prefer the "icon" implementation to the "label" one (as you suggested): icons are smaller than labels and, also, they should not be translated... I hope I do not misunderstood your suggestion.
Navigation
Login
Support me
Click here if you want to support CoolSoft using PayPal