Hello I have a yamaha Genos 2 i am using for my master clock and i want it to set the BPM for my gigperformer 5. its not accurately showing the correct bpm, Genos2 says its 120, but GP will fluctuate constantly around it. Like 119.9, 121.2, 120.5, 119 so and so on. Is there a way to make it stay stable
What Version of GP are you using?
Gig Performer 5 Pro for Windows
Yes for windows
I’ve done a lot of testing and on Windows (can’t compare is with mac) I never got it completely stable. I even built my own external MIDI clock, but no sigar…
It might have something to do with how USB schedules its transfers…
On the other hand: I synced a few instances of GP with this MIDI clock and even after an hour they were still in sync…
The main problem is
I use genos2 with a midifile with the clock to Gp
Then i use mij keytar with a vst in Gp with a delay effect in tempo and everytime the delay is not in sync on the moment the tempo from Gp is changing e.g. 119.6 then 120 then 120.3 then 119.7 and so on
Are you actually hearing a significant difference in the delay or are you just looking at the display values?
hearing a significant difference in the delay
Could it be that Genos is not sending constant midi clock tempo?
Indeed? Also, could it be that the Genos (or something else in your system) is sending a lot of other MIDI data?
with ableton there is no problem
only the genos sent midi clock to GP
with the keytar only one channel to GP for the guitar sound
I just made a test:
Ableton Live 12.3.7 is sending out MIDI Clock
Gig Performer 5.1.6 is receiving MIDI clock
In Rig Manager I enabled receiving MIDI clock
In the Rackspace settings I enabled “Sync tempo with external MIDI clock”
In Ableton I set the tempo to 121.5 and in Gig Performer it stays on 121.5, no jitter at all.
I think that Ableton Live maybe does some interpolation when getting variable MIDI clock as Gig Performer reacts more accurate in incoming MIDI clock.
I was testing with Gig Performer 5.1.6
That may be the case, but it would be great to at least have an option for a smoother interpolation and/or ability to have it calculated to whole numbers only.
Some delay plugins don’t react well to constant fluctuations.
But we agree that the sender in this case is the culprit?
It might be worth requesting an improvement that would perform some averaging/smoothing, perhaps using the same mechanism used for some of the tap tempo alogrithms. This could be used to compensate for systems don’t generate accurate clocks.
I’ve tested GP with a hardware clock generator (Midronome) and GP follows it exactly
There is a product for mac OS/iOS called Midipace that removes jitter for CoreMIDI physical and virtual ports, where you can adjust the sensitivity/rounding as such:
The jitter I’ve measured in Windows with incoming MIDI clocks to GP is ~ +/-0.3. It would be an improvement if GP could, in the future, have some similar type setting for interpreting clock messages. I don’t think it would need to be as granular as Midipace. Even a setting for rounding to the nearest integer(or 0.5) would be cover most use cases.
