VirtualMIDISynth 2.x - Release Candidate 2 released

Pages

Posts: 1103
Joined: March 25, 2012 - 01:19
VirtualMIDISynth 2.x - Release Candidate 2 released

This thread has been started to let all VirtualMIDISynth 1.x users try the beta version of next major version: version 2.x series, VMS2 from now on.

WARNING: If you're an unexperienced VirtualMIDISynth user you should not try beta versions but fallback to the stable 1.x versions.
VMS2 is actually in release candidate stage; it means that it's quite stable and ready to be released but still need to be tested by the community.
DO NOT use it during your live performances.
Don't worry your system won't be messed up and you can remove it completely (and get back to VMS1), but errors and any other issue could happen unexpectedly.

 

What's new in VirtualMIDISynth 2.x and how does it differ from the previous version?

See this thread for a detailed explanation.

 

What now?

I'm testing VMS2 on 3 different systems, but I can't fix all of the issues without your help.
If you're ready to test it, download the setup file linked to this post and be prepared to post your comments here.

Each bug report should be as complete as possible (the more the better).
VMS2 has a new feature to help users create a detailed debug report:
Open the Synth configurator dialog, switch to the About tab then click on "Debug report..." button.
A report file will be generated, now you can cut&paste ite content on the forum or attach the whole file.

Also:

  • Check you're running the latest available version
  • Check the post below to see if the bug you're going to describe is already known and/or has already been fixed
  • Describe the bug with as much details as possible: what happens, when, what you did
  • Try to find a way to reproduce the bug: a sequence of operations, a particular configuration.
    Reproducible bugs are easier to fix.
  • Post your system details: Operating system version, MIDI Player, soundfont, ...everything that could help.
    I suggest you to add these informations to your signature, so it will appear below each of your post.

 

When will it be released?

In a few words: when ready!

I don't have any scheduled release time for VMS2 because I actually don't know how much I can work on it.
VMS2 development is done on my spare time, which is limited by real job, family, personal tasks, ... sorry ;)

 

Download

NOTE: if you're an unregistered user, please download files from VirtualMIDISynth page.

PLEASE REPORT BETA VERSION BUGS HERE, do not start new threads in "Bug reports" forum.

Attachments (Only registered users)
CoolSoft_VirtualMIDISynth_2.0.0-rc2.zip
CoolSoft_VirtualMIDISynth_2.0.0-rc1.zip
CoolSoft_VirtualMIDISynth_2.0.0-beta6.zip
CoolSoft_VirtualMIDISynth_2.0.0-beta5.zip
CoolSoft_VirtualMIDISynth_2.0.0-beta4.zip
Posts: 1103
Joined: March 25, 2012 - 01:19
Re: VirtualMIDISynth 2.x - Beta released

...reserved...

Posts: 1103
Joined: March 25, 2012 - 01:19
VirtualMIDISynth 2.x - Beta1 released

v.2.0.0-beta1 - 2016-01-05

  • NEW: Synth component now has a native x64 version for x64 operating systems only.
    This will allow using more than 4GB of memory for soundfonts.
    Driver still has x86/x64 versions to let x86 MIDI programs work.
  • NEW: VirtualMIDISynth is now installed into its own folder under %PROGRAMFILES% (except for the Driver DLL only, that must reside in \System32 subfolder).
  • NEW: Devices selector in MIDIMapper configuration tab now shows both x86 and x64 installed devices (x64 synth only).
  • NEW: Soundfont list can now be imported/exported from/to external files to make it easier to switch between configuration sets.
  • NEW: Mixer status can now be imported/exported from/to external files to make it easier to switch between configuration sets.
  • NEW: Added a dialog to edit custom client blacklist items.
  • NEW: Added setup option to make VirtualMIDISynth automatically start with Windows.
  • NEW: Added version update check feature.
  • NEW: Updated BASS to version 2.4.11.17, BASSMIDI to version 2.4.9.22, BASSENC to version 2.4.12.9
  • NEW: Increased max voices limit to 100000 (kinda useless for realtime playing, but useful for MIDI-->wav/mp3/flac converter).
  • NEW: Added new command line options to VirtualMIDISynth.exe:
    --configurator: opens the configurator dialog
    --converter: opens MIDI Converter dialog
  • NEW: Added new start menu shortcuts to open configurator, MIDI Converter and encoders folder.
  • NEW: BASS errors will now show a more descriptive text instead of their code.
  • FIX: Fixed handling of external encoders, now they have a dedicated subfolder.
  • FIX: Restored the button to change soundfont filename in soundfont editor.
