When cycling a track containing a ‘normal’ drum pattern (imported from Groove Agent, 130 bpm) with 4 bars - the first MIDI event is ‘eaten’ when cycling - but only every other time (every 2nd cycle). Means the first ‘repeat’ runs ok, the second repeat misses first event, the 3rd repeat is ok, the 4th is missing first event …
when reducing the ‘cycle time’ to 3 bars the same track runs perfectly at every cycle.
The first event starts are set to x.x.x.010.
When you give the first event more time (x.x.x.030) it is triggered, but this is musically too late.
Thanks for your help!
I tried this with GA SE 5 and GA 5, tried some 10 kits, dragging loops into the track and cannot reproduce. 130 bpm, 4 bars, 4 repeats - all played perfectly without a need to increase start position of first event.
Thanks for fast response.
I think it was beat agent.
I added an export of the project.
Issue appears at the part ‘America’. the duration of track is set to 3. if you set it to 4 the issue pops up.
looks like some overload? 4 - 5 instruments per part preloaded (Arturia, Organtech, Steinberg).
Project size is too big for uploading here.
regards Christian
If overloaded, then CPU indicator (bottom-left) would hit red and you’ll hear the crackles.
I updated to 3.0.62 and checked again. I had one kick skipped on bar 2, but it was once and maybe my laptop just made a hickup. But all other notes on all other tries played as expected.
Christian, in which part you loaded Groove Agent? Dvorak or America?
If they all are shared layers, specify in this Track 2 the output to layer in part named America.
I almost can replicate this “missing MIDI events” issue, but not sure when it happens.
correct, on part named America.
as far I observed, it appears every 2nd cycle repeat with 4 bars duration (at start it is ok, 1st repeat is ok, then drop out, then ok, then drop out, …)
May be it is different looking to instrument use.
On a lean test project it does not appear - so seems somehow related to other processes.
I have no other midi (clock) signals around in the environment.
Anyway thanks for fast response.
I use the drum track for practise only…
you are beeing heard. And tempo is in the center of the problem, so if you describe related bugs, please always mention what tempo you were running, thanks.
Thanks for your attention.
My experiance: at similar patterns I described above all is good if tempo is below 98.
It did not belp if you ‘cut’ the length of the last midi event in a pattern before loop, it helped if you moved the first midi event as I described..
Looks it is related to ‘jump back’ time, - whyever only ever 2nd ‘jump’.
Again many thanks.
And - take a break and don’t work on weekends
