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!Pages
- coolsoft
- Posts: 1978
- Joined: March 25, 2012 - 01:19
- guilt
- Posts: 3
- Joined: November 14, 2016 - 17:37
Hi,
It tells me that only 32bit version available, despite both drivers being marked with the (x86 x64) icon. I am running Windows 10.
I know that the 'Windows Wavetable GS Synth Kernel' has both 32bit and 64bit drivers. Please ensure this is fixed.
- coolsoft
- Posts: 1978
- Joined: March 25, 2012 - 01:19
Could you please post the debug file content?
Open VMS configurator, About tab then press "Debug report" button and attach its output here.
- guilt
- Posts: 3
- Joined: November 14, 2016 - 17:37
Here you are!
- Attachments (Only registered users)
- VirtualMIDISynth_debug_report.txt
- coolsoft
- Posts: 1978
- Joined: March 25, 2012 - 01:19
guilt wrote:Here you are!
Configuration seems OK, nothing wrong.
Again, having the x86/x64 icon is a clear sign that drivers was correctly seen by VMS.
Well, it should work as expected...
Since you're on Windows 10 I know you were changing the "Windows Media Player default device" combo box, but which was the situation before/after the warning message?
I mean, were you switching from VMS --> Microsoft GS Synth or back?
- guilt
- Posts: 3
- Joined: November 14, 2016 - 17:37
Yes, both ways, the errors came.
- Draq
- Posts: 6
- Joined: October 31, 2016 - 00:50
What happened to the interface of the configurator? I use a screen reader, and due to how the configurator is coded now I can't access the other tabs. The soundfonts also don't get read out anymore like in the previous version.
- coolsoft
- Posts: 1978
- Joined: March 25, 2012 - 01:19
guilt wrote:Yes, both ways, the errors came.
Can't reproduce it on my side, will test on a clean and updated Win10 machine.
- coolsoft
- Posts: 1978
- Joined: March 25, 2012 - 01:19
Draq wrote:What happened to the interface of the configurator? I use a screen reader, and due to how the configurator is coded now I can't access the other tabs. The soundfonts also don't get read out anymore like in the previous version.
Which was the last working version for you?
VirtualMIDISynth 2.x changed the aspect of GUI, but it still uses the same techniques and libraries as 1.x series.
- Draq
- Posts: 6
- Joined: October 31, 2016 - 00:50
coolsoft wrote:Draq wrote:What happened to the interface of the configurator? I use a screen reader, and due to how the configurator is coded now I can't access the other tabs. The soundfonts also don't get read out anymore like in the previous version.
Which was the last working version for you?
VirtualMIDISynth 2.x changed the aspect of GUI, but it still uses the same techniques and libraries as 1.x series.
I went from version 1.17.1 to 2.0.0-rc2.
Right now I have a workaround. If I want to access the other tabs, I just open the configuration file in Notepad and change the line for the focused tab. This doesn't have to be done very often to be honest.
Pages
Navigation
Login
Support me
Click here if you want to support CoolSoft using PayPal