MIDI issues with Softstep and Max

[Jeff]

This is just an FYI, I don't know if this has been posted elsewhere, but thought I'd add it...When moving to using all standard Max objects with the Softstep, a few friends have run across an issue: "SSCOM PORT 1" and "SSCOM PORT 2" does not show up in the available midi devices list. On a Macintosh, this was easily fixed by

1) Unplugging the Softstep

2) Deleting the Softstep Midi Device in the Audio Midi Setup utility

3) Trashing Max Prefs (quit max first)

And then plugging in your Softstep and restarting Max.

[Macciza]

Hi
I have noted an issue involving the system midiserver crashing which is possibly what you are seeing here . . .
Can you get them to check console crash logs if they experience it or if you do? Also system setup and any other midi drivers in use is also important info. . . .
I have not had a huge play yet but have not had many issues and have not had to go to those lengths to sort it out, yet . . I have had the SS editor , Live with SScrollr and Max with multiple [ss] all running as mentioned in another post. . i guess mileage varies.
Hope to do a bit more stuff soon . . .
Cheers
MM

[Jeff]

Hey Macciza, will do. So far, the culprit seems to be that the midi driver that works with the KMI software won't let go sometimes. The last one was on a 2.8 GHz Intel Core 2 Duo MacBook Pro, 10.6.8. I'll try to grab the crash log next time. Again, an easy fix (unplug softstep, delete device in Audio Midi Setup) was the main point of this post in case anybody else was running into it...but yes, a fix in the software would be nice as well.

[Jeff]

OH yes, and there was a collection of old unused devices sitting in his Audio Midi Setup as well, with MOTU Ultralite in use.

[MattKMI]

Hey,
I had similar issues because of some old digidesign midi drivers... It might be worth mentioning that the digi drivers conflict with a lot of MIDI devices. Deleting them resolved most of the MIDI issues on my machine...

~Matt