garageCube

[mowgli_uk]

It was all working fine and suddenly none of the three variations I have of the BPM global module detect external midiclock. I'm sometimes getting this error at line 21 of the BPM Global module from garagecube:

ZeroDivisionError: float division


The midiclock data appears in the printdirect event module though. Any clues?

[ilan]

Try deleting the modules and re-downloading them from the online library.

[mowgli_uk]

I've done just that including stopping all other modules to no avail.

It's very strange, it's always worked perfectly and suddenly out of the blue having not changed anything it gives this error.

[sigmasix]

Can you try to reload the module several times (cmd-alt-R). Sometimes the debugger acts wiredly…

If you click on the "go to error" button, can you copy/paste the code here?

It's strange that it was working before and now not anymore… did you install something or update your OS with a new version of python?

[mowgli_uk]

No new installs or anything.
I've tried what you said to no avail.
The highlighted code where the error appears is:

speedTest = round (60 * (1.0/ (timeDiff)))


the module works fine until I press use midi clock and the error appears

[The Midi Thief]

Just curious, but did this have anything to do with a system update? Theoretically a change in the OSX midi routines could cause problems.

I haven't seen this problem. But I've had problem when I run two variations on BPM (global) Module at the same time. But that's just a silly mistake on my side.

[mowgli_uk]

No system updates, nothing. It's just stopped working completely suddenly...and I need it!!
Can't any of the developers help by looking at the error?

[sigmasix]

the act of god is quite unusual in computer science

something must have change in your computer in order to return an error you didn't have before.

We'll try to figure out what's going on in the module and if we can bypass this error, but I think in your case, modul8 doesn't receive any midi clock so there's one variable that is not updated and set to zero. When used in a division, it triggers this error.

Can you try the printdirectevent module and see what MIDI modul8 receive?

[The Midi Thief]

I'm just trying to help by troubleshooting (I know how painful these things are when you are on a deadline).

As Sigmasix said, are you sure Modul8 is receiving Midi Clock? And have you tried using another app to send the Midi clock? Theoretically (again) there could be an error at the other end.

[mowgli_uk]

Can you try the printdirectevent module and see what MIDI modul8 receive?

As mentioned above I've already tried this and the midi clock data IS there.

[sigmasix]

can you please give us a copy of what modul8 is receiving?

thanks

[mowgli_uk]

This is it

[mowgli_uk]

I've been doing some tests and the results are confusing.
Basically I fed the midi clock signal from one laptop with ableton to another one with modul8 through a network cable. This worked fine.
The problem happens when I'm sending the midi clock signal internally with both ableton and modul8 running on the same machine although as I've pointed out earlier, this configuration was running flawlessly for a long time before it stopped working.
The ableton midi settings are the same in both cases and in both cases the midi clock data shows up in the print direct event module.

[mowgli_uk]

Even weirder!
It all seems to be working again after feeding midi clock from another machine. It looks like this might have reset something somewhere as I went back to a single machine and suddenly it all works again......I'm happy its sorted but I'd like to know what the hell caused it in the first place?

[mowgli_uk]

And suddenly it has stopped working again!
This is very frustrating as I can't pinpoint what's causing this. Exactly the same symptoms as last time...