garageCube

Doerak · by **Doerak** » Sat Mar 12, 2005 3:38 am

Heya.

I wrote my first module! It is an attempt to make a pretty reliable BPM tapper. It has been posted in the Online Module Library. The code is clean and well commented. Look at it to see how it works. I'm pretty new at python, so it WILL have stupid mistakes

Comments and suggestions are welcome!

sigmasix · by **sigmasix** » Sun Mar 13, 2005 3:37 pm

That's quite good but I think in the future the best thing to do is to group all the "TAP" modules in one with different possibilities to synch all the effects. I can't imagine tapping all the night in a dozen of different modules

yves@garagecube · by **yves@garagecube** » Sun Mar 13, 2005 5:16 pm

sigma6 wrote:That's quite good but I think in the future the best thing to do is to group all the "TAP" modules in one with different possibilities to synch all the effects. I can't imagine tapping all the night in a dozen of different modules

Yes, we have similar thought here. Currently there is no way to share data between two modules that's why we see all these redundancies. The future beta will have a global dictionary shared between all modules. We plan to release Modul8 2.0 with a standard TAB/BMP module that will export its current time sync. value to the global dictionary. This way other modules can simply re-use it and connect the value to the effect they want.

Yves.

Doerak · by **Doerak** » Mon Mar 14, 2005 10:36 pm

Okay. Feel free to use stuff ftom my implementation. Or not

cal6n · by **cal6n** » Tue Mar 15, 2005 3:37 am

yves@garagecube wrote:The future beta will have a global dictionary shared between all modules. We plan to release Modul8 2.0 with a standard TAB/BMP module that will export its current time sync. value to the global dictionary. This way other modules can simply re-use it and connect the value to the effect they want.

Yves.

Excellent! An elegant solution!

Akira · by **Akira** » Sun Mar 27, 2005 8:24 pm

cal6n wrote:
yves@garagecube wrote:The future beta will have a global dictionary shared between all modules. We plan to release Modul8 2.0 with a standard TAB/BMP module that will export its current time sync. value to the global dictionary. This way other modules can simply re-use it and connect the value to the effect they want.

Yves.

Excellent! An elegant solution!

Excellent stuff indeed.

And don't forget to add MIDI clock functionality in this, too .

yeah i'm the local MIDICLOCk annoyance

stuart · by **stuart** » Tue Mar 29, 2005 8:31 pm

will you be able to tighten up the response of the tappers? Currently I get a lot of latency on re-syncing.

X-Ray · by **X-Ray** » Tue Jul 19, 2005 5:12 pm

What about the Midi-Clock-feature within the advanced BPM-Module?
Isn´t there anyone who is able to implement this feature?
Pleeeeeease ...

X-Ray

Akira · by **Akira** » Wed Jul 20, 2005 12:06 am

Something I noticed...

everytime I tap I get HALF the value of real BPMs. Dunno why that is but I am measuing it at 1/1 and for example, 126BPPM songs get a value of 63 if I tap.

Checked with a reliable professional BPM detector, btw

So the module should need a little change in the tapping calculation
Basically I think it needs to multiply the value by two but reduce the speed dividing it by 2. I dont think that was undersandable but I'll try to modify it myself.

And while doing that, I'll see if midiclock can be implemented.

VJ-A2D · by **VJ-A2D** » Sat Oct 29, 2005 9:14 pm

Akira wrote:And while doing that, I'll see if midiclock can be implemented.

And did you find something ?

garageCube

Advanced BPM Tapper

Who is online