I intend to use GP to play a few midi files from time to time (audio as well) and I would like to loop the midi files. I have created a basic pattern in logic and saved as a midi file. I then add a midi player block to GP as assign that file. The issue I am having (with several different files) is that there is a skip delay in the loop. Meaning the loop plays, there is a short pause, then it starts again. Any idea what I am doing wrong here? Maybe some midi message issue (failure to grab that first note on or something?).
As a workaround I have just made the midi file huge (30 measures) and just hold the key down until I’m done, but I’d prefer a true loop if possible.
Loving this program however, it’s the only thing I’ve found that can go toe to toe feature-wise with the Kronos.
It’s just two bars long. In one case it’s the main riff for “take my home tonight” by Eddie Money. There is a section later in the song where there is the main riff, the accent stabs and a pad all going at once. For ease, I want to have that main riff sequenced (2 bars) on a loop so I can use my two hands for pad and stabs.
Not sure where I would upload for viewing, but I am willing. It’s pretty simple.
Definitely two bars and it plays/loops just fine - see video. That said, I’m not sure why the player claims it is 13 bars long - that’s a bug. We’ll look into that.
Oh yeah, I have global transpose on as this project will be playing everything a half step down (super slick to handle in GP btw). Shouldn’t impact the loop however, right?
Oh and: Mac Mini late 2012, i7 16g ram, Catalina 10.15.7. Not a pumper yet, just a “proof of concept” machine as I work on Kronos replacement path.
Depends on how the midi file was saved. If it was saved with between “start” and “end” markers and the “end” marker was set to the 13th bar, it would be seen by the MDP as 13 bars even if the actual midi was only 2 bars long.
Ahh good to know. So I went into the file and found that marker and deleted it, but it’s still showing that 13:0 end point and still skipping at the end. I wouldn’t think that the existence of data past the loop point would affect the loop itself though right? I have tried recreating the loop from a brand new track and the 13 persists, so maybe that’s a midi track default or something in Logic? Just trying to find out a way to make basic loops that I can use when needed. What am I doing wrong? lol.
Have you tried different plugins? When the midi file loops it is sending All Notes Off and All Controllers Off messages. So maybe different plugins are handling this differently. I get a pause with Blue3 when it loops, but not with some others I’ve tried.
If you can, edit your midi file to send its All Notes Off message at the very end of the clip just before the start of the next bar. For instance, at position 2.4.99 instead of 3.1.00.
