Strange behavior for the Cycle function

Hi, I would like to report what potentially could be a bug related to the Cycle function.

Here are the steps necessary to replicate the observed behavior:

  1. Set up a cycle within a Part of a Song
  2. Set the Song End Action as When Last Event EndWhat Start Next Song
  3. Play the Song from the beginning and reach the section delimited by the L and R marks
  4. The section delimited by the L and R marks is repeated cyclically, but the progress of the Part continues and, when the end of the Part is reached, the performance suddenly goes to the next Song without any user action disabling the cyclical execution

That is a bit unclear. Tried: new project, create 3 Parts, set Part 2 trigger to left locator (5.1), set Part 3 trigger to right locator (9.1) which i guess you mean by that? Created a MIDI track and event spanning cycle (5-9). Then when cycle is on (or not), as soon as the event end is reached, the next Song start to play.
Ah - if the event end exceeds the right locator it does behave weird. Will check and fix, is that what you mean? As always, thanks for reporting!

Hi, thank you for the answer and I try to represent you a more precise scenario, so as not to leave doubts:

  1. Create a Song consisting of the Parts:
    • Part 1 → from 1.1
    • Part 2 → from 4.1
    • Part 3 → from 8.1
  2. Create a MIDI track with an event between positions 1.1 and 10.1
  3. Set up a cycle in Part 2 with the locators L → 5.1 and R → 7.1
  4. Set the Song End Action as WhenLast Event End and WhatStart Next Song
  5. Play the Song from the beginning and reach the section delimited by the L and R marks
  6. The section delimited by the L and R marks is repeated cyclically, but the progress of the Part 2 and Part 3 (represented on the left side of the GUI) continues and, when the hypothetical end of Part 3 is reached (end of the MIDI event), the performance goes to the next Song without any user action disabling the cyclical execution.

I hope I have provided you with the way to perfectly replicate the observed behavior.

Thank you, as said before it is wrong when the event exceeds the right locator. Internally, it simply continues to run as if there was no cycle, so when cycle starts over it will eventually reach the end of the event. The bug has been found and fixed, thanks for reporting!

Great, thanks to you! I’m waiting for the new version to evaluate the software behavior after applying the fix :slightly_smiling_face: