garageCube

Today I spend 5 hours trying to configure the midi mapping of modul8, without success. All that I can achieve is mapping a single controller; when I map more controllers, modul8 forgets some of the ones that are already mapped, and/or behaves very strangely.
When I map controllers in position mode, modul8 goes mad: all transparency faders that are mapped to midi controllers are set to zero, unless they are touched. As soon as I don't hold or move a fader, it is set to zero again. Some buttons that are mapped to controllers don't react anymore, neither to midi nor to a simple mouse click - for example I cannot use the contrast effect in my project any more since it was mapped to midi.

I have no problems controlling other software with midi, e.g. Ableton Live, Logic, Union or Arkaos. So I wonder if midi mapping is simply broken in modul8 V2?

Hello,

Your experience seems strange, we use modul8 with a lot of midi controllers without problems.

I you use several controler in the same time, maybe you have same midi informations from different controler, modul8 does not make diffrence between different controlers.

You can use the module "Print Direct Event" to see what modul8 received.

Let me know.

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

Ok, we never tested this controlers, but I understand the problem.
Send me an email at the support with your serial number (support [A-T] garagecube.com)
and I will send to you a custom version with a midi filter this week.

Best,
Boris.

Great!
The email is on the way.
Thanks,
Peter

Get MIDIPipe and filter the real time clock message.

I had to do this with my Electribes.

Why is it that modul8 doesn't support the midi clock message properly? Will this be implemented in 2.5?

cheers

OK I received it, I send you the "custom" version soon.

p8guitar wrote:Great!
The email is on the way.
Thanks,
Peter

hey boris,

je suis egalement interesse dans la maniere de filtrer le midi.
tu peut me envoyer ca aussi stp.
a+