Composer crashes when setting up midi controller

[Pat401]

Hi Sherry,

Over the weekend I've been able to get NC, Loopbe, SoundFont and the free ASIO driver to work together nicely ... ish! Still have to properly understand how to change the sounds in SF but I can work on that.

There are two remaining niggles, one I think is a problem with my computer, the other possibly a NC/Midistart conflict. I'll detail with the conflict first.

When NC has been opened and everything is working as it should, if I close NC and then re-open it (but not turning off the computer), it doesn't find or recognise the midistart controller even though I've left it turned on.

I tried a couple of things, checked the Port and Device tabs in the Configuration window and made sure they're correct. That doesn't do anything. Then, again in the Config window, I tried the Select tab and highlighted the default configuration. Midistart then appears in the config window but with ***Not Detected*** above it. So I have to restart the computer to get everything working again.

The second niggle is that the computer won't actually do a soft restart, it just hangs in the "Windows is shutting down" screen so I have to turn it off via the on/off button. This happens a lot regardless of whether I've got NC running or another music program, even with Red Dot Forever. I've googled the problem but haven't found anything useful yet.

Earlier, I emailed Miditech re a driver for the controller, they replied that I should update Windows drivers, etc., as the unit doesn't have a specific driver. Everything is up to date so I suspect the non-shutting down is due to a driver conflict.

Or, it could be a "I've not had breakfast yet" conflict! Yes? No!

Cheers,
Pat