When cueing a pattern in pattern mode (Hold down pattern and left/right arrow), the cue loses focus if you enter Performance Mode

Bug Description

If you cue up a pattern using Hold Pattern and left/right arrows and go into performance mode, it keeps the cue engaged until you go back to your pattern, and then ignores the cue on the next loop, despite that it still appears engaged.

Steps to Reproduce

Have a project ready with 2 patterns available set at 64 steps so you have time to switch between the 2.

  1. While Pattern 1 is playing, cue pattern 2 by holding down the pattern button and pressing right arrow to arm pattern 2.
  2. While Pattern 1 is playing, and Pattern 2 is armed, Press Perform to go into Performance mode. You can stay in this mode as long as you like. Take note that the cue that was set up does not occur.
  3. When you are ready, press Pattern to go back to the main page. Take note that the cued track is still armed to cue, but when it gets to the next loop, the cue doesn’t engage.

I think 3 things here should happen, depending on the intended functionality.

  1. If you cue a pattern, and move to performance, the Tracker should respect your cue and change patterns at the next loop
  2. Cue patterns work only when you are on the patterns page. If that is the case, then going to performance mode doesn’t cue the next pattern, but when you go back to pattern mode, it goes to the next pattern on the next loop.
  3. The Tracker doesn’t support cuing a pattern, and going to performance and then back to the pattern page. If that is the case, then the pattern should not flash red indicating that it’s going to move to the cued pattern, which it does not do.

Additional Info
Logging this bug from feedback given in the post below. I have had this issue as well and was a bit confused by the results so thought it would be worth logging.

Occurrence / Frequency

Always

Found in Firmware

  • Version: 1.2.0
  • Build: 1480

Attachments

3 Likes

@Dann Thanks for reporting this bug.
I easily managed to reproduce it. It’s logged, and hopefully it will be fixed with one of the future updates :slight_smile:

we just need a mod to agree with us about the broken issues of tracker to get some eyes on it

this was the OTHER glaring problem with tracker that wasnt really bothering me all that much tbh but def needed a fix for this thing to make actual sense

This is the QA lead acknowledging a bug, which is the first step in getting it fixed :slightly_smiling_face:

only someone who uses the tracker would know this was not working. i remember asking about this years ago. is polyend using tracker? itll be fixed you say? great news.

I use the tracker and never ran into this.. BUT i also never use queuing. :person_shrugging:
We all got different workflows.

i guess its good if you dont want to use an implied feature or if you expect it to work like other stuff just does. im guessing you dont use tracker live? imo theres too much to easily do live unless you simplify to the point of relying only on samples and chops. like you have to resample everything. but yeah not keeping the que alive between screens seems like an obvious one tbh. id go even further that all cc control of tracker should be available in all screens too.including entering into the que for all tracks and fx control.

the tracker is brilliant and simple enough to grasp, but broken in a couple ways that are genuinely important to a performer and composer. its not far off the mark! thats frustrating.

1 Like

totally get you and that is an absolutely fair statement.