Hi Jason, According to our long experiments, I can say that getting rid of the delay by introducing compensation is not very effective. For many reasons. One of the main ones is that the delay is not constant. It varies greatly in time and you will have to devote a lot of time and energy to the issu...
The algorithm of work is now clear. It seems to me, let's leave it unchanged for now. When you fix the bug with the BPM definition, we will test this assembly of MM and understand whether it needs to be changed or not. What can you say about my proposal described in the topic "Discrete corrections B...
Yes, in version 3.7.6 midi clock works correctly and bpm is true, but very nervous (there are short emissions).
Maybe it makes sense to use a filter for smoothing? (As an option, have an attack and release fader?)
Hi mad-matt, You used the version for MAC OS. And we work under WIN 10. Here is a demo version of Waveclock for Windows. Test her out. https://yadi.sk/d/Ckjd_DFBLQrV-A For the local machine, we use loopMIDI(http://www.tobias-erichsen.de/software/loopmidi.html ). For transmission over the local netwo...
Hi, We have long known that the internal MM module does not correctly detect BPM (from an audio signal). To work around this problem, we began to use the external Waveclock program. With its help, we plan to synchronize all the programs included in the creation of the show. BUT, and then a nuisance ...
Hi,
Another important addition, in our opinion, will not harm the functionality of MadMapper. There is really not enough opportunity to press one button to sharply increase (or underestimate) the BPM value by 2 and 4 times.