by p8guitar » Mon Jul 10, 2006 11:47 pm
Hi Boris,
the print direct event module was very helpful, thanks for the hint!
1. Apparently the microKontrol repeatedly sends messages called
{'message': 'REAL_TIME_CLOCK', 'param1': 0, 'rawEvent': 248, 'channel': 0, 'param2': 0}
After 13 of this messages the evolution keyboards sends this message:
{'param1': 0, 'rawEvent': 254, 'channel': 0, 'param2': 0}
The evolution message is called "system real time - active sensing 254" by the midi pipe monitor, but the microKOntrol message is not detected by midi pipe.
The result is that modul8 gets a lot of CC1 and CC0 messages, even when I don't touch a knob, and these messages get mapped when I try to map other midi messages.
Unfortunately I don't know how to stop these messages but by turning off the devices...
Can we maybe expect some kind of midi filter in the next modul8 update that prevents this kind of problems? I would appreciate this a lot...
2. After turning off the microKontrol and the evolution keyboard I was able to do some midi mapping via the fireface midi port without problems (I used a IBK 10Control to generate the midi messages.)
As soon as there was some midi mapping done, the microKontrol and the evolution keyboard were not detected any more when I turned them on again.
It seems that it is not possible to use more than one midi port for midi mapping with modul8? That would be a pity!
Peter
(Modul8 2.5.4, Mac OS 10.4.9, iMac 2.33GHz Intel Core 2 duo / 2GB RAM; MIDI: RME fireface 800, Novation Remote ZSL, Korg microKontrol, Faderfox LV2 and LX2. )