Posts: 10
Joined: October 21, 2014 - 08:30
Re: VirtualMIDISynth 2.x - Beta1 released

Thanks, looking good so far. I`ll come back with bugs...if I`ll find any :))

Posts: 9
Joined: August 14, 2015 - 05:27
Re: VirtualMIDISynth 2.x - Beta1 released

See attached

Happens when trying to set the Fluid GS (not GM) soundfont to preload (then pressing ok/apply), no DAW open when doing.

Debug:
Windows 10 Home (64 bit) (10.0.10240)
VirtualMIDISynth: 2.0.0-beta1 (x64)
Memory (MB): total 12171, free 4261 (36%)
Available devices: 2
* VirtualMIDISynth #1:
* VirtualMIDISynth #2:
Active voices: 0 - 0
Rendering time: 0% - 0%
Update rate (ms): 0 - 0
 

Attachments (Only registered users)
Temp.PNG

--

CTMiner

Using: Windows 10, Cakewalk SONAR, VB-Cable, VanBasco Player

Posts: 1103
Joined: March 25, 2012 - 01:19
Re: VirtualMIDISynth 2.x - Beta1 released

The error description is wrong (will be fixed in next version).
Error 37 should read like this: BASS_ERROR_NOTAVAIL: The soundfont does not contain the requested preset.

Maybe the GS soundfont only have some specific preset (have not checked it).
Try to configure VMS to use one of the contained presets only.

 

Posts: 1103
Joined: March 25, 2012 - 01:19
Re: VirtualMIDISynth 2.x - Beta1 released

I've added a feature to SoundFont properties editor to show soundfont details; it will be available into next beta.

Meanwhile, this is the output of FluidR3_GS.sf2 soundfont:

Name: Fluid R3 GS+SFX Portion
Copyright: Frank Wen 2000-2002, 2008; Toby Smithe 2008
Comment: Licensed under the MIT license.
Sample data size: 3191202 bytes
Compressed samples: No
 
Soundfont contains 33 presets:
(bank:preset = name)
----------------------------------
1:120 = Gtr. Cut Noise
1:121 = Fl. Key Click
1:122 = Rain
1:123 = Dog
1:124 = Telephone 2
1:125 = Car-Engine
1:126 = Laughs
1:127 = Machine Gun
2:120 = String Slap
2:122 = Thunder
2:123 = Horse Gallop
2:124 = Door Creaking
2:125 = Car-Stop
2:126 = Screaming
2:127 = Lazergun
3:122 = Wind
3:123 = Bird  2
3:124 = Door Slam
3:125 = Car-Pass
3:126 = Punch
3:127 = Explosion
4:122 = Stream/River
4:124 = Scratch
4:125 = Car-Crash
4:126 = Heart Beat
5:122 = Bubble
5:124 = Wind Chimes
5:125 = Siren
5:126 = Footsteps
6:125 = Train
7:125 = Jet Plane
8:125 = StarShip
128:56 = SFX

As you can see bank 0, which is selected by default, is missing in this soundfont.
You need to configure an existing bank (i.e. bank 1).

Posts: 9
Joined: August 14, 2015 - 05:27
Re: VirtualMIDISynth 2.x - Beta1 released
coolsoft wrote:

I've added a feature to SoundFont properties editor to show soundfont details; it will be added to next beta.

Meanwhile, this is the output of FluidR3_GS.sf2 soundfont:

Name: Fluid R3 GS+SFX Portion
Copyright: Frank Wen 2000-2002, 2008; Toby Smithe 2008
Comment: Licensed under the MIT license.
Sample data size: 3191202 bytes
Compressed samples: No
 
Soundfont contains 33 presets:
(bank:preset = name)
----------------------------------
[Snip]

As you can see bank 0, which is selected by default, is missing in this soundfont.
You need to configure an existing bank (i.e. bank 1).

Ah, that makes sense. I only knew that GS built on GM, I was not aware of the banks thing. I'll play with it when I get home.
Thanks for explaining!

--

CTMiner

Using: Windows 10, Cakewalk SONAR, VB-Cable, VanBasco Player

Posts: 10
Joined: April 13, 2015 - 18:54
Re: VirtualMIDISynth 2.x - Beta1 released

I am getting a cacophony of dissonent sounds.  I tried different sound fonts...same result.

I was using the alpha version.   I uninstalled it first and checked to make sure it was really gone.

During install it asked me what language to use twice.

Below is the debug file generated by the program (great idea!).

