Beatloop_activate should respect active loop in point
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Fix Released
|
Low
|
RJ Skerry-Ryan |
Bug Description
I think that if a user has set up a loop with loop_in and loop_out (or any other way other than beatloop_activate), and that loop is active at the point when the user presses a beatloop_activate button, the newly activated beatloop should start at the loop_in point of the previously active loop.
Currently, it seems that beatloop_activate will start a beatloop at the current play position, regardless of whether a loop is currently active or not (in other words, the loop_in point will change if a beatloop is activated over a currently existing loop that was manually set up.) The only exception to this seems to be if the previously active loop was also initiated using beatloop_activate - in that case, the inpoint doesn't change.
tags: | added: loop |
tags: |
added: looping removed: loop |
Changed in mixxx: | |
importance: | Undecided → Low |
Changed in mixxx: | |
status: | Fix Committed → Fix Released |
Thank you for the report. Which Version of Mixxx is effected?
I either cannot reproduce it with Mixxx 1.11.0-pre and Ubuntu Precise or I have not got your point.
Can you give a step by step description to reproduce the issue.