Thanks for mentioning this issue. We've taken a look at it today and the fix for this unwanted behaviour should already be included in the update later today. Now you will be able to over-hold the trigger to make sure there are no gaps when the loop gets played back. The record loop will still record beyond its borders, but the playback will no longer have gaps because of overlapping midi notes.
Your proposed solution of stopping recording MIDI when the playhead leaves a record region (so that the play loops are exact copies of record loops and any over-held notes from recording are cut off) would also work but it might present a problem for another user who wouldn't want a MIDI note to necessarily be retriggered after the exit of a region. Imagine having a pad with a very long attack time - retriggering it at the beginning of every loop would constantly start it at a very low volume, while a user might just want to leave the texture/drone to persist in the background.
In the future we might implement a drop down menu for every loop where users could set if the MIDI notes should be retriggered for every loop or not, but for now they will have two options:
- A play loop assigned to a shorter record loop will play back also notes that were over-held (but it will no longer produce gaps because of overlapping MIDI notes) - in short - no cutting off of over-held notes
- If the user wants to make sure MIDI notes are retriggered then instead of assigning a long play loop to a record loop he will have to create a number of play loops, not longer than the record loop (creating them is very easy and fast using the copy and paste commands)
For easier understanding, I've added a picture - the upper track corresponds to the first option (does not force retriggers) and the lower to the second (forces retriggers).