You are here
Home › Forum home › VirtualMIDISynth › Bug reports › Missing "Default MIDI Out device" options/"No soundfont"-error (Windows 10) ›Missing "Default MIDI Out device" options/"No soundfont"-error (Windows 10)
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!- NappyMash
- Posts: 2
- Joined: August 9, 2015 - 15:49
- LEO
- Anonymous user
YES
ME TOO
Any solutions?
THANKS!
- fred james
- Anonymous user
I had the same problem. Uninstalled coolsynth, reinstalled it and set it up again. That fixed it.
- NappyMash
- Posts: 2
- Joined: August 9, 2015 - 15:49
fred james wrote:I had the same problem. Uninstalled coolsynth, reinstalled it and set it up again. That fixed it.
- Thank you Fred James. I have tried that thrice now though, once with the previous version, and all three times without any results, sadly.
Anyone who has any other suggestions?
- bogie152
- Posts: 5
- Joined: August 29, 2015 - 15:30
No MIDI sound on Notation Composer with Windows 10
Ed Burk - August 31, 2015 - 17:33
I keep getting the following message; "No soundfont loaded/enabled. Press OK to open VirtualMIDISynth configurator and load/enable at least on soundfont file. Then remember to restart your MIDI application."
I have tried this for two days and can't get a list in the box to to check or choose. I am trying to get the sound to work in Notation Composer. Since I now have Windows 10... I have been having problems.
Thanks for your help.
Ed Burk
- coolsoft
- Posts: 1978
- Joined: March 25, 2012 - 01:19
There's a similar error reported here.
It seems that Windows doesn't allow accessing some folders.
Try the workaround suggested there and please report your results.
- drewz
- Posts: 1
- Joined: November 25, 2015 - 05:01
I too kept getting VirtualMIDISynth's 'No Device found' error on one of my PCs (I tried restalling multiple times as well). However, VirtualMIDISynth works fine on my two other PCs. Main difference, it would seem, is that the PCs that work without issue were originally installed with Windows 8 (then subsequently updated to Windows 10), whereas the PC which has the 'No Device Found' error was originally a Windows 7 machine, which was then updated to Windows 10. So somehow the path from Win7 to Win10 creates issues, whereas the path from Win8 to Win10 is OK. Another one of those weird Windows idiosyncracies, no doubt.
- KaleidonKep99
- Posts: 102
- Joined: March 8, 2014 - 22:29
drewz wrote:I too kept getting VirtualMIDISynth's 'No Device found' error on one of my PCs (I tried restalling multiple times as well). However, VirtualMIDISynth works fine on my two other PCs. Main difference, it would seem, is that the PCs that work without issue were originally installed with Windows 8 (then subsequently updated to Windows 10), whereas the PC which has the 'No Device Found' error was originally a Windows 7 machine, which was then updated to Windows 10. So somehow the path from Win7 to Win10 creates issues, whereas the path from Win8 to Win10 is OK. Another one of those weird Windows idiosyncracies, no doubt.
Check if both MME and DirectSound are present in the system, by installing Audacity.
You should see something like this: http://prntscr.com/976rsu
This happened to me on Windows 8.1 a while ago. I wasn't able to use synthesizers nor play games based around DirectSound and MME.
Navigation
Login
Support me
Click here if you want to support CoolSoft using PayPal