NoteWorthy Composer Forum

Forums => General Discussion => Topic started by: nschreiner on 2016-01-04 06:12 am

Title: midi trouble with windows 10
Post by: nschreiner on 2016-01-04 06:12 am
New forum user here, been with NWC since '98. If this has already been discussed and figured out, please let me know. I recently upgraded to windows 10, and after a few weeks of the computer freezing up requiring a hard shutdown and reboot, all the midi ability  stopped. The computer runs more smoothly now, but I can't play midi, record, or in any other way use midi. When I click 'play', a warning window pops up saying "One or more of your selected midi devices are failing to open. Would you like to go to the midi options tab to investigate?" I click Yes. The midi tab shows Microsoft GS Wavetable Synth in the field for "Devices used by play back", where it is supposed to be. I click OK. I click Play again, and an alert pops up at the bottom of the screen saying "Alert #1: Upgrade Check Failed: Could not connect to noteworthycomposer.com"
I dabbled in the Microsoft Knowledge Base regarding this, and couldn't get any answers except to try using CoolSoft VirtualMIDISynth. I downloaded it and I get the same result. It is also listed in the field for "Devices used by play back".
The same midi problem happened when I upgraded another machine to windows 10, except much more promptly, not several weeks later.
Does anyone have a solution? Many thanks!
Title: Re: midi trouble with windows 10
Post by: Rick G. on 2016-01-04 06:26 am
You might look at: Windows 10: Configuring Play in Version 2.51a (and older) (https://blog.noteworthycomposer.com/info/windows-10-configuring-play-in-version-2-51a/) on NoteWorthy's blog.
Title: Re: midi trouble with windows 10
Post by: nschreiner on 2016-01-04 07:24 am
Ha! Haha! That worked! I saw something about that earlier, and I thought I tried it without success. But it worked this time. Thank you.
Title: Re: midi trouble with windows 10
Post by: NoteWorthy Online on 2016-01-04 07:54 am
I recently upgraded to windows 10

Two points:


See also: