garageCube

Greetings,

From the thread http://www.garagecube.com/forum/viewtopic.php?t=500

Saturnines wrote:when using "edit midi map",

for example, it says for a moment "1/36" ( the button I pressed ) but then immediately some other false message goes in, such as "1/0" or "1/99".

Here's what I've noticed: certain MIDI controllers, when plugged in via USB, will cause the problem mentioned above (when mapping to a module). When plugged into a firewire interface via MIDI cable, the above problem goes away. USB seems to be the culprit, but I couldn't tell you why.

Cheers,
Justin

I suppose this being a fault of the MIDI controller/interafce used, since I have no problems either with my Edirol PCR30 or my Edirol UM-1SX.

We are not able to reproduce this problem.
Can you use the "printDirectEvent" to show what exactly your controler send ?

I had this issue as well using a KORG microKontrol. In my case it was caused by my midi controller sending a midi clock signal @ 1/0.. It was solved by turning the midi clock off (on my unit just turning the tempo knob all the way down till it says "clock off").
This clock message was overriding the other signals coming from the controller..

oh, thankyouthankyouthankyou for having a microKontrol and encountering the same problem as me! turning off the clock message worked.

We are not able to reproduce this problem.
Can you use the "printDirectEvent" to show what exactly your controler send ?

sorry, have not had time to really read the forum in a while.. Will investigate, and bring the direct event data...

refresh wrote:I had this issue as well using a KORG microKontrol. In my case it was caused by my midi controller sending a midi clock signal @ 1/0.. It was solved by turning the midi clock off (on my unit just turning the tempo knob all the way down till it says "clock off").
This clock message was overriding the other signals coming from the controller..

Hmmm... turning off the clock signals?
This might solve the problem with the Korg Electribe also? Will try.


(Actually, though - Is there a way that Modul8 could recieve the clock tempo?)

Saturnines wrote:(Actually, though - Is there a way that Modul8 could recieve the clock tempo?)

Well, you should be able to receive midi clock messages in the DirectEvent script of the module system. However it is up to you to do something with them, because Modul8 does not use midi clock information at all.

The why not make a global midi clock for the next m8

It is a bit anoying having to set the BPM in each modul...

VJ-A2D wrote:The why not make a global midi clock for the next m8

It is a bit anoying having to set the BPM in each modul...

You are right. Centralizing the BPM/clock is something we plan to do for quiet some time. It won't be integrated for the V2.5 (too many other things to do), but definitively for the V3.0.

Yves.

Saturnines wrote:Hmmm... turning off the clock signals?
This might solve the problem with the Korg Electribe also? Will try.

Hmm I think I mentioned it before.. The Electribes don't send your standard fare of MIDI, they send some mixed shit of sorts. There is a MidiOx patch to mak the Electribes perfect controllers, but that means you will need a PC, and you will be adding latency to the equation.

I don't know why Korg did that with the electribes

Akira wrote:that means you will need a PC, and you will be adding latency to the equation.

Anything but that!

getting ready for a show
okay. I have the oxygen 8 attached and am printing direct events for midi

control messages show up normally when I move the knobs,e tc.

but also an endless stream of something like this:

param1 0 rawEvent 254 channel 0 param 2 0

about 1 per second. (even if Im doing nothing) what does that message mean?


when I try to set any knobs of a module, they are reset to 1/0
it's impossible to control any module.

though it works fine to control the "main interface" of m8?


this oxygen 8 is destined for the scrap heap soon.
trying to decide on which new control...

Hmmm... 254 in hexa is 0xF4

It is a sys realtime message for "Active Sensing (Sys Realtime)". You should be able to disable it?!

yves@garagecube wrote:It is a sys realtime message for "Active Sensing (Sys Realtime)". You should be able to disable it?!

1. You mean disable it on the Oxygen 8 itself, or somewhere else?

2. So that message isn't caused by a broken control, but some system function

Something is sending to Modul8 the 254 message periodically. This is a midi message called ""Active Sensing (Sys Realtime)" (from I saw in the midi references). I may be wrong, but I guess it is the Oxygen 8 which sends this message... So maybe there is a way to disable that.

PS: A small correction from by previous post: 254 of course is not 0xf4, but 0xfe. (It changes nothing, because 0xFE is the command for "Active Sensing (Sys Realtime)")