garageCube

[The Midi Thief]

I'm getting a bad midi clock read with BPM (Global). A BPM of 126 reads 6839 in the BPM (Global) module. X-Ray's M-BPM-MIDI reads corectly, however. Is this a bug or are different MIDI devices using different MIDI clock defaults? (I'm using the BPM analyzer RED Microsync Beat Xtractor).

Regards,
Fry up

[momo3010]

did not have any problems with midi clock, for me it works perfect. I`m using a yamaha external hardware sequencer.

[transoptic]

Hello,

I had the same problem reading a Midi BPM with that module.... I was trying to read a Midi clock from a freeware program called MidiClock...

Now I use the Module "M-BPM-Midi" to receive the Midi clock and it works fine.

[boris]

Seems strange, I had using MidiClock for the development of this module.
Witch version of modul8 do you use ?

Hello,

I had the same problem reading a Midi BPM with that module.... I was trying to read a Midi clock from a freeware program called MidiClock...

Now I use the Module "M-BPM-Midi" to receive the Midi clock and it works fine.

[transoptic]

Hi!

I'm using the final release 2.5. The BPM (global) picks up about 3900 from MidiClock, which is set at 130.

I'm on a G5, dual 2.0. Os 10.4.8. I tried starting MidiClock first, then M8.

I just checked it out on my MacBook, and it works fine though

I can just as well set BPM manually... was just checking MIDI out...

Thanks!

[boris]

I made this module from my intel macBook and you'r right the module have some trouble on a G5 computer with thw midi clock (I didn't test it on a G4).
It seems to have a problem with the midi time stamp on modul8, we will fix it for the next version.
Sorry for the inconvenience.

[Hugobox]

I have a similar problem. I'm using version 2.5.4 on a mac mini. If I use the midi clock from either Live or MidiClock, Modul8 syncs to the actual bpm times 3, so a bpm of 100 in Live results in a BPM of 300 in Modul8.

[boris]

Your mac mini is intel or g4 ?