Composer crashes when setting up midi controller

[Pat401]

Thanks for all the info, Sherry.

I've done the configuration part and that seems to have fixed the crashing problem so far.

I checked out the drivers at Miditech but there isn't one particularly for my controller. I'll email them and ask if any on their list will do.

Downloaded and installed the free ASIO driver but up to now it doesn't work because I can't find any reference for it my sound card's panel. I'll have a look at the other stuff you've suggested over the weekend and get back to you on how it goes.

Cheers,
Pat

[Sherry C]

Hi Pat,

Well, hopefully the MIDI Device Configuration settings will eliminate the crashing problem.

For ASIO, it won't show up as a device. It just provides a "fast path" as it were for audio, as opposed to the default Windows MME or Windows Direct Sound. It won't do you any good unless you use a MIDI device other than the default GS Wavetable, as the GS Wavetable interferes with ASIO. You'll need to use something like SynthFont's "MIDI input" feature while using Composer, and setting SynthFont to use the ASIO routing for the audio output.

The "generic" signal path during recording goes like the following:

keyboard -> Composer -> MIDI Device -> audio

When you play your keyboard, the signal goes to Composer, which then (1) records the notes and MIDI controllers (eg. volume, velocity, etc.) and (2) sends the signal on to the MIDI device to create the audible sound by converting the signal to something the audio device (your soundcard) can interpret into sound.

If you want to use SynthFont as the MIDI Device, then you'll need to install a virtual MIDI cable to get the signal from Composer to SynthFont (the MIDI Device). SynthFont can then use the ASIO "route" to get the signal to your audio output (your soundcard).

In that particular case, your signal would look like this:

MIDI Start 25 -(USB cable)-> Composer -(virtual cable)->SynthFont -(ASIO)-> soundcard->speakers/headphones

Hope this helps things make sense You can search on this forum to find discussions, specifics, and links for SynthFont and virtual MIDI cables, and in the Tutorial Videos for helps as well.

ttfn,
Sherry

[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

[Sherry C]

Hi Pat,

A quicky thought (I'm fixing supper) - maybe try turning off the MIDI Start, and then turning it back on after you restart Composer. There is one other keyboard that a user found (only one I know of) that actually has to be off before Composer and then turned on to work properly.

ttfn,
Sherry

[Pat401]

Nope, that doesn't work. I'll just keep fiddling around. Probably just have to get a different keyboard or computer at some stage. Won't be for a while though so I'll keep fiddling and swearing for now.

Thanks for all your help,
Cheers,
Pat

[Sherry C]

Hi Pat,

I think your surmise that the problem is some sort of driver conflict is most likely correct, given that Composer is not consistently detecting the device (which Composer is quite good at), and that the computer is hanging like that on shut down. A quick google on "driver for MIDI Start 25" shows that some other MIDI programs have issues with the MIDI Start 25 unit as well. That's unfortunate, because it looks like a well-built piece of equipment from what I see in descriptions. Perhaps some gentle nudging from customers would get them to come up with a more robust driver solution (probably not swearing, though ).

Here's hoping for you!

ttfn,
Sherry

[Pat401]

Thanks, Sherry.

I'll let you know if I manage to get things sorted and if there's any joy from Miditech.

Merry Christmas and Happy Holidays.

Cheers,
Pat

[Sherry C]

Hi friends,


I'm adding the information to all SynthFont related posts that with the Notation Software Synth, as well as the advanced audio capabilities of version 5 and going forward, there is no need to use SynthFont with our software as our synth is actually more flexible and handles more than SynthFont does.


ttfn,
Sherry