MIDI gone bad.

[Wiskow]

I have posted before about my strange MIDI problems and tonight I have done further investigation.
The problem is after a period of time playing the MIDI keyboard ghost MIDI data begins to play.

Setup:
Roland A-33
Edirol UM-1SX
MIDI-OX
MIDIyoke
USINE4.22d (happed with v5.01 too)

MIDI-OX: Edirol Input is mapped to MIDI Yoke 1 and 2.
USINE MIDI-IN: is mapped 1:MIDIyoke1 2:MIDIyoke2 3:Edirol

Tonight I played a MIDI file of a rather complicated Piano Beethoven piece consisting of one channel. I directed it towards the Edirol MIDI-out so that it then went through the Keyboard back into the Edirol, into MIDI ox, through MIDI yoke, into USINE, into a track containing a VST instrument. After some time that I didn't record the Ghost notes happened. The Ghost notes are always repeats of what was originally played and in the same order just at a latter time and rhythm. I discovered that it was only coming in through USINE MIDI 1 which is MIDIyoke1. I am not sure if that was the active port at the time stuff went screwy. I also discovered that the Ghost notes only played when a new MIDI data was being sent down MIDI yoke1 either I was playing a note, MIDI time code or CC data was being sent. Without closing USINE I opened standalone Kontact, set its MIDI In to MIDIyoke1 and played some MIDI. Kontact gets the MIDI data perfectly, simultaneously while USINE continues to play its Ghost MIDI.

My guess is USINE uses some MIDI buffer on each midi-input that crashes.

The quickest fix I can do is open Global Setup, navigate to MIDI In and make a reassign the MIDI In. It seems to reset all the MIDI-In ports.

Is there away around USINE MIDI-In? Like a VST I can drop on to a track that was MIDI-in?

[gurulogic]

jthalamus vst, MIDIIO andTobybear MID2VST will both give midi input in plugin form.
Sorry, I don't have links....Google

Let us us know if it changes things. I too have dealt with some midi issues in 4. 2 but it seems specific to certain VSTI's and I can't be certain it is Usine's handling of Midi to blame..
I haven't noticed anything too weird yet in v5 but I've been more patching than actually using so far.