I don't know why it says Vista, I have Windows 7.

Status
======
Windows Vista (TM) Ultimate (64 bit), Service Pack 1 (6.0.6000)
VirtualMIDISynth: 2.0.0-beta1 (x64)
Memory (MB): total 2815, free 1287 (46%)
Available devices: 1
* VirtualMIDISynth #1: C:\Program Files (x86)\Voyetra\Record Producer\RecordProducer.exe (#3908)
Active voices: 0
Rendering time: 24%
Update rate (ms): 10
 
Soundfonts
==========
filename: C:\Save\Drivers\SoundBlaster\2GMGSMT.SF2
enabled: 1, preload: 1, bank: 0, preset: -1
 
MIDI Devices (x64)
==================
[0]: VirtualMIDISynth #1
[1]: kX Control SB0102 10k1 [ec00]
[2]: kX Synth SB0102 10k1 [ec00]
[3]: kX Synth2 SB0102 10k1 [ec00]
[4]: kX Uart SB0102 10k1 [ec00]
 
MIDI Devices (x86)
==================
[0]: VirtualMIDISynth #1
[1]: kX Control SB0102 10k1 [ec00]
[2]: kX Synth SB0102 10k1 [ec00]
[3]: kX Synth2 SB0102 10k1 [ec00]
[4]: kX Uart SB0102 10k1 [ec00]
 
Configuration file
========================================================================
[General]
Version=1.999.999.101
[SoundFonts]
sf1=C:\Save\Drivers\SoundBlaster\2GMGSMT.SF2
sf1.enabled=1
[Mixer]
[Shortcuts]
[Update]
CheckFrequency=14
[Windows]
Configurator=90,250,586,442
Configurator.ActiveTab=0
[Advanced]
LangID=1033
========================================================================
 
Registry keys
=======================
*** x86: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 ***
midi1: VirtualMIDISynth.dll
midi2: wdmaud.drv
 
*** x64: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 ***
midi1: VirtualMIDISynth.dll
midi2: wdmaud.drv
 
*** HKCU\Software\Microsoft\Windows\CurrentVersion\Multimedia\MIDIMap ***
szPname: VirtualMIDISynth #1
 
*** HKCU\Software\Microsoft\ActiveMovie\devenum\{4EFE2452-168A-11D1-BC76-00C04FB9453B}\Default MidiOut Device ***
MidiOutId: 4294967295
 
*** HKCU\Software\Microsoft\ActiveMovie\devenum 64-bit\{4EFE2452-168A-11D1-BC76-00C04FB9453B}\Default MidiOut Device ***
MidiOutId: 4294967295

 

Posts: 1103
Joined: March 25, 2012 - 01:19
Re: VirtualMIDISynth 2.x - Beta1 released
Steve Wellens wrote:
I am getting a cacophony of dissonent sounds.  I tried different sound fonts... same result.
I was using the alpha version. I uninstalled it first and checked to make sure it was really gone.

Can you confirm alpha versions worked good?
Beta1 version features the first x64-bit version of VirtualMIDISynth.exe, so that could be the issue on your side.
Could you also try with FluidR3_GM.sf2 soundfont (you can find its download link in VMS1 webpage)?

Steve Wellens wrote:
During install it asked me what language to use twice.

This is really strange. Have you uninstalled alpha* before running the beta1 setup?
If not, beta1 will offer you to uninstall the previous version, but you shouldn't receive a language choice dialog because it should default to the one you used during the installed alpha* setup...

Steve Wellens wrote:
I don't know why it says Vista, I have Windows 7.

Another strange thing.
Since detecting all of the hundreds Windows version, that information is read straight from the registry here: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion, values ProductName and CSDVersion.
Do you, by any chance, upgraded to Windows 7 from Windows Vista? If so, maybe this registry key was not updated correctly...

Anyway version number (6.0.6000 in your case) is retrieved with a system call, so it must reflect the OS kernel version, unless VirtualMIDISynth has been started with PCA (Program Compatibility Assistant) or in compatibility mode.
6.0.6000 is the correct version number of Windows Vista.
Could you please right-click on VirtualMIDISynth.exe --> Properties --> Compatibility and double check that no compatibility mode is set?

Pages

warning

Warning, JavaScript is disabled!

JavaScript is not available, maybe because you disabled it globally into your browser settings or you are using an addon like NoScript.

We do not have any dangerous JavaScript running here.
Please enable JavaScript; if you're using NoScript this image will help you adding CoolSoft to your whitelist.

Thanks for your comprehension and enjoy CoolSoft.