I know this project is well and truly closed, it's just that it's such a useful app I need to raise this issue.
The timing is great except for one thing- when synced to midi clock, ztracker runs at 5/4 of the speed it should. Put simply, for every four beats the clock source plays, ztracker plays five. Is this a bug somewhere in the midi song position pointer code? I'm not sending song position pointer, so maybe it's expecting it.
This issue happens using any clock source (software routed through midi yoke or hardware from a sequencer).
I can code in c++, but I don't have visual studio. I'm currently trying to find it in the code, but if the original author is out there, maybe he could point me in the right direction (please?). I'm a poor uni student right now and cant make donations at the moment but will next year when I'm working, if that's any incentive. I have software of my own that people don't donate to when they use it :)
Regards,
Laurence
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I know this project is well and truly closed, it's just that it's such a useful app I need to raise this issue.
The timing is great except for one thing- when synced to midi clock, ztracker runs at 5/4 of the speed it should. Put simply, for every four beats the clock source plays, ztracker plays five. Is this a bug somewhere in the midi song position pointer code? I'm not sending song position pointer, so maybe it's expecting it.
This issue happens using any clock source (software routed through midi yoke or hardware from a sequencer).
I can code in c++, but I don't have visual studio. I'm currently trying to find it in the code, but if the original author is out there, maybe he could point me in the right direction (please?). I'm a poor uni student right now and cant make donations at the moment but will next year when I'm working, if that's any incentive. I have software of my own that people don't donate to when they use it :)
Regards,
Laurence