CSMMidiReciever::OnError > short

jorge · 27 Feb 2005

thanks haydxn, that's a very good description of the bug and the text in the popup dialog box will point me to the exact line of code causing the problem. I'll have a look at the code and I'll try to re-create the same bug here. I'll post here again later to let you know what's happening.

jorge · 27 Feb 2005

ok, here goes where I got so far.

The error message pops up because SM is being delivered a midi error message from windows. The message is already an error when it arrives inside SM. I created a version of SM that doesnt display the popup error message and just ignores it. You can download it from here: [old link] or if you prefer rar: [old link] With this version the DirectSound output component is a bit different:

at the moment you have to click on the DirectSoundOut component to activate it:

The DirectSoundOut component is still beta, so make sure you check the beta checkbox in the settings:

I've also included in the example schematic a String data component showing your midi messages:

I forgot to ask you before if it worked wit the PC keyboard instead of an external keyboard.

Let me know if you have problems with this version.

haydxn · 28 Feb 2005

it worked fine with the pc keyboard.

i've just tried this new version and it works just fine now. not only are there no error messages but it also plays the notes for me fine. it's odd that it's a midi error before it gets to the program; i've not had any other programs indicate this before. hmm curious indeed!

but yes, this one works fine for me! is this something that is worth leaving in 'ignore' mode? a headscratcher to be sure. something tells me that it's not the best idea to leave an error unreported, but i'm not sure why it is an error anyway. everything else is fine, it's only the older versions of SM that complain! 😮

jorge · 28 Feb 2005

haydxn wrote: it's odd that it's a midi error before it gets to the program; i've not had any other programs indicate this before. hmm curious indeed!

but yes, this one works fine for me! is this something that is worth leaving in 'ignore' mode? a headscratcher to be sure. something tells me that it's not the best idea to leave an error unreported, but i'm not sure why it is an error anyway. everything else is fine, it's only the older versions of SM that complain! 😮

Thats a good point, I feel exactly the same that its not a good idea to just ignore an error. I intend to investigate it further. The Midi message SM gets from windows is called MIM_ERROR, the microsoft documentation says the following:

MSDN wrote: The MIM_ERROR message is sent to a MIDI input callback function when an invalid MIDI message is received.

I have a feeling the message is not actually an error but just a Midi message not supported by windows. I wasnt expecting that would happen but just in case it did I put a popup dialog box message to get my attention later on if it would ever happen which just did in your case. Popup messages are not a good way to report errors, I think at some stage we'll change it to a log system. At the moment SM only supports a few Midi messages like NoteOn, NoteOff, ControlChange etc..., I think it is fine to ignore all other messages.

I'm glad it is now working for you, if you find other problems please let us know.